Hacker News new | past | comments | ask | show | jobs | submit
This is why we need to resurrect the neglected git-blame and go back to the days of git-before-GitHub. Way back in the old timey days of 2009-ish, just before the Dawn of the Pull Request, code reviews were seldom. Maybe you’d all get a conference room and talk about architecting some new thing or whatever, but none of this endless nit-picking bullshit that came later. And there were no branch protections, anyone could crap all over the main branch (nee: master) anytime they wanted. Boy, those were some wild times, let me tell ya!

Truth be told, it was the firm hand of the git blame-and-shame that kept our code civil and orderly. Binding contract written in blood was “the name on the blame owns the change”. If you pushed it, you owned it. For life.

Of course, mental health wasn’t so great back in those days, but I would take that over having my PR blocked all day because Chad, who’s only gift is somehow finding a new hill to die on every day, thinks zero is a “magic number” there’s no way he’s going to budge on this issue.

I think what is missing here is that the fight with Chad (not Chat) over whether zero is a magic number or not is a healthy corporation-strengthening process that imbues a sense of

1. Pride in the code we are developing and 2. How the dang things holds together and why this function is important and 3. Some coding guidelines that we can try to follow later (or not)

Thats how companies worked - they argued and talked about and fought over the code and that created the engineering culture that if you were lucky and had a product that made it carried you to your series C

I pine for those days. It was kind of fun hunting down a bug with git bisect (especially after the pain of SVN) instead of just pointing an agent at it. Not to mention ribbing the new hires or underlings for breaking the build. This new-fangled proompt engineering is boring AF.