You must be logged in to reply.

Page 1 of 2 out of 15 messages.

Microsoft technology, the future

Posted 2yr ago
by mtylerjr | King | 24,672 exp
Posted 2yr ago
by mtylerjr | King | 24,672 exp
Hello GHI forum.

I had an interesting talk with someone today. They are Kiwi, but have been living in Silicon Valley for the past 20+ years. They've been in startups, and large companies. They have sucesffully transformed several technology companies over the past few decades. One newspaper article here described the guy as "the best software guy the country has ever produced."

I had coffee with him this morning here in new zealand, where he was visiting (well, I had hot chocolate.) We talked about our careers, and he asked me where I was planning to go, career-wise. I mentioned several Microsoft-platform areas I've been happily exploring and improving in - ones most of us here have experience with - VS2017, C#, UWP, IOT-core, Xamarin, Linq, WPF, XAML - and he was surprised. He said that this would be a dead-end in silicon valley, if I ever planned to move back there.

This was sobering. These are my favorite platforms for development, even if it has mostly been at-home/personal experimentation, while I toil away at my day-job propping up ancient legacy embedded C code written by committed of transient engineers over the past 20 years,, my mind atrophying from lack of learning anything new.

So now, I am open to rethinking a career path. Yes, I'm 50, but there are infinite resources for learning/becoming expert in any software area. I have no doubt I could ratchet up my javascript, ruby, python, sql, linux, Node.jz, django, RESTful architecture skills, but this seems like a random attack.

Who here thinks that a career in Microsoft-centric areas is a still viable career path now, in 2017?

What other career paths do you think could be more useful/in-demand for the next 15 years?

Anyone have any advice?
4 likes
Reply #1 — Posted 2yr ago (modified)
by mcalsyn | Legend | 48,189 exp
Reply #1 — Posted 2yr ago (modified)
by mcalsyn | Legend | 48,189 exp
Martin's manifesto of developer value...
Specialization is for insects. Over-specialization (or viewing yourself as specialized) will hurt your employability. It may make you valuable for a certain problem for a certain time, but that value always fades.

I used to be a Fortran fellow - all Hollerith and tapes and science. Then I was a PL/I and Pascal person, all mainframes and UCSD on minis. Then I became a COBOL person in a bank, all pointy collars and ties and code audits. Then came PC's and I was a PC C++ and ASM fellow. Then came the internet and I became a BSD Unix fellow, and later Linux. Then came NT and I was writing protocol code and IETF docs and server code for Microsoft. Since then I have been a C++ and C# individual contributor and dev manager for various Microsoft projects. I also learned Xamarin and did a bunch of mobile apps (including a fair piece of the original Power BI app, but that was C++). And I have always been close to my EE roots and the close-to-the metal hardware and software that makes me happy.

Now - here I sit today exercising some new skills in VS-Code, Node.js, npm and friends.

My point is, technology rots but the essential skills have been the same for a long time. Master the skills of time management, self-education, algorithms, problem solving and a solid work ethic, and then your one marketable product - those core talents - will never be out of fashion or off market. You may need to learn a new trick or two to make a transition, but until AI replaces us, skilled and dependable programmers will never be out of demand.

I am 57, and I definitely do not feel I have outdated skills.

[edit: summary: yes, I think being a 'Microsoft' fellow either is or at some point will be, very limiting. As soon as you stop thinking that way and start building and marketing broad talent instead of narrow skills, then you will be at your most marketable. By extension, that means a lot of personal investment in tech outside your current comfort zone]
Reply #2 — Posted 2yr ago
by Mr. John Smith | Legend | 42,263 exp
Reply #2 — Posted 2yr ago
by Mr. John Smith | Legend | 42,263 exp
@mcalsyn - Grow or die is that right? I thought that I would never need PowerShell, since I can just write what I needed in C#. Now I'm working with non programmers who don't/haven't coded in 20 years. (What am I trying to say)... How do you know which ones are fads and which ones are good? Python seems to be here to stay, where is Java? Why is Node.js suddenly so important?

