2 ms·
This reads an awful lot like post-how justification of poor business practices. It’s got a bit of”uhhmm actually, poor management and high turnover is good act
by FridgeSeal 3mo ago
This reads an awful lot like post-how justification of poor business practices.
It’s got a bit of”uhhmm actually, poor management and high turnover is good actually” vibes, which is then (over)extended to a kind of carte-Blanche justification of “why using kms and having no idea of what’s going on” is good-and-desireable.
Which is like, certainly a take, and I can think of at least one “technical skills hating” exec from a past life who’d read this and foam at the mouth to feel justified in their decisions to try and throw all engineering practices out with the proverbial bath water.
- incrudible 3mo agoI read it more as pointing out the inevitable and accepting the implications. You can not call it the result of poor practice when every business beyond a certain size has this problem. Perhaps the problem could be mitigated by keeping the company itself small, but that has nothing to do with programming anymore.
- deleted 3mo ago[deleted]