3 ms·
You're operating in the same company that let this happen in the first place. And — not to take away from the piece – If noone noticed the logs have been garba
by knallfrosch 2y ago
You're operating in the same company that let this happen in the first place.
And — not to take away from the piece – If noone noticed the logs have been garbage for two years, they can't be that important.
- pavel_lishin 2y agoThe logs are unimportant until suddenly they're critical.
- moregrist 2y agoIt all seems easy to fix until you end up in a place where management process (and thus politics) has become more important than outcomes. The people with experience and knowledge get pushed aside in favor of someone who can talk management-speak and (often) looks the role. Suddenly meetings where Things Get Decided only include managers who don’t know what they’re doing. The best is when they make a mess and then get tremendous accolades for half-fixing it. I’ve even seen it happen within relatively small startups. It’s a sign of rotting culture, but sometimes you have a mortgage to pay and have to get comfortable with the situation until you can find a better gig.
- ludicity 2y agoI wrote a piece last year on how they were running a $500K Snowflake bill due to typing one number in wrong, and how I noticed within my first few weeks there by literally eyeballing something and going "queries take milliseconds so you really have to justify everywhere a minute appears in the configuration". The logs are stupid (sorta) but imagine how many other issues can exist if we uncover something like this every time we open something.