Re:Drunk Post: Things I've Learned as a Sr Engineer
by daenz on Sunday May 30, 2021 @11:51AM
(#27334073)
That hurt me to read! Have you communicated this to your manager? Might be worthwhile to have a decision "from the top" that is essentially: all logging is good, so long as it doesn't hurt performance or contain PII/PHI.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by sharken on Sunday May 30, 2021 @12:03PM
(#27334162)
Logging is like a lamp in the dark, you need it.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by knighthack on Saturday June 12, 2021 @11:48PM
(#27489589)
I love how poetic this sounds.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by josephorjoe on Sunday May 30, 2021 @12:11PM
(#27334228)
three things i find to be true of every web app i work on:
1. good logging is the most important part of the app. whatever the app is meant to do is secondary. the app should be a logging app first, and then a backend service to sell widgets second.
2. assume performance requirements for request latency and transactions per second will be at least 3x whatever the product owner tells you at the start of the project and plan accordingly. never trust any suggestion that you can 'ignore performance for now'.
3. the UI may be more important than logging
Re:Drunk Post: Things I've Learned as a Sr Engineer
by swader999 on Sunday May 30, 2021 @12:29PM
(#27334368)
Logging at the boundaries or seems is especially helpful.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by fighterpilot on Sunday May 30, 2021 @01:15PM
(#27334752)
Can you elaborate on what you mean by a boundary? You mean logging the interface between two services or modules?
Re:Drunk Post: Things I've Learned as a Sr Engineer
by mikepurvis on Sunday May 30, 2021 @01:23PM
(#27334817)
Boundaries between anything. I recently was dealing with an issue in a Jenkins pipeline, where I didn't realise that state was being serialized to string form between job stages until I explicitly logged it out. The thing that was a list in the previous stage was suddenly a string, but then Groovy would happily accept the join method on a string because it's still an iterable. Auuugh.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by swader999 on Sunday May 30, 2021 @01:31PM
(#27334890)
Both these above are great answers. It's a bit of an art.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by eps on Sunday May 30, 2021 @01:42PM
(#27334975)
Should've put it into a branch and added an one-line comment to that effect to the master.
Re:Drunk Post: Things I've Learned as a Sr Engineer
by BurningFrog on Sunday May 30, 2021 @02:56PM
(#27335590)
A better approach is usually to write test covering all edge cases.
someone then removed all of my logging because it was ugly.
and then had to put it all back in when another bug was coming from the same terse beautiful code.