The distinction is even easier to make these days -- brogrammers aren't actually programmers.
There is an emerging coterie of people whose entire approach to software startups is to vibecode an MVP, raise enough seed to hire a real programmer (or get one interested enough to become their "cofounder") and move on to the next MVP. To them, doing one company at a time in the era of LLMs is a sucker's game.
I fell into this career because I programmed as a kid, hacked on pre internet bboards, and understood how to drive a computer via the command line. I like solving the problems. GED, college dropout. I never planned on making this much money, but I'm certainly not giving it up. I don't feel like I fit in either camp tbh.
To the best of my knowledge zero of the people passionate about programming that I know have spent a meaningful portion of their career at non-tech companies. Internships or first jobs out of college are common, but the passionate people end up going somewhere where the thing they're working on is more than an incidental cost center for their employer.
I'd guess it makes sense that if programming is a passion for you then probably a non-tech-centric F500 company probably isn't where you'd choose to work.
For context: my current company with ~400 employees (not just engineering) is the largest company I've ever worked at.
Sure, and that's a big shift in industry culture over the last several decades.
While there had long been perfuctory white collar programmer analysts filling the ranks at some dry divisions at IBM, it used to be way more common to have a software engineering department full of Asimov-steeped Omni-reading nerds who had genuinely passionate interest in the field that had taken hold even before they started working in it.
But later the career increasingly came to be treated more like law, medicine, or finance and you started to see those rooms fill with people that were often generally bright but not really "called" to the field in the same aay.
I wonder if carpenters, plumbers and electricians, etc have the same kind of love for their jobs in comparable ratios.
I certainly don't ask when I hire one.
I mean I got into it because I loved it as a kid in the 80s and 90s. And I still loved it in college. Turning it into a job quickly crushed any love I had though.
If you don’t have style rules baked into the PR process, you should. Tabs vs. spaces is a team decision and needs to be matched by everyone to reduce code churn. It’s correct to reject a PR if it violates the team style guide (although it should be automated and have tooling locally to enforce it as well.)
I worked for twitter and there was a guy like this. I made a big stink that "yo, everything this guy says just needs to be in a linter" and they actually implemented it.
