News for hackers. Stuff that matters.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by mevile on Wednesday September 21, 2016 @03:23PM (#12551375)
Wherever this guy has worked is where I never want to work. If people can't appreciate the value your engineers create then that's not a place to work. If this guy's advice applies to your job, get a new job. I'm not going to work at a place where I'm worried about "attaching myself to the company's profit center" and other bullshit and I've been a happily employed programmer for 9 years now.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by codingdave on Wednesday September 21, 2016 @04:07PM (#12551764)
I've done the startup thing. I've done the corporate LOB thing. They both can be great, they both can suck. Frankly, it mostly depends on your boss.

But the point of the article is to not pigeonhole yourself. Don't be that guy who wrote that library, or the guy who maintains that app. Be the guy who brings value to the business. Be the guy who is considered an asset no matter what role they have, because you are working towards the goals of the business. Be the guy who knows when to say, "Yes, I can code that, but we can buy it just as cheaply, and let me focus on more important details of our business."

Re:Don't Call Yourself A Programmer, And Other Career Advice... by mevile on Wednesday September 21, 2016 @04:43PM (#12552042)
> Yes, I can code that, but we can buy it just as cheaply, and let me focus on more important details of our business."

Uh no. I code, that's what I do. I'm fine with being laid off if that's not creating value. I can code somewhere else.

If you go into a non-engineering role, you are sacrificing your engineering career for temporary survival at your current job. The next engineering job you apply to wont probably like that you haven't done SWE work for whatever amount of time. Just pull off the bandaid and get a new job.

I'm an engineer. I want to be good at engineering. I'm not interested in the rest of it. It's not my job to make sure the engineering tasks line up with business success. My job is making the math and the code work. Division of labor. I don't want any other role. If engineers aren't valued I'll go somewhere where they are. There are lots of engineers creating value all over the place. There's lots of opportunities out there, there's no reason to have to sell yourself if your skills don't.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by redwards510 on Wednesday September 21, 2016 @04:57PM (#12552169)
While I certainly sympathize with this attitude, these days I simply can't afford to think this way. If all I do is write code from a spec, what separates me from the millions of other 10x cheaper coders offshore? My native English skills?

As an engineer it's easy to think "yeah, well I write good code.." but in my experience you will never be able to adequately demonstrate that to a potential employer during the interview process.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by throwanem on Wednesday September 21, 2016 @05:49PM (#12552574)
> I want to be good at engineering. I'm not interested in the rest of it.

Being "interested in the rest of it" makes you a better engineer. Indeed, there's an argument to be made that that's part of what makes you an engineer.

How do you know whether you're creating value if you don't care to know what's valuable? How do you expect to be able to make yourself worth hiring if you don't know and won't learn how to make your paycheck worth signing? How do you intend to build tools that make people's lives better if you can't be bothered to understand what they need?

Re:Don't Call Yourself A Programmer, And Other Career Advice... by mevile on Thursday September 22, 2016 @04:24PM (#12560055)
Being interested in the rest of it creates problems because you're getting involved in domains you don't have any expertise in.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by throwanem on Thursday September 22, 2016 @05:50PM (#12560631)
There's a difference between paying attention and meddling.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by perfectfire on Wednesday September 21, 2016 @06:36PM (#12552871)
> Uh no. I code, that's what I do.

If all you do is code I wouldn't consider you an engineer.

> Engineers design materials, structures, and systems while considering the limitations imposed by practicality, regulation, safety, and cost.

Re:Don't Call Yourself A Programmer, And Other Career Advice... by mevile on Thursday September 22, 2016 @04:22PM (#12560046)
I personally don't care what you consider to be an engineer. I solve engineering problems, and I solve them well and I get compensated for it. I want to create great physics systems in game engines. It's not my problem to solve to make games built with that engine a success. I want it to succeed, but I don't get involved. That's not what I'm good at.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by blub on Thursday September 22, 2016 @02:36AM (#12554903)
It's part of a larger series of wise advice that seems to be appreciated nowadays. It goes like this:

* don't call yourself a programmer, you are a revenue-enhancing solution provider

* especially don't call yourself an X programmer, you will use whatever tool is necessary to complete the project and provide value

* don't look for a job, this shows that you're weak. Let the jobs come to you.

* keep yourself current with the latest frameworks and languages to prove that you can adapt to new challenges

* having at least one but ideally more open source projects on github proves that you have passion

* make sure you're a culture fit. Do go to the company parking lot beforehand to see what others wear.

* wear nice clothes, brush your teeth and eat your veggies

* <insert your own here>

After doing all of this you will probably succeed in avoiding having your job outsourced or having that promotion given to someone that's an even bigger bulshitter than you. Congratulations! Now you only need to have some minor plastic surgery done and learn a few recent cultural references in order to not make your colleagues uncomfortable.

You are well on your way to become the perfect solution provider citizen!

Re:Don't Call Yourself A Programmer, And Other Career Advice... by vvanders on Wednesday September 21, 2016 @03:43PM (#12551554)
Remember that d99? Getting a 1-95 are the places he describes. Congrats on making a good roll but this is still very relevant advice.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by mevile on Wednesday September 21, 2016 @04:41PM (#12552020)
I've worked multiple places and it's never been a problem, including big corporations. If you rolled badly roll again.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by nostrademons on Wednesday September 21, 2016 @03:49PM (#12551610)
The nice thing about at-will employment is that you can always re-roll, and usually keep the max of the two (or three, or five).
Re:Don't Call Yourself A Programmer, And Other Career Advice... by ryandrake on Wednesday September 21, 2016 @04:40PM (#12552017)
You don't get an infinite number of rolls in your career though. If you rolled a low number, you might not know it until after a few years. A better analogy is a baseball game. You get a few at-bats throughout your career, and that's it, and you generally have to do them serially. Either you swing for the home-run and risk missing, or take the safe base hit and never end up scoring a run.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by linkregister on Wednesday September 21, 2016 @04:09PM (#12551788)
I don't think dice are a good analogy since previous jobs affect the ability to get better subsequent ones. Yes, names on a resume and knowing the right people are important.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by Vraxx on Wednesday September 21, 2016 @05:03PM (#12552223)
An important point to be sure, although you don't exactly keep the max. It's more of a press-your-luck type of operation where you can't necessarily revert back to the max if you've already left it. Still a very valid point that you can switch jobs at any time you're unsatisfied.
Re:Don't Call Yourself A Programmer, And Other Career Advice... by Xantier on Wednesday September 21, 2016 @03:36PM (#12551482)
This is a very interesting comment and I like to think the same way. That is the way that seems to bring most happiness to me in professional life. The question is, how do we recognise these places before joining them?
Re:Don't Call Yourself A Programmer, And Other Career Advice... by zodiac on Thursday September 22, 2016 @12:47AM (#12554436)
"This guy" used to run his own business and also did consulting when the article was written