Your Software Passed Testing. Why Did It Fall Over on Launch Day?
A system can pass every test with empty data and one user, then buckle on launch day. Here's why realistic performance testing matters and what it should cover.
Insights
Practical thinking on business systems, automation and software built around the way organisations actually work.
A system can pass every test with empty data and one user, then buckle on launch day. Here's why realistic performance testing matters and what it should cover.
A search box is one of the most requested, least specified features in any brief. Here's why the naive version breaks down and what real search actually needs.
Paying for something you can't see until it's finished is a real worry. Here's how I let clients watch a build take shape, and what to ask any developer about it.
A failed API call that retries too eagerly can knock over the very system it's trying to reach. Here's what a retry storm is and how sensible automation avoids one.
Most businesses assume backups work until the day they need one. Here's what 'we have backups' should actually mean, and the questions worth asking before that day comes.
Blocking AI training crawlers and staying visible in AI-powered search aren't the same setting. Here's how the crawlers actually differ, and what to check on your own site.
Chat tools can turn a spreadsheet into a chart instantly, but ask the same question next month and you might get a different answer. Here's why that matters for business reporting.
The Chess.com leak wasn't a hack, it was scraping. Here's what that means for any business running a platform with user profiles, listings or public-facing data.
The John Deere right-to-repair story is really a story about who controls the software your business depends on. Here's how to check where you stand.
Got a problem worth solving properly?
Tell me what's slowing your business down. The first conversation is free and straightforward, and it's with me, not a salesperson.
Or email me at josh@thackr.co.uk