Hacker News

Favorites Setup
Comment by jghn | original | A family tree of software job titles
[−]jghn · 2026-11-14 Sat 22:56 UTC · link
> So jack of all trades master of none?

Why does the ability to interact with users, being able to test code, profile/debug code, and actually manage your deployed software imply you're a master of none? Too many developers act like it's a good state of affairs that they just get locked in the basement to grind the code. And now that we have tools that can grind code for you, they're finding out why that wasn't a good state of affairs for them.

The answer is master all of them, not none of them.

[−]ravenstine · 2026-11-15 Sun 07:36 UTC · link
Most people aren't particularly good beyond 1/3 of those domains. It's delusional to expect everyone to be Superman even though that idea is amazing in a vacuum.
[−]999900000999 · 2026-11-15 Sun 09:24 UTC · link
Everyone now needs to be full stack and experienced with dev ops , cicd too. Maybe you’ll also be forward deployed so you can gather client requirements, implement them, test, and deploy the whole project.

I’m seeing contracts with twice as many required skills for about half of what I was making in 2019.

[−]nkmnz · 2026-11-15 Sun 10:49 UTC · link
Wait until you hear that some employers might expect that you take a car or public transportation to the office, all by yourselves. I mean, come on, you're not a mechanical engineer or public transportation policy expert, how should you do that. Driving a car or taking a bus are skills that cannot be acquired in a couple of hours. Those are crafts that rely on wisdom of generations, passed on only from father to son. Just like taking care that the new image compression that you've implemented for your company's "Not Hotdog" app doesn't break production. How dare they asking you to write an e2e test that plugs into the existing test runner, and add the creation of required artifacts to the existing CI/CD pipeline.

If someone expects a non specialized developer to create a CI/CD pipeline for a brownfield project from scratch, or implement a test strategy including runner infra etc., then that's not DevOps. It's just stupid.