Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



Wherever you are in the world, if you’re a commuter on the subway whether on London Underground, the New York City Subway, taking the SkyTrain in Vancouver or on Paris’ Metro , some things are always the same. Just as we have our morning set routines so does the person sitting opposite you. Like you they most likely get the same train or bus, like to sit in the same seat and spend their journey sleeping, listening to their iPod, reading a book or reading the same daily newspaper.
In many ways these people around you seem so familiar, and yet you know so little about them. Now a new study in Singapore has tried to map and understand these daily interactions.
Using travel smart card anonymised data supplied by Singapore’s Land Transport Authority, the researchers from the Future Cities Laboratory, Singapore-ETH Centre for Global Environmental Sustainability looked at the bus journeys of almost 2.9 million individuals over a week; some 20 million bus trips – capturing almost 55% of the population of Singapore.
The researchers looked at the movements on all these individuals, and looked to see how these “familiar strangers” come across each other – so called “joint encounter patterns.” And compared with other relationships that we have, for instance with friends which are driven by agreeing to meet at certain times and places, the meetings of “familiar strangers” is driven entirely by our own individual regularity. The study reinforces earlier findings, taken from mobile phone records and travel diaries that as individuals our patterns of movement are remarkably regular and predictable. We are to all intents and purposes creatures of habit.
The study looked at the pattern of repeated joint encounters – when two individuals were on the same bus – and worked out an encounter networker, detailing how often two individuals were paired together and measured the time between two encounters of those people.
Perhaps not surprisingly, certain patterns began to emerge from the data. The times between joint encounters tended to be regular, and in around 85% of cases the encounter happened around the same time each day. The study also showed that repeated encounters between two individuals tended to occur far more frequently in the morning than in the afternoon – no doubt driven by our bosses demanding that we’re in work at the same time each morning, but our home time differing depending on whether we’re working late, meeting friends or have chores to run.
This study not only makes interesting reading in terms of gleaning an insight into our own social interaction and human behaviour, but it can help transit authorities understand better not only how we move as individuals but as a mass. Planners can look at the ebbs and flows of human traffic – how we move around our transport networks, our supermarkets and shopping malls.
And with more and more devices being online, even underground as transport networks start installing wi-fi, companies like Google will be able to track devices in a similar fashion – using an ever richer set of data. When two devices come together might we see how their users online habits are influenced by the world around them – as a bus passes a billboard for a new movie might Google track how many people respond by searching for it. And might we see how ideas spread virally. How when a “familiar stranger” sees someone looking at a site on another user’s device then visits that themselves, and is then seen looking at that site themselves by another stranger who themselves goes on to visit it. And so on.
Although there’s clearly a need for data privacy the ability to track data in this way, and how we and our devices interact with others, could lead to a far better understanding of social science and collective human behaviour.
James Barnes, StatusCake.com
Share this
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
3 min read In the previous posts, we’ve looked at how alert noise emerges from design decisions, why notification lists fail to create accountability, and why alerts only work when they’re designed around a clear outcome. Taken together, these ideas point to a broader conclusion. That alerting is not just a technical system, it’s a socio-technical one. Alerting
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
Find out everything you need to know in our new uptime monitoring whitepaper 2021