Code Best Fit vs Best Practice Story as a Senior Tech Bro

This is a story about a senior tech engineer who shares their experience with failed products due to disagreements among developers about whether to prioritize best fit or best practices when building a minimum viable product (MVP).

The story highlights how often there is tension between adhering to established best practices and finding the best fit for the specific needs of a project when creating an MVP. I will be sharing how this tension can lead to unaccountability and arguments among team members, and ultimately result in failed products.

The author also emphasizes the importance of understanding and being patient with knowledge gaps, while also acknowledging that incompetence and unaccountability must be addressed. Ultimately, the story serves as a cautionary tale for other tech engineers and teams about the potential pitfalls of prioritizing best fit over best practices when building an MVP.

[abdulrahmanabdulmujeeb]

hmm... "to write good code, you must have written a lot of bad codes"

[theophilusaika]

Often times when people talk about best practices, they share opinionated views. If you don't seem to adopt their methods or style of development, you are wrong. It therefore means that, what we call best practices are mostly subjective views.