Software technologist
The Netherlands
Joined January 2009
- Tweets4.7K
- Following304
- Followers257
- Likes1.3K
Stefan Holdermans retweeted
Get your ticket for Devopsdays Amsterdam 2024 now and save! Spend 162 Euro instead of 215, or 195 instead of 289, if you wanted to do workshops as well.
Take me to Early Bird NOW: devopsdays.org/events/2024-a…
Stefan Holdermans retweeted
It is our great pleasure to announce that we have hired a new Executive Director for the Haskell Foundation: José Manuel Calderón Trilla! #haskellfoundation #haskell
Learn more:
discourse.haskell.org/t/welc…
That anxiety when you pick up a piece of code after a long time again. I need to make a change but I’m holding back. So first I do some tiny refactorings, just to regain my confidence in the tests. And, yes, then it comes back—and all is good.
From a PL design perspective, Python is, imho, a terrible language. 😱 But its ecosystem—the vast amount of libraries available for pretty much anything you can think of!—makes it hard to compete with as a scripting language. 🤔 May be the right tool for what I want to do today.
Stefan Holdermans retweeted
Hey Twitterverse, I've created a self-paced version of my TDD for [Embedded] C training course. Do you have any ideas how I could get the word out to developers that could benefit?
- “I’m building a software team.”
- “Ah, I see. Then you need a Scrum Master.”
- “No, I don’t.”
- “Sure you do.”
- “What do I need a Scrum Master for if I’m not going to do Scrum?”
- “…”
Here’s two cents. Imo “Product Owner” should not be a job title. It could be a role, a very important one. But: I don’t think we should call that role “Product Owner” as that name is tainted so much by Scrum that I think it’s well beyond repair.
This conversation had a profound impact on me. It broke my heart. I suppose, over the years, I have become quite cynical about most implementations of what people believe or claim to be “Agile”, but this was beyond just ignorance and well underway towards plain evilness.
If we prioritise form over matter and insist that only a one-size-fits-all approach to software development accounts for “scaling” (whatever that means), then we deny ourselves the possibility of picking the approach that best fits the team and the circumstances.
Until yesterday, I’d never heard of the term “seagull management”. Then, at #GOTOams, @bjschrijver coined “seagull architects”: they’re usually out there, high in the sky, but occasionally they take a dive and come down to sh*t on you (and steal your fries, too).
μservices, μteams. It’s all about small, smaller, smallest in @aahoogendoorn’s keynote at #GOTOams. Works at scale.
@aahoogendoorn This reminded me. Are you familiar with @GeePawHill’s Many More Much Smaller Steps (MMMSS)? geepawhill.org/series/many-m…
.@dylanbeattie’s closing keynote at the final day of #GOTOams: “Failure is always an option”, many times a very viable one even. A plea to give way to the creativity of your users and have them make good use of your software—in ways that you never could have anticipated!
@bjschrijver at #GOTOams on the tension between optimising for reuse and striving for loose coupling. As always, software design is all about trade-offs. 1/2
Drawing a distinction between “positive” and “negative” stakeholders, and the trade-odds that emerge from balancing their concerns. 🤔 From @eoinwoodz’s talk on democratising architecture. #GOTOams