Jesper Ottosen | Comments

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

Great to see these viewpoints collected in one place. There is no one definition of quality - which you choose tells a lot about your current situation and background. Humanistic views, fact-based and socio-technical. One to book mark for future works!

years ago I was part in shipping a backend system update to 80% of the country's internet users, who then couldn't go online. Same story as above, it was first picked up by customer service. and the luckily just a DB fix. but still...

I recently became aware of the CD-holder in the lower frame. To the future indeed!

All the best for your goal. A hobby to try could be jigsaws or puzzles, there's also the Wasgij version that can be fun. Can be combined with podcasts!

Congratulations on your article and welcome to the consulting space. One of the great challenges for this kind of work is that the contracts limits being adaptive. The one I’m starring at have content requirements for the the strategy documents.

“ The absence of unnecessary friction" Stuart Crocker aka @StuC