Solutions

Every multi-tenant system has a tenant filter on every query. It works for years, because people are careful, and then one query written under time pressure exposes one customer to another.

This decision gets made on a feeling about isolation and then lived with for a decade. The variable that actually decides it is what happens on the day you have to change the schema.

Every payment integration works in testing. The one that matters is what happens when the provider retries because your acknowledgement was slow, and a customer is credited twice for one payment.

The queue is backing up, so you double the workers. Throughput does not double. You double them again and it gets worse. At that point you are not scaling, you are adding contention, and every further worker makes it slower.

Realtime features arrive one at a time, each built sensibly by somebody solving their own problem, and the result is four persistent connections per tab and four reconnection strategies that behave differently.

The report takes eleven seconds. Somebody suggests an index. Somebody else suggests caching it. Both might help and neither is a diagnosis, and one of them will make the write path slower forever.

Access control starts as three roles and an if statement. It ends as a spreadsheet nobody trusts, where the only safe way to give somebody a capability is to copy an existing user and hope.

An auditor asks who approved a payment in March, under which policy, on what evidence. If the answer requires reconstructing it from a status column and a changelog, the answer does not exist.

The migration that takes the site down is rarely the complicated one. It is the single line rename that somebody ran on a Friday because it was obviously safe.

Almost every project eventually asks whether to build the API first. The honest answer depends on one thing, and it is not architectural purity, it is whether a second consumer actually exists.

The rewrite that replaces everything on a chosen weekend is the most reliably disastrous plan in software, and it keeps being chosen because the alternative sounds slower.

A site can be perfectly built, thoroughly reviewed, and rank as a single page for a year, because the thing that is wrong is only visible in the output and everybody was reading the source.

The people most in need of a service are frequently the ones on the worst connection to reach it. Designing as though everybody has fibre is not an oversight, it is excluding the users who need you most.

Working alone removes the reviewer, the second opinion, the person who remembers why, and the colleague who takes the call at two in the morning. Each of those has to be replaced by something, or the system slowly becomes unmaintainable while still working.

Observability advice assumes a team, a budget and a platform. Alone, the goal is narrower and more useful: turn every two hour investigation into a two minute query, because you are the one paying the difference.