#TestEngineering-Advocate and Facilitator, loving Agile & self-empowered teams. Scouting for tech trends and still have time for Charleston SwingOuts + ModSynth
I’d lose all respect for myself if I chose to lay people off or fire them during the holidays.
Leadership is about doing what’s right by your employees as much as it is hitting quarterly goals. This behavior is repugnant and shameful.
I wrote about my journey of testing Machine learning based system. It's been a long way, finally published at
@InfoQ :)
https://t.co/tNukfXKOce
Hope to motivate others by sharing my learnings, challenges and opportunities ☺️
@BenLinders@rahul_verma Thanks for the review.
Here's a Wardley Map on Prompt Engineering, showing the components and skills that are needed [draft].
You can find the source for the Wardley Map here, https://t.co/f9HQviraks #WardleyMaps
“How long does a 2-point story usually take?”
“We peg story points to half-days so 2 points is one day.”
“Yes, how long does a 2-point story usually take?”
“One day.”
“Historically, or ideally?”
“One day.”
“Most of the features you released are over 40 days old.”
“But, um….”
One of the most profound lessons I've learned in my 20 years of working in software product delivery is the importance of TESTABILITY.
High performing teams are obsessed with TESTABILITY.
To better explain Testability I've created model I call the "10 P's of Testability"
Releasing a big thing with bugs brings in potential customers who try it for a few days, delete it, & never look at it again.
Releasing a small bug-free thing that does something truly useful brings in actual customers, who stay and help you improve it incrementally
Your choice
Sie stören die öffentliche Ordnung, den Verkehr, den Flugbetrieb.
Man nennt sie Terroristen.
Sie machen Fackelzüge, üben Gewalt wegen der Maskenpflicht aus, zünden Asylheime an.
Man nennt sie besorgte Bürger.
Nur falls mal wer fragt, wann wir falsch abgebogen sind.
Test-after:
1. Write code
2. Write tests (green)
3. Change tests to make them red
4. Change tests back to green
5. Change the code to make tests red
6. Change the code back to green
7. Refactor
Test-first/TDD:
1. Write tests (red)
2. Write code (green)
3. Refactor
Das Wesen des Kulturkampfs ist es übrigens die Probleme, die man so mutig aufzuzeigen vorgibt, überhaupt nicht lösen zu wollen.
Es geht nur darum ganz niedere Emotionen zu bedienen und am köcheln (eigentlich am überkochen) zu halten. Don‘t fall for it.
The pro-estimate people say "my client won't invest in the software unless I can provide a cost up front." That's not investment. That's a purchase of something that doesn't exist. That's like saying "I'll invest in your stock only if you can give me a guaranteed return." →
Do you struggle to code after a meeting? In the morning? Do you struggle to pay attention to a meeting after a deep work?
We know that context switching is costly but we rarely talk about how we can be more interruptable.
Here's a simple interruptible workflow that you can try:
The reason we can't switch off, or focus on meetings after deep work, is because of the Zeigarnik Effect; the tendency to occupy our working memory with unfinished tasks.
Writing activity tricks our brain into forgetting the unfinished tasks, circumventing the Zeigarnik Effect.
The Agile Manifesto captured what people were already doing, sometimes for years/decades. It is not theory. Worth thinking about, especially if you're in the "it can't work in the real world" camp. It did (and does) work quite well in the real world, thank you. Always has.