Not everyone has a wikipedia article :)
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.
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.
The fact that you are the inventor of the D programming language puts you in a very different league of people.
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?
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.
Internet branding is overrated. Personal network is a lot more important :)
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.
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
Judging by HN, about 60 per year
Do people really think if you're 45 you worked in Cobol?
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.
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.
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.