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
The “Corporate States of America” is a map created by writer, photographer and artist Steve Lovelace. His project, which shows the most famous brands to have come out of 50 US states, has got plenty of people talking – mostly about whether or not the brand he’s picked is the right one. For instance Apple is the brand chosen for California, but why does Apple make it to the top ahead of Google and Facebook?
Lovelace created his brand-map after writing an article on “corporate feudalism.” He believes that as companies grow ever bigger and more influential, that the power of government becomes less and less relevant. He suggests for instance that people will come to think of themselves as citizens of Apple for example.
The map also perhaps highlights that not all states are born equal. Whereas some states such as Alaska and New Mexico have few big companies, others such as California as noted above, are inundated with them. Of course this disparity is much to do with established networks and hubs – the availability of finance, staffing and location of a particular state.
In creating his map Steve Lovelace has also not necessarily used the biggest company within a particular State. For instance in Texas, the home of the oil industry, he chooses Dr. Pepper instead of perhaps the more obvious ExxonMobil.
James Barnes, StatusCake.com
James Barnes
Share this
More from StatusCake
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026
Make Your Engineering Processes Resilient. Not Your Opinions About AI
4 min read Why strong reviews, accountability, and monitoring matter more in an AI-assisted world Artificial intelligence has become the latest fault line in software development. For some teams, it’s an obvious productivity multiplier. For others, it’s viewed with suspicion. A source of low-quality code, unreviewable pull requests, and latent production risk. One concern we hear frequently goes
James Barnes
January 8, 2026