Articles like this are a good wake-up call, but I'm sure the author would be saddened to see this become Dogma.
I've been recently reflecting on a startup that encountered ~2 lost years due to too much "move fast and break things": I just think teams just need rationale discussions about the trade-offs at every stage, and to come to a close-to-concensus. Easy to say, hard to do.
All things software & product, honestly - FrontEnd, BackEnd, DevOps, ML - as long as we're solving massive problems.
My code is used by millions of users globally - Potatoes make me happy
You're not wrong in saying that sometimes building at velocity without discussing the repercussions can hurt and sometimes even kill a business (has happened to me)
I think if anything I'd like people to take away from this is to be more outcome driven than feature driven. This can translate to faster dev, focus on customers or move fast/break things. In the end, as we all know - in startup land pace is everything (unfortunately), pace to build until you hit PM fit and then pace to maintain what you've built
I've written about refactoring and rebuilding your code. And if it's necessary to do so, it needs to be done.
Again you're not wrong 😀 and I'm glad you raised this comment!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Articles like this are a good wake-up call, but I'm sure the author would be saddened to see this become Dogma.
I've been recently reflecting on a startup that encountered ~2 lost years due to too much "move fast and break things": I just think teams just need rationale discussions about the trade-offs at every stage, and to come to a close-to-concensus. Easy to say, hard to do.
Hey @coolman!
You're not wrong in saying that sometimes building at velocity without discussing the repercussions can hurt and sometimes even kill a business (has happened to me)
I think if anything I'd like people to take away from this is to be more outcome driven than feature driven. This can translate to faster dev, focus on customers or move fast/break things. In the end, as we all know - in startup land pace is everything (unfortunately), pace to build until you hit PM fit and then pace to maintain what you've built
I've written about refactoring and rebuilding your code. And if it's necessary to do so, it needs to be done.
Again you're not wrong 😀 and I'm glad you raised this comment!