Sorry but the biggest myth in design systems and in digital products more broadly is that something is always better than nothing. “Just get it out there and we can iterate” will be the death of me I swear tg
Comments
Log in with your Bluesky account to leave a comment
I do agree to be fair. It’s just that a lot of the time I think it’s a something for something’s sake - delivery in and of itself has no inherent value. There’s an orders of magnitude thing here of course.
You’re not wrong. I just have a particularly big chip on my shoulder about some roles expecting to be or positioning themselves as the better angels of what’s nearly always a madhouse.
Why? Agile Manifesto is pretty clear that working software that meets immediate customers needs should be shipped. These are requirements, not options.
Of course. It's "if a tree in the forest" type of problem. Software is nil without users. Also, Agile approach got bastardized through all mutations, so it is useful to go back to principles. They were written by people who loved to work directly with customers to solve their needs. So simple.
Sprints are the real focus of my ire. Everything so easily seems to shift into a mindset of delivering things purely for the sake of having evidence that work is being done and actual important maintenance tasks are endlessly backlogged
Comments
Me …dies of natural causes an old man waiting for the next phase
Mainly, I don’t believe that doing nothing is ever really a viable option for a team in a commercial organisation.
Hope you’re well, been a while.
Hope you’re well too! Happy new year etc 🥳
Let it all burn.
Launching a product that's 'broken' can destroy trust/confidence in whatever comes next (even if it ends up close to perfect)
Sprints are the real focus of my ire. Everything so easily seems to shift into a mindset of delivering things purely for the sake of having evidence that work is being done and actual important maintenance tasks are endlessly backlogged