Trunk-Based Thierry (they/them)
@tdpauw.bsky.social
most outspoken shy & introverted engineer 🙌 💪
former electromechanical engineer ⚙️
consulting CTO 🤵
founder https://thinkinglabs.io/
former electromechanical engineer ⚙️
consulting CTO 🤵
founder https://thinkinglabs.io/
Reposted by Trunk-Based Thierry (they/them)
There’s also the other way around, where management says they tried OKRs and found that they ‘don’t work’, so you can’t introduce them. So you agree, and instead talk to the team about your ‘goals’ and ‘success measures’ 😶
November 13, 2025 at 8:01 AM
There’s also the other way around, where management says they tried OKRs and found that they ‘don’t work’, so you can’t introduce them. So you agree, and instead talk to the team about your ‘goals’ and ‘success measures’ 😶
I know that 😉
I’ve good ones but as you say they are limited
I’ve good ones but as you say they are limited
November 13, 2025 at 12:39 AM
I know that 😉
I’ve good ones but as you say they are limited
I’ve good ones but as you say they are limited
Me: What development methodology do you use?
X: We don’t follow an agile framework. Instead we practice OKRs.
Me: Oh, well, that’s refreshing! Mind to share your OKRs?
X: Sure. Here they are.
Me: Ugh 😳 … well, that’s not quite how it is supposed to be 😬
X: We don’t follow an agile framework. Instead we practice OKRs.
Me: Oh, well, that’s refreshing! Mind to share your OKRs?
X: Sure. Here they are.
Me: Ugh 😳 … well, that’s not quite how it is supposed to be 😬
November 13, 2025 at 12:38 AM
Me: What development methodology do you use?
X: We don’t follow an agile framework. Instead we practice OKRs.
Me: Oh, well, that’s refreshing! Mind to share your OKRs?
X: Sure. Here they are.
Me: Ugh 😳 … well, that’s not quite how it is supposed to be 😬
X: We don’t follow an agile framework. Instead we practice OKRs.
Me: Oh, well, that’s refreshing! Mind to share your OKRs?
X: Sure. Here they are.
Me: Ugh 😳 … well, that’s not quite how it is supposed to be 😬
With that difference that when people tell they practice OKRs I still give them the benefit of the doubt. With Continuous Integration I’m fairly past that.
November 13, 2025 at 12:38 AM
With that difference that when people tell they practice OKRs I still give them the benefit of the doubt. With Continuous Integration I’m fairly past that.
Reposted by Trunk-Based Thierry (they/them)
I’ve heard @tdpauw.bsky.social talk about this before, and it clicked instantly — totally agree. But every time I share this idea, people look at me like I’ve just declared code reviews are a myth from ancient folklore. 😂
October 16, 2025 at 8:20 AM
I’ve heard @tdpauw.bsky.social talk about this before, and it clicked instantly — totally agree. But every time I share this idea, people look at me like I’ve just declared code reviews are a myth from ancient folklore. 😂
Myeah, I get the same reaction.
Having said, the whole code review thingy starts to be folklore, really 🤷
Having said, the whole code review thingy starts to be folklore, really 🤷
October 16, 2025 at 9:07 AM
Myeah, I get the same reaction.
Having said, the whole code review thingy starts to be folklore, really 🤷
Having said, the whole code review thingy starts to be folklore, really 🤷
Why do Teams think Single-branch Development Does not Work?
thinkinglabs.io
October 16, 2025 at 8:14 AM
Reposted by Trunk-Based Thierry (they/them)
“Anyone who believes code reviews catch bugs, believes in fairytales”
Automated and exploratory tests catches bugs…
Code reviews help lower the risk that we release low quality code.
@tdpauw.bsky.social #agilecam
Automated and exploratory tests catches bugs…
Code reviews help lower the risk that we release low quality code.
@tdpauw.bsky.social #agilecam
October 1, 2025 at 2:43 PM
“Anyone who believes code reviews catch bugs, believes in fairytales”
Automated and exploratory tests catches bugs…
Code reviews help lower the risk that we release low quality code.
@tdpauw.bsky.social #agilecam
Automated and exploratory tests catches bugs…
Code reviews help lower the risk that we release low quality code.
@tdpauw.bsky.social #agilecam
Reposted by Trunk-Based Thierry (they/them)
What code reviews should not be:
* Ways to exercise power - it should be true peer reviews
* Done by seniors missing mentoring skills
* blaming or harming
* a miserable experience
* gate keeping (gates introduce delays)
* a must
@tdpauw.bsky.social #agilecam
* Ways to exercise power - it should be true peer reviews
* Done by seniors missing mentoring skills
* blaming or harming
* a miserable experience
* gate keeping (gates introduce delays)
* a must
@tdpauw.bsky.social #agilecam
October 1, 2025 at 2:29 PM
What code reviews should not be:
* Ways to exercise power - it should be true peer reviews
* Done by seniors missing mentoring skills
* blaming or harming
* a miserable experience
* gate keeping (gates introduce delays)
* a must
@tdpauw.bsky.social #agilecam
* Ways to exercise power - it should be true peer reviews
* Done by seniors missing mentoring skills
* blaming or harming
* a miserable experience
* gate keeping (gates introduce delays)
* a must
@tdpauw.bsky.social #agilecam
Reposted by Trunk-Based Thierry (they/them)
It was two days of interesting talks and workshops, where three stood out to me:
First was “Non-blocking continuous code-reviews, a case story” by @tdpauw.bsky.social
I always enjoy hearing Thierry’s talks. He provides great insight in various ways of getting higher quality code :)
First was “Non-blocking continuous code-reviews, a case story” by @tdpauw.bsky.social
I always enjoy hearing Thierry’s talks. He provides great insight in various ways of getting higher quality code :)
October 9, 2025 at 4:46 PM
It was two days of interesting talks and workshops, where three stood out to me:
First was “Non-blocking continuous code-reviews, a case story” by @tdpauw.bsky.social
I always enjoy hearing Thierry’s talks. He provides great insight in various ways of getting higher quality code :)
First was “Non-blocking continuous code-reviews, a case story” by @tdpauw.bsky.social
I always enjoy hearing Thierry’s talks. He provides great insight in various ways of getting higher quality code :)
Oh thank you, Stephan, for referencing my article ☺️
October 16, 2025 at 7:51 AM
Oh thank you, Stephan, for referencing my article ☺️
Reposted by Trunk-Based Thierry (they/them)
I answered over @ sw-development-is.social/@TheTravelle... ➙ For more about trunk-based dev, I suggest @tdpauw.bsky.social's article thinkinglabs.io/articles/2025/… He wrote more great articles about the topic.
There's even a VCS that doesn't use branches: Jujutsu ➙ jj-vcs.github.io/jj/latest/
There's even a VCS that doesn't use branches: Jujutsu ➙ jj-vcs.github.io/jj/latest/
https://thinkinglabs.io/articles/2025/…
October 16, 2025 at 7:28 AM
I answered over @ sw-development-is.social/@TheTravelle... ➙ For more about trunk-based dev, I suggest @tdpauw.bsky.social's article thinkinglabs.io/articles/2025/… He wrote more great articles about the topic.
There's even a VCS that doesn't use branches: Jujutsu ➙ jj-vcs.github.io/jj/latest/
There's even a VCS that doesn't use branches: Jujutsu ➙ jj-vcs.github.io/jj/latest/
Oh gosh, thank you, Gerald ☺️
October 2, 2025 at 6:52 PM
Oh gosh, thank you, Gerald ☺️