Just like "if it's stupid and it works, it's not stupid", if you were smart enough to see all the problems in all your past jobs but those companies still went bankrupt, maybe you weren't actually the ideal employee you think you are. And if programming interviews are beneath you and only passed by your inferiors but you can't pay rent, maybe they're not actually so far beneath you.
Using your l33t knowledge of AWS to make the query go from 7 seconds to 40ms or the batch job go from 40 hours to 20 minutes is rarely the difference between a successful company and a failure. Executive dysfunction often is that difference, but if all you do is remember it for your snarky blog post then you're not giving people a reason to employ you.
Wanting companies to be better at sysadminning is good up to a point, but when you focus too much on better database design and AWS cost savings then you're the middle stonemason in that McKinsey parable.
Using your l33t knowledge of AWS to make the query go from 7 seconds to 40ms or the batch job go from 40 hours to 20 minutes is rarely the difference between a successful company and a failure. Executive dysfunction often is that difference, but if all you do is remember it for your snarky blog post then you're not giving people a reason to employ you.
Wanting companies to be better at sysadminning is good up to a point, but when you focus too much on better database design and AWS cost savings then you're the middle stonemason in that McKinsey parable.