Sebastian Stautz

@SebastianSolidwork
18 Followers
12 Following
576 Posts
☯️🕊️☮️FIX THE SYSTEM!🛠️
Testing, Ludo, Economy🧭
Problem Scout since '08🔬🔭📢
Multi-disciplinary people connector
👨‍👩‍👧‍👧🌐🇩🇪🇬🇧🤘🥋🏹🤺 ENFP
Websitewww.enteresc.net
@nobsagile The only monetary incentive for me is having enough money for my family.
If not I'll look for another company.
Inflation + no raise = sucks
@nobsagile 😭I will be there again soon.
@krisbuytaert Only the short-term costs are going down. Long-term AI will cause way more problems than we solve by it.
And what you said.
@captainfutura Sollen sie doch! Dann werden sie wegen Wegzugsbesteuerung endlich (höhere) Steuern zahlen!

🔴 👁️ - "Das Aussetzen der Vermögenssteuer hat uns bisher locker dreihundertachtzig Milliarden Euro gekostet. Zeitgleich sind seit 2001 die Vermögen der hundert reichsten Deutschen um 460 Milliarden gewachsen."

via Philip Simon

Quelle:
↪️ ▶️ https://www.ardmediathek.de/video/mitternachtsspitzen/mitternachtsspitzen-maxi-im-dezember/wdr/Y3JpZDovL3dkci5kZS9CZWl0cmFnLXNvcGhvcmEtMmJkZDFmZDAtMjExZS00NzJmLTkxZDYtMTZjMTE1M2Q2Y2Rk

#TaxTheRich #Umverteilung #Vermögenssteuer

Organisational Dysfunction of the Day

DORA, the wrong way round

Context: The DORA metrics have become the gold standard for measuring engineering performance. Deployment frequency, lead time for changes, change failure rate, and time to restore service. The four key metrics. Teams build dashboards around them, set quarterly targets, and run improvement initiatives to move the numbers in the right direction. Some teams genuinely improve, while others find the numbers are stubborn or that improvements one quarter quietly reverse the next. Leadership concludes that the teams need more discipline, better tooling, or another round of training. What gets called cargo culting (for lack of a better term) in the industry, copying the visible practices without the underlying conditions, is exactly this pattern.

OST explains: DORA was designed as a research instrument, not as a target system. The metrics are downstream signals of healthy delivery, not the drivers of it. Healthy delivery is when self-managing teams own the whole product, make decisions without escalation, and have tight feedback loops with the people they serve. Take those structural conditions away, and the numbers regress, no matter how many dashboards you build. Treating DORA as a goal in DP1 (bureaucratic) is exactly the goal displacement Goodhart warned about: the moment a measure becomes a target, it stops being a good measure. In DP2, the self-managing-group structure, the same numbers emerge naturally as side effects of work well done. You do not need to chase them. You need to build the conditions that produce them.

#OpenSystemsTheory #SocioTechnical #OrgDesign #DevOps

@nobsagile Depends on the context. This might be it's original by its tech founders. But business often cracks down on it.
At the very least it's about iterations and the question is if you use them for learning or just breaking one big waterfall into multiple smaller ones.
@nobsagile Sorry Thomas. By that you refered to the ambiguous "tests".
If you want smaller stories, how do you want to improve the automation as well as the exploration?
What are your referring to?
Ambiguous phrases in testing

I see many people using at least one of these phrases … test(s) case(s) test case(s) scripted test(s) scripted case(s)…

EnterEsc by Sebastian

@nobsagile It's very ambiguous and can be misleading.
And it's an industry-wide problem.

I guess you refer mostly to automation?
When then just stopping there? Why no better, deeper exploration?