What's the advantages of moving slow and fix things? The author mentioned he moved slow for his existing open source projects and non-profits over 15 years. Why not distil some lessons about what moving slow means and what life experiences he went through to put forth this perspective...
Half of it was just ranting about vc culture and Paul Graham...
The hustle culture the author mentions reminds me of my time in big tech. It was an endless search to unlock growth for the sake of career progression, monetary gain, corporate infighting, etc.
I believe there exists an alternate approach which appeals a lot more to me. That is a slower pace of fewer but more polished capabilities. Refining a tool instead of expanding it. Appreciating what’s there instead of chasing something that’s not.
Many products deserve to be “done”. But that’s rarely the case in high tech and I’m not sure most people could answer the 5 whys of why it’s not “done”.
If it isn't broken don't fix it is not an inherently bad way of operating despite what Big Tech would have you believe. Move fast and break things has for at least the last decade been accompanied by the hidden rejoinder of "and I'll fix the problem I created by breaking things, but only sort of, in a way that financially benefits me and fucks everyone else".