Jesper Ottosen | Comments

awwh. <3

that reminds me: I’ve seen things you people wouldn’t believe. Browser wars off the shoulders of the millennium, mainframes glitter black-green and management shooting for delivery gates. All those moments are not lost in time, but curated and internalized. ... https://www.ministryoftesting.com/satellites/keeping-track

I remember when we put this together. Thank you for resurfacing ❤️

mostly on the side of dev, while test often is more integrated. Yet struggling with the same issues as us, how to fit into the development flow, tooling and automation and the challenge between what is pragmatic and what would be best.

.. or any other search service really. Qwant (F), Ecosia (D), Mojeek (UK)

Certainly relevant for Staff-level folk's too!

Stagemom ❤️

trackback: https://www.o2sn.dk/2026/03/29/return-of-the-darlings-pets-cattle-and-guids/

as with many other elements: build in smaller batches, built frequently and align often. Especially when dealing with other people, but it also goes for LLM output etc. Align up front. When I prepare large formal documents then I strive to align up front and while doing the authoring. That makes the final approval trivial. ;) Similar to the Japanese concept Nemawashi comes up to explain it.

If we can evaluate more explicitly we can automate more tests. Ideally, as pr DORA research this is best done by developers. Let's call it a new flavor of shift-left :). The test tooling eco system needs to catch up and cover all types of testing - that has been an issue for long already. And for us testing specialist - to see beyond test cases. What is left is still all the implicit and indirect - the narrative to the customer.

Checks out