Australis13

As the senior dev, please don’t.

Definitely the latter.

We work in protoduction.

Nope, just inherited a colleague’s codebase when they left. It’s years later and I still haven’t sorted it all out.

As someone who has inherited code like that, I would like to strangle the first programmer in the comic.

Make sure it’s not whitespace sensitive and requires explicit typing, just to mess with everyone.

Ouch.

I have actually encountered those sort of potential differences between ground planes. They can indeed wreak havoc under the right circumstances.

I can’t decide whether to laugh or cry.

I think it’s just that we’re possessive/protective of “our” code, even more so if one is passionate about programming. We’ve put a lot of effort into it, then somebody else comes along and “ruins” our “perfect” (to our eyes) formatting/styling!

Some linters can do both. Getting one set up as an automated job whenever code is pushed to the repo is on my TODO list…

I felt that. I have a colleague whose coding style is different to mine and whenever they work on code that I originally wrote, I have to resist the temptation to modify things to camelCase.