And google, please stop showing ads for products I already bought. Or worse: for better and cheaper alternatives! :)

Which one did you read?

If I change a red test, by default I simply rerun it. Easier than having to think if it's needed. Maybe pure refactoring (using IDE refactoring tools) might be a counterexample, but since most tests are so fast, maybe I'll again save the trouble of having to think. And to minimize diff btw runs.

Although misleading in the name here, half-closed ranges are almost always the most pragmatic choice, and closed ranges easily lead to complications. For example workshifts of nurses: the same value ends the previous shift and starts the new one. No worries of overlaps there, either.

Yet another point against microservices.

Atlantic Archipelago? Always learning new concepts. Until now I knew Great Britain, British Isles, United Kingdom, Commonwealth Countries, ..erm there may be more.. I'm sure there is more. Greetings from Finland. Just Finland. :)

I'm sure they'll resume the apathy when the limits of this newest "silver bullet" become obvious. Many did try the older ones, too, but without really investing in learning their own responsibility. LLM may get them a bit further, but the hangover will be all the worse.

Still, I believe, those same people so over-eagerly believe LLM, a tool, will make their jobs easier & faster.

Quantity over quality. Human wave (meat wave) attack even. But given no context I may be way off.

I just recently found out that the inevitable "unsolvable problems" are the key. Give the desert all the time to solve one their way. WHEN they fail, solve it the forest way, present the solution with a prepared tutorial of what why and how. It would take a dedicated desert fan to oppose this start.

I know the feeling, but I don't know a word for it, especially not in German. As a Finn I'd describe it as sähköpyörätasoitus, electric bike handicap. Or maybe sähköpyörätekosyy, electric bike excuse.

I have found blackbox (mostly happy path) tests to be safe enough to proceed with making server code testable. The biggest problem is automating configuration and bootstrap. Both often overlooked neglected and overly complicated feature epics.

Troy

Ah, is it the third revolution on the wheel of reinventing Continuous Integration, or have I lost count? (And no, I'm NOT talking about a server but about a practice.)