Very much sounds like a tech bro wrote it. A lot of these are simply in the wrong place. I feel being “eager to fix what isn’t broken” is a terrible trait on most projects that need to ship. Or at least, terrible if you go forward with trying to fix something that isn’t broken without looping in production first. You have a schedule to keep so if it works, continue forward. The whole article reeks of perfection being the end goal rather than good enough. Every usable technology out there is built off of good enough being the goal. I’ve yet to see a piece of software that shipped with perfection being the goal and actually hitting that goal. More so when you lose that sight of good enough you stop making adjustments to fix things quickly. “Well this button doesn’t work the third time you click it really fast” “Well that’s because our button interface has a specific pop back-up animation delay and we’ll need to rewrite the whole button system interface to become clickable again only after the button pops back up. So let’s put that as the only answer on Jira, slate it will take 3 months, and ignore you could just clear the delay if the button is clicked again as a workaround.”