The Hidden Cost Of Speed

"don't tell me what to do internet moustache man" LMAAAOO

I agree that the critical flaw wasn't making a quick and dirty demo, the critical flaw was not saying hey if we want to do this for real we need to take the time to develop it for real.

The most permanent thing in life is a temporary solution.

00:32 Flip, truly a Godsent editor 08:42 L take, we will not be accepting this slander

00:32 gotta love the heads up 3:44 can see it was true 😅 Added a sponsorblock segment to skip duplicated part 👍🏻

Sounds like LinkedIn fan fiction.

Yak-shaving isn't bike-shedding; it's dependency task completion. e.g. "I want to do X... so I am doing A right now, because X depends on W, which depends on V, which depends on U and T, which depends on..."

Reminds me of the university I used to study at. I heard the IT guys say they had no idea how the system actually worked. It was a big mess and changing anything was a horror because no one understood how the different parts of the system interacted with each other. Anyway, mentioning it because it seems like the "quick patch over quick patch over quick patch ad nauseam" the article was talking about. I think we just need to adapt the speed to the project and how critical it is for business. An internal website has a completely different set of requirements than firmware for medical equipment.

*Don’t tell me what to do internet mustache man*

Thanks for keeping the ad break Q&A in, those of us who spend most of our time on Youtube don't get much Q&A.