News for hackers. Stuff that matters.
Re:Sucks to be an old engineer by WalterBright on Monday May 27, 2013 @05:21PM (#5776649)
> Is it an example of ageism if someone who is 45 can't find a job when what they know is Ada, Cobol and Forth?

Um, I'm 54 and the languages of my 20's were C, C++, etc.

I also fairly regularly get calls from recruiters.

> So yes, you either need to find a job that doesn't change (eg a plumber or a teacher) or you need to constantly battle to maintain relevancy in a fast-changing industry or you need to become master of your own fate.

Or, you can be a driver of this change yourself by developing a modern, advanced programming language.

Re:Sucks to be an old engineer by vowelless on Monday May 27, 2013 @05:45PM (#5776765)
> I also fairly regularly get calls from recruiters.

Not everyone has a wikipedia article :)

http://en.wikipedia.org/wiki/Walter_Bright

Re:Sucks to be an old engineer by WalterBright on Monday May 27, 2013 @06:06PM (#5776843)
That brings up a relevant issue. I realized a long time ago that developing an professional online persona is worthwhile. To that end, I recommend regularly to people:

1. create a website from your own name, like walterbright.com, and put your professional work there

2. create a github account under your own name, and contribute to significant projects using it

3. ditto for stackoverflow, hackernews, gamedev.net and other relevant forums

4. write interesting and useful tech articles under your own name

I.e. your name is your brand, make use of it. If you use a pseudonym and hide your contact info or otherwise put up barriers to being contacted, you'll lose opportunities.

Aside from that, one the best ways to get recruited is to show up at tech conferences and engage with the other participants. A lot of companies use tech conferences as ways to find good engineers.

If you're broke and can't afford to go to a tech conference, submit papers to them and try to do a presentation - speakers usually get expenses paid.

Re:Sucks to be an old engineer by Swizec on Monday May 27, 2013 @06:58PM (#5777044)
> If you use a pseudonym and hide your contact info or otherwise put up barriers to being contacted, you'll lose opportunities.

In my experience using a pseudonym consistently works just as well. Most people don't even realized my "real" name isn't Swizec until we start signing contracts.

Yes, I also introduce myself as Swizec when meeting people in person. Especially people who might google me.

Re:Sucks to be an old engineer by kamaal on Monday May 27, 2013 @11:29PM (#5777859)
I am willing to bet none of that will help. Not for a common guy.

The fact that you are the inventor of the D programming language puts you in a very different league of people.

Re:Sucks to be an old engineer by WalterBright on Tuesday May 28, 2013 @01:09AM (#5778200)
When I first decided to write a C compiler, a friend of mine thought it would be nice to introduce me to the community C guru for some advice.

The C guru looked at me and said "Who the fuck do you think you are thinking you can write a C compiler?", and not in a nice way, either.

So what's stopping you?

Re:Sucks to be an old engineer by kamaal on Tuesday May 28, 2013 @05:53AM (#5779098)
Nothing.

And frankly your post had me thinking this whole afternoon.

What is really stopping me. And I have to frankly say, Nothing. Thanks for this valuable advice.

Re:Sucks to be an old engineer by WalterBright on Monday May 27, 2013 @09:37PM (#5777526)
Sadly, I often run across technical articles where the author omitted his own name, not even a pseudonym. I don't understand this.
Re:Sucks to be an old engineer by vicaya on Tuesday May 28, 2013 @04:10AM (#5778826)
Quite a few seemingly legit articles from Google results are "stolen" content created by bots and/or cheap copy writers from content SEO companies like Demand Media to generate ad revenue.

Internet branding is overrated. Personal network is a lot more important :)

Re:Sucks to be an old engineer by danbmil99 on Monday May 27, 2013 @08:33PM (#5777339)
> someone who is 45 can't find a job when what they know is Ada, Cobol and Forth?

I'm 53, know many engineers 45+, none of them are (still) hawking their Cobol/Ada/Forth skills. Just like the young 'uns, we learned C++, Python, Java, Javascript; we use node.js (if it's indicated), we read HN and other tech sites, etc. If we don't, then we're idiots and deserve not to get hired, and we know that.

One thing I've discovered is that knowing the new stuff in conjunction with some of the lost arts (messy old C builds, hardware-related mysteries, debugging without debuggers) gives me some skills that are not easy to come by, and that is a real advantage getting work. There will always be legacy systems that are 10-15 or more years out of date, and a market to keep them running.

Re:Sucks to be an old engineer by wglb on Monday May 27, 2013 @06:51PM (#5777030)
Ok, this might be a little sandbagging or serious understatement here:

the languages of my 20's were C, C++, etc. As in "I wrote compilers for these languages".

If you aren't getting calls from recruiters, then none of the rest of us will.

For those of you who don't know, he wrote, so far as I can tell, the first native c++ compiler.

ex-MWC guy: ...ihnp4!mwc!wgl

Re:Sucks to be an old engineer by taude on Monday May 27, 2013 @05:38PM (#5776730)
The people capable of "Or, you can be a driver of this change yourself by developing a modern, advanced programming language." is probably farer and fewer between. How many are capable and how many advanced programming languages are needed?
Re:Sucks to be an old engineer by WalterBright on Monday May 27, 2013 @05:56PM (#5776804)
There are plenty of other things you can do to drive the state of the art forward. I personally chose to develop a modern, advanced programming language.
Re:Sucks to be an old engineer by danbmil99 on Monday May 27, 2013 @08:35PM (#5777347)
> how many advanced programming languages are needed?

Judging by HN, about 60 per year

Re:Sucks to be an old engineer by taude on Tuesday May 28, 2013 @08:05AM (#5779412)
Awesome, so I guess there's only room for 60 SDEs over the age of 35 in this world.
Re:Sucks to be an old engineer by waterlesscloud on Monday May 27, 2013 @05:28PM (#5776681)
Java is nearly 20 years old.

Do people really think if you're 45 you worked in Cobol?

Re:Sucks to be an old engineer by Jare on Monday May 27, 2013 @07:19PM (#5777106)
I'm 42 and I did, working part-time at a bank during college. For 3 days, at least. Then I designed a DSL and wrote a C tool to generate the COBOL programs from templates and DSL files. Then my boss decided to never again let me near the mainframe and bank accounting systems. But many of my coworkers spent 3+ years entirely on COBOL.
Re:Sucks to be an old engineer by nikatwork on Monday May 27, 2013 @08:14PM (#5777278)
I work in finance. We are teaching plenty of fresh-faced graduate recruit devs COBOL.
Re:Sucks to be an old engineer by rbanffy on Monday May 27, 2013 @08:26PM (#5777321)
For someone into retrocomputing (who even made a 327x-ish terminal font), being paid to learn COBOL is weirdly interesting.
Re:Sucks to be an old engineer by nikatwork on Monday May 27, 2013 @09:44PM (#5777551)
Most of the org's original COBOL programmers are retirement age. So there's 60yo greybeards teaching COBOL to 20yos.

It's a weird time to be a mainframer. If you are an experienced specialist you can charge insane hourly rates. At the same time, some bigger orgs have started transitioning off the old stack because all the experts keep dying or retiring.

At some point mainframe specialist skills will go from insanely valuable to completely worthless.

Re:Sucks to be an old engineer by rbanffy on Monday May 27, 2013 @08:28PM (#5777328)
Never worked with COBOL, but did a lot of FORTRAN 77 in school. Some days I feel like I'll code high-persistence phosphor simulation into Compiz...
Re:Sucks to be an old engineer by nikatwork on Monday May 27, 2013 @10:39PM (#5777713)
It's OSX only, but this app should float your boat: http://www.secretgeometry.com/apps/cathode/
Re:Sucks to be an old engineer by rbanffy on Monday May 27, 2013 @11:53PM (#5777948)
I love it! I install it on every Mac I lay my hands on.
Re:Sucks to be an old engineer by garysweaver on Monday May 27, 2013 @11:13PM (#5777814)
In the late 1990s, I remember people there being recruitment efforts to find people with very little coding experience, teach them COBOL, and have them search for and fix Y2K bugs in COBOL code. I actually thought about doing that at the time, but ended up getting into Java. Even now, there is a lot of more COBOL out there that you'd think.
Re:Sucks to be an old engineer by bdunbar on Monday May 27, 2013 @10:35PM (#5777702)
I am 46. I was trained - Marines - in COBOL.

Although after I left Quantico they put me in a billet working with dBase III, I could just as easily been assigned to a billet at a RASC where I would have been using COBOL.