News for hackers. Stuff that matters.
Re:Programmers Should Plan for Lower Pay? by amelius on Sunday December 29, 2019 @10:28AM (#21906346)
I think, therefore, we should try to use different labels for different kinds of developers as much as we can.

E.g. "software engineer", and "programmer" should be labels for different roles/capabilities, as should be "computer scientist". Using the terminology incorrectly should be frowned upon, similarly to how this goes in other disciplines.

Re:Programmers Should Plan for Lower Pay? by pjc50 on Sunday December 29, 2019 @11:53AM (#21906885)
As jefftk's comment says, the field is too .. protean and ill-defined to do that. We can barely agree on "frontend" and "backend". There used to be separate "analyst" and "programmer" jobs, enshrining that would have prevented a whole load of efficiencies.

It's also why there's so much difficulty in bringing wages down by just training more programmers: it's much harder than it looks. Teaching people to program is far more unreliable than other disciplines; the degree of self-starter on-demand continuous improvement required is very high. Other professions (e.g. actuary) may have a big hill to climb, but the requirements are written down and there is a clearly marked path up the hill. In software you may wake up to find that someone has moved the entire hill during the night and you have to make your own path, again.

Re:Programmers Should Plan for Lower Pay? by jefftk on Sunday December 29, 2019 @10:59AM (#21906518)
I'm not sure the field is mature enough yet for us to be splitting things up like that. I've worked in performance critical code, research science code, website optimization, ads infrastructure, browser testing, experimentation frameworks, dumbphone mobile payments, and other things, in C, C++, Python, JS, Bash, and Java. Most of my coworkers have a similarly wide range of experience.

These have a lot of core skills in common, both hard and soft, but it's such a mishmash of things that trying to impose precision via labels doesn't seem helpful to me.

Re:Programmers Should Plan for Lower Pay? by deadmutex on Sunday December 29, 2019 @11:34AM (#21906746)
Perhaps this is due to the location where you work.
Re:Programmers Should Plan for Lower Pay? by pjc50 on Sunday December 29, 2019 @06:55PM (#21909535)
Similarly in the UK I have done bits of everything from IC design, IC design software, ARM assembly, webserver (Zeus), network engineering, sysadmin, web apps, Windows CE, and even some actual soldering. Small companies are great for this.
Re:Programmers Should Plan for Lower Pay? by jefftk on Sunday December 29, 2019 @01:06PM (#21907350)
I'm in Boston, and more than half of the above were while working for a single company (Google)
Re:Programmers Should Plan for Lower Pay? by tomphoolery on Sunday December 29, 2019 @01:18PM (#21907418)
This! I think Rob Pike said it best in his initial talk about Go: there are two kinds of developers...programmers, and engineers. programmers want to build things, engineers are constantly monitoring and maintaining existing structures. the terms "builder" and "gardener" are also used in this context, but I always felt that the classic usage of "engineer" was someone who would maintain, monitor, and keep systems alive...whereas a programmer is tasked with building that system in the first place. Not saying that programmers shouldn't be responsible for the correctness of their own work or anything, nor should engineers never build anything from scratch, it's more a matter of your preference and what you personally like to do in your job.

But what is a "computer scientist", really? Is it just some theorist who sits in an ivory tower and tells us all what to do? In my opinion, a "computer scientist" can actually be either a programmer or an engineer (or maybe have both in their blood? who knows). It's someone who is less concerned about building things for today, and more concerned about how computers are going to work tomorrow. It's a wholly separate role from us "construction workers" who have our boots on the ground and are actually building things...the scientists are concerned with how we're going to build things tomorrow. I don't know if Rob Pike, Robert Griesemer, Ken Thompson, or Russ Cox still work on actual systems code anymore or whether they just figure out how to improve the Go language, but assuming that they only work on Go full-time, that to me is the role of a "computer scientist", though for example Ken Thompson is also a "programmer" because he likes to build things.

Re:Programmers Should Plan for Lower Pay? by nnq on Sunday December 29, 2019 @01:52PM (#21907645)
...except that people tend to use there words with reversed meanings too :| If a programmer wants to sound fancies he/she uses the term "software engineer".

Also, separating "building" from "maintaining" (when "maintaining" means more than running / scaling / securing, and also includes adding features) is a a recipe for disasters! The builders/creators start creating unmaintainable messes because it's not their job to maintain them.

I don't think these kinds of distinctions help in software... we need different ways to look at the problem...

Also this lack of separation is kinda what makes software dev a cool field to work in... I love the hacker mentality and if it ever fully dries out I'm gonna quit working in this field and move to a fresher/younger one.

Re:Programmers Should Plan for Lower Pay? by analog31 on Sunday December 29, 2019 @11:24AM (#21906669)
Most people with engineering titles are primarily busy creating whatever represents "glue code" for their particular field. Most white collar work is like the saying about dissertations in the humanities: The transfer of bones from one graveyard to another.