EDITED:
Reply #3 — Posted 2yr ago
by mcalsyn | Legend | 48,189 exp
Reply #3 — Posted 2yr ago
by mcalsyn | Legend | 48,189 exp
Forget forecasting the future - you can't. Follow the money and/or your passion (choose one, two if you are very lucky).

I am doing vscode/nodejs/npm/etc because it is the best tool for the job I need to do right now.

A big toolbox of skills is great to have - that's what goes on LinkedIn after all - so grow those, but never consider yourself 'done' nor define yourself by a set of skills. Use those core talents to grow new skills. So yes, grow, or grow hungry.
Reply #4 — Posted 2yr ago
by mcalsyn | Legend | 48,189 exp
Reply #4 — Posted 2yr ago
by mcalsyn | Legend | 48,189 exp
Mr. John Smith says:

Why is Node.js suddenly so important?

Node.js leverages commodity skills (JavaScript), is cross-platform, and is finding a role as 'right tool for the job' in a lot of interesting server and desktop scenarios. It helps you get more done with less effort (a lot like NETMF on MCUs).

For instance: Electron (by github) is NodeJS bolted onto Chromium. VS-Code (and the popular editor, Atom) is built on Electron. So if you want to build extensions or services for VS-Code, you need to learn Node, Chromium (HTML5+JS), and npm. NodeJS is also one of the fastest ways to build for Docker containers or build HTTP'ish services in general.

Azure, for instance, supports NodeJS as the back-end for Azure mobile sites, and in fact, developed support for NodeJS before C#
1 like
Reply #5 — Posted 2yr ago
by Mr. John Smith | Legend | 42,263 exp
Reply #5 — Posted 2yr ago
by Mr. John Smith | Legend | 42,263 exp
mcalsyn says:
grow, or grow hungry.

Now there's a best quote.
1 like
Reply #6 — Posted 2yr ago
by devhammer | Legend | 55,820 exp
Reply #6 — Posted 2yr ago
by devhammer | Legend | 55,820 exp
mcalsyn says:

I am doing vscode/nodejs/npm/etc because it is the best tool for the job I need to do right now.

Funny...I just got back from giving a talk on VS Code at a local user group this evening, and made much the same point about using it when it's the right tool for the job, not because it's new or "better" than full VS overall.
Reply #7 — Posted 2yr ago
by mtylerjr | King | 24,672 exp
Reply #7 — Posted 2yr ago
by mtylerjr | King | 24,672 exp
I hadn't heard of vscode - I use slickedit at work, on our ubuntu boxes. I may see if I can substitude vscode.
Reply #8 — Posted 2yr ago
by Terrence | Hero | 12,056 exp
Reply #8 — Posted 2yr ago
by Terrence | Hero | 12,056 exp
@mtylerjr - You're gonna love VSCode.
1 like
Reply #9 — Posted 2yr ago
by ianlee74 | Superhuman | 127,688 exp
Reply #9 — Posted 2yr ago
by ianlee74 | Superhuman | 127,688 exp
mtylerjr says:
Who here thinks that a career in Microsoft-centric areas is a still viable career path now, in 2017?

I agree whole heartedly with @mcalsyn. However, as someone who has spent the last 25 years working almost 100% in Microsoft technologies this is a question I ask myself regularly. Early in my career, I saw myself as a "VB guy" and a "SQL guy" then later as a ".NET Guy" (meaning a "C# guy" since that's the only language that really matters... Wink. But, these days as I start thinking about what I want to do next I find myself thinking on a higher level about what sort of projects I want to work on and what products I want to devote my time to. I prefer that the project is based around Microsoft tech since I have to do less educating but that's a lesser requirement. When I find a project I want to be involved in then I find a way to get involved and somehow the money & skills always seem to follow.

That being said, I think you can absolutely keep a job as a "Microsoft guy" for the next 5, 10 or maybe 15 years. It just depends on the level of pay and types of projects you're willing to settle for.

Page 1 of 2 out of 15 messages.

You must be logged in to reply.