3 ms·
I'm sure parquet is the bees knees, and I'm sure if its your code you'll know how to fix it. But what if it isn't your code? And you've never heard of parquet
by rhelz 3y ago
I'm sure parquet is the bees knees, and I'm sure if its your code you'll know how to fix it.
But what if it isn't your code? And you've never heard of parquet before? And its 2AM and they can't get a hold of the guy who wrote it, so they call in you....
- mulmen 3y agoThen there’s a serious organizational failing. Parquet is the de facto standard, the chances are a random engineer knows how to interact with it and not ZSV.
- rhelz 3y ago> Then there’s a serious organizational failing. Man, if your success is predicated on working at a company with with no organizational problems.... A scrappy start-up can't afford to hire multiple, redundant engineers--and what with all of the massive layoffs happening, even at the big companies a lot of engineers are going to find themselves debugging other people's code.
- mulmen 3y agoThen embrace industry standards and don't add unknowns. “There are always organizational problems” is a poor justification for creating more problems.