Ha yeah “Sr dev” was never seen again, the team member stuck around for quite a few more years.

Once we had a “sr developer” join a project from a consulting group. The project wasn’t going well so me and another dev started helping with some tasks as well.

After a couple days of helping, trying to get his web application to work with data from an API he turns to us and says “oh, json is just a string.”

The other developer from our team stared at him for a few seconds, stood up, walked out of the room and told the project manager something along the lines of “if that guy ever comes back in the building I’ll quit”

So yeah, json is just a string… But if that’s the end of your knowledge you’re in for a bad day.

So using react will get you fired? I knew it!

I’m ashamed… It’s simply “bump deps”

Did I also touch some code and tests connected to dependency updates. Yes.

Did I document any of that? No.

Did I spend more time writing this comment the thinking about the commit. Most definitely.

Will I be bisecting to this commit after our next deploy and cursing at myself? Probably.

It sounds like a joke but as another senior dev, one of the big lessons I’ve learned is getting really good at capturing all the requests that come in and who approved them.

It’s a bit of cya, but mostly so I can say “I can change that but it’s not a bug. It’s what was requested for this to do last year. Here’s the discussion” It’s surprising how often that results in “Oh yeah, that was for x. Let’s not touch it.” Or “oh that’s not a quick fix, let me come back with more information” etc

Array(16).join(“wat” - 1) + " Batman!";