zlacker

>>gsky+(OP)
I get what he's trying to say, but the danger is people (especially management) getting the wrong impression. The risk of "move fast is good" is that it becomes hustle culture where people rush under deadlines and eventually burn out. There are plenty of occasions where slowing down and being thoughtful is beneficial. Often stopping focus is what gives eureka moments as the other side of the brain starts churning once new input ceases. There's a reason the cliché story of your best ideas happen on the toilet or in the shower are a thing.

It's like people reading Radical Candor (which I quite like) and concluding that being an asshole is ok.

>>hylari+g5
I am all in favor of continuous development. Program. Check-In. Build. Test. Merge to dev. Build. Test. Merge to master. Build. Test. Deploy. I have a very fancy Play Button, that does everything automatically.

But it always takes like half an hour. :))

I usually start then something else. I have many projects open. But its like....these context switches, they are draining.

So yeah, i like to go the dangerous part, deploy right away from my dev machine. But i get immediate reaction. I dont have to wait. But my mates dont like it. And so i deal with it.