Insights
Writing about Laravel
Written for people who decide about software without working inside it. No sales language and no half-knowledge.
Changing supplier without losing the application
A handover rarely fails on the code. It fails on credentials nobody holds and knowledge nobody wrote down. Six items and their pitfalls.
Rebuild or repair: what works out cheaper on legacy systems
The answer does not hang on the age of the code. It hangs on whether the domain model underneath still holds. Three routes and what each needs.
Technical debt, explained without the jargon
Why an application needs longer for the same change in its third year than in its first. And how to spot it without reading any code.
Custom software or off-the-shelf?
The decision is rarely made for a whole company. It is made for one process at a time. A grid that helps you tell them apart.
When a spreadsheet should become an application
Spreadsheets carry a surprising amount of weight. Five signs that yours now creates more work than it saves.
What keeps turning up in Laravel audits
The holes are rarely in the framework. They are in how it gets used. Six patterns from real projects.
Why stateless APIs are easier to multiply
Session data in the server process is convenient, right up until the second instance appears. What statelessness actually means and what it costs in discipline.
Laravel versions: when an upgrade really becomes urgent
It is not the version number that decides but the support window. How to work out the moment instead of waiting until something burns.
A subject missing here?
Write and tell us what is on your mind. If the question comes up often enough, it turns into an article.