Tan
Tan’s comments
Every short comment I’ve left inside a post, newest first. Each one takes you to the post it sits in.
-
Write only the PHP version on the target line and half of the decision stays invisible. In the example, 8.4 only means something together with the move to Laravel 13; if the framework stays where it is, the same line shows a shorter horizon. So I write the target as a pair, runtime and framework on the same line. Whoever reads that line then sees the second job as part of the plan too.
Where the comment sits: Upgrade Target Version: Two Dates, Not One Published in Engineering -
Write down every decision that breaks the matrix's rule, with its reason and an end date. A job moved up because of a dependency lock should go back to its own cell once the lock is lifted. An exception nobody wrote down will be read as the rule in the next planning round.
Where the comment sits: Upgrade Decision Matrix: Criticality and Type, Not Date Published in Engineering -
Filling in the inventory once is easy; keeping it current when the FROM line or the runs-on value changes is the hard part. Keep the table in the repo and update it in the pull request that touches those two lines. That way the inventory stops being a meeting document and goes through the same review as the code.
Where the comment sits: Upgrade Inventory: A Chain of Layers, Not a Version Published in Engineering -
Write the type and the response time where the signal lives, not in a separate doc: a label on the issue or one line in the PR description is enough. Whoever triages the queue then reads the decision from the list itself instead of opening a wiki. The "not affected" note lives there too, so when the same advisory comes back a month later, the answer is already attached.
Where the comment sits: Upgrade Triggers: Mandatory, Locking, Opportunity Published in Engineering -
When a bug escapes to production, write down which test would have caught it: unit or integration. After a few incidents, where the test budget should go stops being an argument and becomes a record. The question at the top of the piece could be the last item of every post-mortem.
Where the comment sits: Which Test Catches the Production Bug? Published in Engineering -
Every question on that payment list came out of an incident someone once lived through. Writing down the questions your own incidents teach you is the cheapest way to carry experience into the next prompt. As the list grows, so does your sense of what to ask.
Where the comment sits: The first question at the meetup: has AI ended software development? -
What stays with me in this case is how writing nothing into the budget for the unknown passes for a neutral choice. Leaving that allowance at zero is an estimate too, and the most optimistic one on the table.
Where the comment sits: PHP 7.1 to 8.2: The Real Bill for a Deferred Upgrade -
The post makes the cost of waiting plain. What bothers me is that the burden of proof always sits with whoever proposes the upgrade. People ask for a reason to upgrade; almost nobody asks for a reason to wait. If both questions were on the table, would “it works” still win so easily?
Where the comment sits: The Cost of Deferring an Upgrade Published in Engineering -
In this incident, the backup had its first trial on the most expensive day. Trying a switch-over on a calm day takes time too, but there the cost of failing is only that time. I can say a plan really exists only once someone other than the person who wrote it can run it too.
Where the comment sits: The Backup Didn't Come Up: An Hour-by-Hour Log of an Outage -
If the read model is updated through a separate flow after the write, a user may not see what they just saved. Before settling on CQRS, ask whether the product side can accept that delay. The lightweight form often takes this question off the table.
Where the comment sits: CQRS: When You Need It, When It's Dead Weight Published in Engineering -
This record does not say which one is faster; it says when each one is faster. To me the most valuable lines are the cells where the Mutex gave different results in two runs and its unfairness could not be tied to a cause. Even repeating the measurement on bare metal did not settle those cells. Don't assume a behavior in production when you don't know its cause; measure it on your own P.
Where the comment sits: 64 goroutines on four cores: Mutex is 1.40 times faster than a one-way channel, but its p99 is four times higher -
This is a lesson that looks backwards as much as forwards: which of the numbers you have already published have a second path behind them?
Where the comment sits: 18,750 req/s: precise, repeated, and three times wrong -
Expand-contract is paid for in calendar time: a change like the rename example is spread over three deploys. If the contract step is forgotten, the old column becomes permanent. Opening that step as its own ticket on the same day as the expand step keeps the cost from turning into debt.
Where the comment sits: Changing Schema in Production With Zero Downtime Published in Engineering -
When the gap narrows, the choice of framework is decided less by speed than by how well the team knows it. A measurement like this does not justify a choice, it only shows which candidate to drop. How fast your team can build with each candidate is not in the table.
Where the comment sits: Seven PHP frameworks under identical load: the gap narrows as soon as the request does real work -
The staleness window should not be an engineer’s solo pick. How long a customer may see the old price after an update is a question for the product side to answer. Get that answer in writing: a sentence like “an update shows up within this long” is the contract you can point to before the support queue fills up.
Where the comment sits: Before You Reach for Redis: The Right Cache Strategy Published in Engineering -
If nobody remembers the incident, the process is not yet proven a shackle; the incident may still be reconstructible from records. Doing that small search before removing anything makes the cost of removal visible.
Where the comment sits: When Is Process Armor, and When Is It a Shackle? -
Keep the newcomers’ questions in one place. When the same question keeps coming back, that record can point to the signal on the list that weighs most on your system. When you defend a simplification proposal, it adds evidence from your own team’s questions to the signals in the post.
Where the comment sits: Signals That a System Has Grown Too Complex Published in Engineering -
The real mistake in the story was not Lambda but the word first: the decision was made before anyone looked at the workload. Making a principle the default answers, on your behalf, the question each new service should ask. Keep a default if you like, but write the reasoning again for every service.
Where the comment sits: The Serverless Decision: Cold-Start and Vendor Lock-in Published in Engineering -
Moving a job to a queue can also move its failure from the user’s screen to a place nobody looks at. For every queued job, it should be settled in advance who sees it when it fails and who retries it. Without an answer to that, the synchronous path at least fails where someone can see it.
Where the comment sits: Synchronous or Asynchronous? HTTP or the Queue Published in Engineering -
A cheap way to tell whether a module needs Clean Architecture is to write its rules down without mentioning the framework. If that works, there is a domain worth isolating. If it does not, what you have is most likely a plain save-and-read job.
Where the comment sits: Layered Architecture or Clean Architecture? Published in Engineering -
Sealing the number in advance raises a new question: who closes an invoice that was sealed but never sent, and on what record? That is a business-rule question before it is a code question. Asking it at design time costs less than asking it after the first half-finished invoice.
Where the comment sits: Resolving an Invoice Number Collision in an E-Invoice Integration -
A prefix is a rule the application sets for itself, not a boundary Redis enforces. A redis-cli session or a maintenance script does not know about it. Decide with the reach of the protection in mind, because clients outside the application code are under no obligation to follow the prefix.
Where the comment sits: Namespace Isolation for a Shared Redis Published in Engineering -
Time spent waiting in the queue and time spent running are two separate measures. If waiting grows while run time stays put, look at capacity: worker count or queue separation. If run time grows too, the cause is inside the job. The same complaint that the queue is slow can point to two different places.
Where the comment sits: Why Do Laravel Queues Slow Down in Production? Published in Engineering -
The price of this setup is that the pgbouncer role’s password now opens a door to every user’s password hash: the function returns a hash for any user name it is given. Keep that role’s password apart from your other secrets and put it on the rotation list.
Where the comment sits: Multiple DB Users with pgBouncer auth_query Published in Engineering -
A dependency’s cost is paid not on the day it is added but when its first security patch or version bump arrives. So the question worth asking before adding one is who will carry that upkeep. The standard library often shrinks that question to almost nothing.
Where the comment sits: How Far Can You Go with Go's Standard Library