News for hackers. Stuff that matters.
Re:Reflections of an “Old” Programmer by thesmallestcat on Thursday October 06, 2016 @08:32PM (#12657303)
Hm. The author works for a web/mobile development agency and uses React Native and GWT as examples of the new and the old, respectively. I hope it isn't news to anybody here that this sort of work is a race to the bottom and has such turnover precisely because it's mostly being done by junior developers. Linux systems programming arcana, for instance, doesn't disintegrate so quickly as the ten years the author cites. That's why, after getting into the industry as a frontend web dev, I will only do that sort of work now as a last resort to pay the bills (the other reason is because it's easy/boring as hell, apart from the greater opportunity for mentoring). Doing that sort of work now feels like I am sabotaging my career.
Re:Reflections of an “Old” Programmer by noname123 on Thursday October 06, 2016 @09:41PM (#12657562)
Yes. I'd love to hear some people's journeys to advance their career and move from web development into more specialization. Off the top of my head, there are three types of specialization, for money, for domain knowledge and for technical skills.

For Money: Not necessarily any more satisfying or churn-proof than web development; But definitely more lucrative. Salesforce/SAP/Oracle consultant, mobile app developer, SEO or becoming a web dev consultant or remote work arbitrage or just becoming a manager.

For Domain Knowledge, you are becoming a computational {Biologist, Geologist, Financial Quant} than a pure coder. Fields like modeling fluid dynamics or finite element analysis for GE or GM; or modeling petroleum reserve for Shell; or Bioinformatics for BigPharma or modeling risk for banks. You probably have to go back to school for another degree in that subject or get the equivalent on-the-job training.

For Technical Skills, you are specializing in a sub-field of practical coding/IT, working at a software company. Like Data Science/Machine-Learning (distributed computing tools and knowledge about basic learning models), or Information Security (e.g., MITRE) or Embedded System (C++/Assembly) or high-performance system (e.g., Akamai; C++/networking).

Curious anyone who took the step to specialize or just started out in a more specialized field and their thoughts; and if I am missing any potential specialization options out!

Re:Reflections of an “Old” Programmer by WalterBright on Friday October 07, 2016 @12:21AM (#12658161)
I started dabbling in compilers early on and just got increasingly into them and their associated tools. It's still fun watching a new optimization rumble into life:

https://github.com/dlang/dmd/pull/6176

(Yes I know some other compilers do that already.)

It's fun knowing how it all works from the source code to the executable.

Re:Reflections of an “Old” Programmer by xaa on Friday October 07, 2016 @02:40PM (#12662943)
Well, I learned to code in order to do bioinformatics. I didn't start out as a programmer looking to specialize.

I agree that it seems that programming + X is often a much more powerful combination than programming or X alone. But I would say to anyone starting out that it is better to head towards, and get the formal qualifications for X, and learn programming on the side (or if in college, get the major in X and a minor in CS).

The reasons are that programming is relatively easy to learn outside of classes, and programming itself really doesn't require formal qualifications.

For me, biology has been orders of magnitude harder to learn than coding. With coding, you can learn by doing, and you get immediate feedback from the compiler/interpreter. Not so with biology. You can be mistaken for weeks/months/years and never realize it until you read just the right article. And often, domain-specific knowledge like biology seems to be composed of thousands of tiny details without too many general principles, whereas if you learn a few basic principles for programming, you can learn pretty much any new language or framework easily.

I don't know if this is generally true of all specializations, but if so, it would behoove someone to get started on learning the specialization-related information ASAP, because that will take much longer to reach proficiency than for programming.

Re:Reflections of an “Old” Programmer by noname123 on Friday October 07, 2016 @07:15PM (#12664654)
Thanks xaa for your thoughtful comments. I've taken a few MOOC on Bioinformatics. Biology certain seems much harder to get feedback esp. if you work in the wet lab, but I'm curious however about what particulars in Bioinformatics in your opinion is harder to learn (assuming that a computer person has taken Biology 101, aware of DNA to RNA, transcription, translation, mutations, variants, alleles, genotypes, haplotypes, basic cell biology; and maybe let's say even a step up, familiar with basic's of processing NGS files, processing assembly, variant calling, RNA-Seq and ChIPSeq differential analysis).

Is it the statistics (finding the right statistics inference test and knowing what are the pitfalls of your models)? Or is it understanding the underpinnings of the biology behind a particular pathway you're studying? (e.g., knowing how to perform or iterate on the wet lab experiments of doing in-vivo or in-vitro experiments). Thanks again for your comments.

Re:Reflections of an “Old” Programmer by xaa on Saturday October 15, 2016 @05:19PM (#12715686)
> is it understanding the underpinnings of the biology behind a particular pathway you're studying

Yes, this is it. You are right that the really general basic concepts (what is DNA? how does transcription work?) are not all that hard to learn. And it is certainly part of the core job skills to know, e.g., how to process sequencing data and how to use statistics. But in the real world, bioinformaticians work in collaboration with wet-lab biologists.

So, a typical project for me might look like this: collaborator comes in and tells me that his lab studies a particular protein X that operates at the presynaptic terminal in neurons. And they are collecting data about how some perturbation to X affects other cellular systems. The data will often be some combination of sequencing/array data and more specific wet-lab experiments (western blots, electrophysiology, etc).

So, in that case, to really do my job well, I have to go back and read in depth about the presynaptic interface, the major proteins and the mechanisms that work there. I may already know the generalities, but to really be able to interpret the data correctly, I need to know the details.

Now, imagine doing this process 10-20X a year for different collaborations and totally different biological systems. It's very hard to keep up. Now, it is certainly possible to be the kind of bioinformatician who is "give me your sequencing data and I'll give you the DE genes back", treating everything as a purely technical problem. But these kinds of bioinformaticians are not as much sought after because the wet-lab biologist doesn't want Excel spreadsheets full of lists, they really want to know "what do my results mean?". And to answer that really requires both the bioinformatician and the wet-lab biologist to understand what the other is doing at a more than superficial level.

In short, the hard part isn't learning the things that are used in every project, the hard part is learning the domain-specific information that is relevant to each individual project.

Re:Reflections of an “Old” Programmer by nickpsecurity on Thursday October 06, 2016 @08:55PM (#12657379)
Ill add people doing COBOL, C, and C++ to that list. Rate of change is slower. People are more conservative about what they're doing. Reuse of proven components prefered. Knowledge doesnt have to get worthless so fast if it was worth something in the first place.
Re:Reflections of an “Old” Programmer by sotojuan on Thursday October 06, 2016 @09:55PM (#12657608)
> Doing that sort of work now feels like I am sabotaging my career.

Heh, I feel that way and I'm 22. Unfortunately the only language I know is JavaScript and the stuff I am interested in and learning isn't quite there yet in terms of jobs.

Re:Reflections of an “Old” Programmer by Zyst on Thursday October 06, 2016 @09:03PM (#12657404)
Twentysomething year old here, so you know, not like you don't have a point but:

>the other reason is because it's easy/boring as hell

I legitimately think front end development is not only very fun, it can have some really challenging aspects. I wouldn't think there's any programming challenge that is inherently easier because it's on web as opposed to something else.

Of course I bet there are domain-specific tasks (Distributed Programming, Embedded hardware to list some) that are likely harder than web development. But I guess what I'm trying to say is: I don't appreciate you calling what I make a living off, and spend quite a few hours studying weekly 'easy/boring as hell'.

Re:Reflections of an “Old” Programmer by quickben on Thursday October 06, 2016 @10:16PM (#12657663)
35 here. I completely understand why you are on defensive about something you are passionate about. Try to see our perspective though; web dev, we've been there. In my case, you name it, I've done it, nobody gave me a T-shirt thought they all asked for unpaid overtime.

At some point you realize that it's a race to write more lines of code with every iteration, and that employers will gladly abuse your passion in many ways go get cheaper output from you.

If I may take the liberty to give you an advice here, go for the lower level/more specialized stuff as your career progresses. Not only they change at a slower pace but they are paid way 2-4 times more here in Toronto. If you care that you studied and make a living off of it, try to focus after technologies where your hard work will be relevant longer.

As for me, I love what I'm doing. Currently it's a mashup of crosplatform c++14, .net core rest api, elastic search, postgre and bunch of connecting glue. Our resident js expert is busy for the next few weeks so I'll probably learn typescript and go up my stack to provide an interface.

Smaller shops are tons of fun.

Re:Reflections of an “Old” Programmer by Chris2048 on Friday October 07, 2016 @08:09AM (#12659963)
> go for the lower level/more specialized stuff

This is my own strategy, though domain specialised rather than low-level.

I don't want to do "business" or project manage.

Re:Reflections of an “Old” Programmer by thesmallestcat on Thursday October 06, 2016 @09:06PM (#12657417)
I was only speaking for myself. The challenges got old and most of the work felt like framework jockeying; it was work I could do in my sleep apart from the sweat of learning new tools. I won't deny that there are some exquisite challenges in frontend development, but most of the paying work does not involve them and is pretty CRUD-oriented. Also I was referring to web development in general, not just frontend.
Re:Reflections of an “Old” Programmer by douche on Friday October 07, 2016 @06:41AM (#12659561)
I can't get over the endless yak-shaving in front-end dev. Fighting with browsers that all do things slightly differently, a terrible programming language, an abused, crufty markup language and a baroque styling language on top of that is not my kind of idea of a good time. Not to even get into the node/bower/grunt/gulp/webpack/babel shitshow compile and build process that it seems to be trending towards.

Working on the backend building APIs, optimizing data flows and managing backend services is more fun, and wildly more productive, if less whizz-bang and shiny.

Speaking as a 20-something who frequently forgets he's not a forty-something...

Re:Reflections of an “Old” Programmer by Chris2048 on Friday October 07, 2016 @08:10AM (#12659968)
> endless yak-shaving

I think this is the issue, it's not that the problems aren't hard, rather you aren't solving new problems, but trying to figure out how the existing tangle of software can be made to do what you want...

Re:Reflections of an “Old” Programmer by EpicEng on Thursday October 06, 2016 @09:34PM (#12657534)
Well, sorry, but... it is. Maybe you find it interesting, that's subjective, but there's no real technical challenge in front end stuff. You're not solving hard engineering problems; you're pasting together libraries other people wrote on top of libraries other people wrote (and on it goes) and searching google to figure out why your opaque stack doesn't seem to be working.

Developing a good UI is difficult, no question about it, but not for technical reasons. Whether you resent that or not doesn't make it any less true.

>I wouldn't think there's any programming challenge that is inherently easier because it's on web as opposed to something else.

Not because it's on the web, because front end work doesn't require anything more than knowledge of your toolset and some design sense.

It's nearly all "hey, build a UI with some CRUD functionality which is essentially the same as the 100 you've built before, but for this special snowflake customer." Bleh.

Re:Reflections of an “Old” Programmer by GuiA on Thursday October 06, 2016 @10:20PM (#12657679)
Honestly when I see what my friends who design airplanes and particle accelerators are doing, I feel like we're all kind of fucking around in software engineering, frontend or not.
Re:Reflections of an “Old” Programmer by nickpsecurity on Friday October 07, 2016 @12:32AM (#12658187)
Re:Reflections of an “Old” Programmer by kybernetyk on Friday October 07, 2016 @04:27AM (#12659017)
Heh, true. Compared to real engineers and scientists we're just a bunch of monkeys re-inventign the wheel every 10 years (with each iteration being worse than the prior one).

But from time to time one of us monkeys gets lucky and changes the world.

So I guess it's a risk/reward thing :)

Re:Reflections of an “Old” Programmer by EpicEng on Thursday October 06, 2016 @10:39PM (#12657745)
I agree, most are.
Re:Reflections of an “Old” Programmer by shitgoose on Thursday October 06, 2016 @11:24PM (#12657924)
"but there's no real technical challenge in front end stuff."

oh boy, you are so wrong! as an old fart having spent a number of years building UIs, can tell you, this is hard! information layout, controls, flow - it can be tangled into a total CF, or it can be seamless. you are not pasting libs on top of libs - that is the job of a monkey, front or back end alike. normal devs start their day with talking to end users and listening to their pain. then they spend rest of the day trying to alleviate it. monkeys spend their days thinking how they can add to user's pain by pasting more layers of crap.

engineering is an important part in back end, front end or in cleaning the toilets. it is not what you do, it is how you do it.

Re:Reflections of an “Old” Programmer by EpicEng on Friday October 07, 2016 @01:30AM (#12658395)
You're describing a task which is more frustrating than technically challenging. Nothing you described requires a high degree of intelligence or training, only time. Of course some are better than others at it, but that's true of anything.

Think; designing the CV systems for self driving cars (since that's a hot topic at the moment) vs designing a UI which works seamlessly across browsers. One is a real, honest to God engineering challenge; the other is an exercise is patience and perseverance. There are many more people in this world who could pull off the latter than could the former.

If you truly, honestly believe that UI dev work is technically difficult when measured against the rest of the engineering world then I can't imagine you've been solving hard problems throughout your career. UI layout is not "hard" and it's certainly not engineering, nor is 'cleaning toilets'. of course creating UI's comes with its own set of challenges, but I'm specifically talking about technical difficulty.

Re:Reflections of an “Old” Programmer by buzzybee on Friday October 07, 2016 @05:15AM (#12659207)
You can jump off the train and do bad UI at any moment. But UI always, always, gets hard when you start caring. That's not a measure of whether UI is harder than CV, it's a low-pass filter on what the market will value.

Most of the individuals making CV demos are not making unfathomable genius-level demos: they are taking an existing library and bolting on a simple application to it. And most such demos are flimsy and not commercially viable, because the technology needs more massaging at a deeper level than the author is capable of in order to fulfill the desired marketing promise.

Meanwhile, simple bolt-on UI tends to be good enough. Not because it's fine as-is, but because the user can accommodate for its brokenness without being able to express what exactly is wrong with it. The product can ship and create value, albeit not as much. Yet, a UI dev who wants the best possible experience has to have the same attention to detail up and down the stack as the CV dev who wants their algorithm to perform well along every metric. UI innovations are understated because they oft seem obvious or unsurprising in retrospect, but they do come along every so often, and often in tandem with the developments elsewhere - these days, AI algorithms are increasingly intertwined with the interface in a very direct fashion, when one considers voice processing, predictive text, or other such features.

And yet, if you should aim to achieve better UI, some naysayer will come along and proclaim that you have made something "overengineered" and should "just use a standard toolkit like the rest of us."

Re:Reflections of an “Old” Programmer by shitgoose on Friday October 07, 2016 @02:23AM (#12658603)
by UI design I do not mean cross browser compatibility, but rather an understanding of the underlying data and operations on it, which involves familiarity with the business domain. this is hard. putting stuff on the screen is not hard. I am OK with tables and gifs. with all due respect your contempt for people who build UI (and clean the toilets) and misunderstanding or general principles of engineering are sad (pardon my microagression).
Re:Reflections of an “Old” Programmer by Chris2048 on Friday October 07, 2016 @08:05AM (#12659949)
> putting stuff on the screen is not hard

> your contempt for people who build UI

You've carved out your own definition of Frontend dev, it doesn't always require business/domain knowledge, many just put stuff on the screen.

Incidentally, I found this hard - not in a math problem way, but in a costing a lot of time and patience way. I distinctly recall spending a couple of hours trying to align some div after being requested to do so. I strongly dislike CSS.

Re:Reflections of an “Old” Programmer by acaciapalm on Thursday October 06, 2016 @11:19PM (#12657904)
Oh don't even get me started on front end development. A few times I've actually had the opportunity to make some really brilliant JavaScript optimizations only to have any performance gain made totally irrelevant by business loading up the page with a ton of totally non-performant ads.
Re:Reflections of an “Old” Programmer by thesmallestcat on Friday October 07, 2016 @05:04PM (#12663895)
This hits home way too hard.
Re:Reflections of an “Old” Programmer by randomdata on Thursday October 06, 2016 @11:59PM (#12658058)
> You're not solving hard engineering problems

What, in your mind, makes an engineering problem hard? I've certainly had to dig out CS algorithms and 'clever' applications thereof to reach desirable performance out of some custom widgets in front end projects. I don't know if that can considered hard – hindsight tends to make everything seem easy – but it is certainly beyond pasting in a library like you describe.

I have to agree that you can create some very useful projects that do not deviate from a framework/library's documentation, or what have you. But we don't really know what the parent in particular is working on.

Re:Reflections of an “Old” Programmer by EpicEng on Friday October 07, 2016 @01:36AM (#12658422)
>What, in your mind, makes an engineering problem hard?

A problem which requires a high degree of creativity, intelligence, and technical ability, likely one which hasn't been solved before. You're right; it's a bit difficult (at least for me) to define, but we know it when we see it. Sending men to the moon was a hard engineering problem; implementing the UI for gmail was not.

You speak of using 'CS algorithms' in your UI's. I assume you're talking about things like optimizing a search of a list by using a better data structure or sorting algorithm. C'mon. You didn't solve these problems, other people did, you just did a little research, and this is basic stuff most of us can pull off fairly easily.

The vast majority of web development is not engineering. It is in fact just pasting together code other people wrote to solve a particular, relatively trivial problem.

Re:Reflections of an “Old” Programmer by jhall1468 on Friday October 07, 2016 @02:12AM (#12658561)
Lol, you think you are spending 40 hours a week at the forefront of problem solving new challenges?

Let's be real, for a moment. By your definition of a hard engineering problem, very few people are spending their time doing it. Virtually no one is doing it every day.

Why pick on front end dev specifically? You think the average backend dev building installing flask is facing a lot of unsolved problems? You think the average game dev is rendering 3D models in some new, magical way?

Re:Reflections of an “Old” Programmer by EpicEng on Friday October 07, 2016 @02:38PM (#12662918)
So, I didn't want to say what I do because I didn't want to make it personal, but yes, I do. I work in biotech and desogn control systems for an immunofluorescent imaging device and associated computer vision algorithms used to identify circulating tumor cells in the blood stream.

We just released a prognostic test for colon cancer which is actually relatively groundbreaking as it provides a new treatment path for people who previously had no options.

So yes, I feel that I am. I have been a part of small engineering teams delivering brand new technologies to the market my entire career.

And you're right, very few people, especially in software, are solving hard problems. I wasn't picking on anyone, I was responding to a comment.

Re:Reflections of an “Old” Programmer by jhall1468 on Saturday October 08, 2016 @08:01PM (#12669281)
So you are using a fluorescent fiberscope to identify tumors.

So you are implementing some vision library. How is that a hard engineering problem?

> So yes, I feel that I am.

That's the crux of the issue. You are doing exactly what you find so distasteful about web development: implementing existing algorithms to solve a specific problem.

Unless of course, your team is actually inventing new vision algorithms that somehow changed the field, which I'd love to see the paper on.

Re:Reflections of an “Old” Programmer by randomdata on Saturday October 08, 2016 @11:58AM (#12667367)
Stringing together some OpenCV functions isn't hard engineering.
Re:Reflections of an “Old” Programmer by Chris2048 on Friday October 07, 2016 @07:59AM (#12659916)
> You didn't solve these problems, other people did

that's a high bar for engineering. Integrating known solutions into a situation is engineers. Mechanical engineers don't discover the laws of motion themselves.

Re:Reflections of an “Old” Programmer by EpicEng on Friday October 07, 2016 @02:40PM (#12662936)
So you're right about that, and I thought the same right after I posted. There is of course a scale here. Taking academic scientific research and turning it into something real is a far cry for changing e.g. an array to a hash table to improve lookup speed.
Re:Reflections of an “Old” Programmer by randomdata on Friday October 07, 2016 @10:24AM (#12660873)
> I assume you're talking about things like optimizing a search of a list by using a better data structure or sorting algorithm.

You assume wrong. They were not straight up textbook problems, but I agree that I used a wealth of existing knowledge to apply it to my specific problems. That's what engineering is.

> You didn't solve these problems, other people did

Naturally. If you are working on finding novel discoveries the world has never seen before, you would be appropriately labeled a scientist working on science. Hence, also why we consider the algorithms I mentioned before to come from computer science, not software engineering.

Re:Reflections of an “Old” Programmer by dunkelheit on Friday October 07, 2016 @06:36AM (#12659544)
You are comparing the sexiest problems of one field with the ordinary problems of another. This is just unfair comparison.

By saying that "we know it when we see it", you are acknowledging that this is a value judgment (nothing wrong with that, just don't present it as an absolute truth). Also, by your definition, sending humans to the moon is not a hard engineering problem. It has been done before; it involves pasting together some relatively well-understood components like rocket engines and guidance systems.

Re:Reflections of an “Old” Programmer by nightski on Friday October 07, 2016 @07:35PM (#12664729)
I think you have confused engineering for research. Engineering is not anything like you have described. I went to school for aerospace engineering.
Re:Reflections of an “Old” Programmer by JSDave on Thursday October 06, 2016 @10:24PM (#12657689)
Ok, then backend folks just do API integrations and database guys just make tables, no real technical challenges anywhere. Anybody getting stuff done is pasting together libraries.
Re:Reflections of an “Old” Programmer by RandomOpinion on Thursday October 06, 2016 @10:48PM (#12657792)
>Ok, then backend folks just do API integrations and database guys just make tables, no real technical challenges anywhere. Anybody getting stuff done is pasting together libraries.

The original poster said nothing about frontend vs. backend. Still, you're absolutely correct, backend work is mostly gluing together pre-built libraries and software too.

Re:Reflections of an “Old” Programmer by scandox on Friday October 07, 2016 @04:58AM (#12659132)
> there's no real technical challenge in front end stuff

You're looking at this backwards. It isn't about the task. It's about the person who approaches the task. Someone "creative, intelligent and technically able" (to quote your later comment) will bring vision to any task.

Like water they will find their level, find the new and shining thing they can bring to the arena in which they find themselves.

These invidious distinctions contribute nothing to mutual understanding amongst computing professionals. All of whom need to work with each other to achieve great things. That includes the documentation people - shout out to them for their intelligence and creativity too.

Re:Reflections of an “Old” Programmer by sotojuan on Thursday October 06, 2016 @09:58PM (#12657612)
There's engineering challenges in frontend but they only apply to Facebook-tier scale. There's also cooler stuff like data visualization, advanced animations/design and WebGL but those seem to be done by designers. For most of us, it truly is gluing X framework to Y backend over and over again.
Re:Reflections of an “Old” Programmer by EpicEng on Thursday October 06, 2016 @10:38PM (#12657741)
Sure, but even then I wonder how much of that complexity (the scaling bit) is actually implemented by the front end devs. I would assume that it's handled on the back end, but of course a UI like FB, used by 1.7 billion people, can't be an easy thing to design.
Re:Reflections of an “Old” Programmer by nostrademons on Thursday October 06, 2016 @11:05PM (#12657852)
At least at Google, "front end dev" extended down to the webserver tier, written in C++/Java. You were expected to make any changes necessary inside the webserver to complete your feature. That's part of what made hiring so hard: the number of devs who know Javascript and C++ and have their algorithms down cold is relatively low.

I imagine it's fairly similar at Facebook.

Re:Reflections of an “Old” Programmer by EpicEng on Thursday October 06, 2016 @11:36PM (#12657970)
Of course, that's not the definition most 'front end devs' fall under.
Re:Reflections of an “Old” Programmer by zebraflask on Friday October 07, 2016 @11:58PM (#12665597)
"[T]here's no real technical challenge in front end stuff"

I have the distinct sense that you might not have done much of this.

There might not be many esoteric algorithms to implement, but there is plenty - more than plenty - to do in terms of managing UI state and back end integration, especially if you have stakeholders who want to see a variety of complex UI manipulations happening in response to various business rules. Which can often be internally self-contradictory. In a DOM that delights in being uncooperative, pretty much . . . always.

Frankly, it's enough to make using Java or a C variant for typical back end work look like a walk in the park.

Re:Reflections of an “Old” Programmer by marcosdumay on Friday October 07, 2016 @11:59AM (#12661653)
What option do people have?

We created a universal interface for computing, and it is web programming. It does not matter if you are creating a CRUD application of an improved Google search, you'll have to present it the same way. Thus, unless you are willing to give up control on the presentation of your work, you'd better learn it.

Re:Reflections of an “Old” Programmer by dsjoerg on Thursday October 06, 2016 @09:23PM (#12657471)
When it's easy / boring as hell why not make the computer do it?
Re:Reflections of an “Old” Programmer by DenisM on Thursday October 06, 2016 @10:25PM (#12657695)
Yes, lets just make a framework to put an end to... well... all that mess of frameworks... ugh... :)
Re:Reflections of an “Old” Programmer by dunkelheit on Friday October 07, 2016 @05:47AM (#12659339)
There is a lot of tasks with enough variation to resist being automated (or at least they require much higher skill to pull it off) but they are boring as hell after you do a few instances.
Re:Reflections of an “Old” Programmer by go_go_ on Thursday October 06, 2016 @08:55PM (#12657377)
What do you duo instead? I want to get into embeded/systems development or marine (ship systems) development -- but the vast majority of that work seems to be DoD and/or require more than Public Trust clearance which I refuse to get.

Web Dev is just so easy to get, and pays well, at the moment the temptation is hard to ignore.

Re:Reflections of an “Old” Programmer by thesmallestcat on Thursday October 06, 2016 @09:02PM (#12657397)
Nothing as cool as embedded development, database development or anything like that. Just general backend positions, working on the guts of something that may have a web layer, mobile layer, etc. Web jobs are plentiful and paid fairly well early in my career, but pay on the upper end has a pretty hard cap, so it's been a worthwhile move as there's more opportunity for career growth. It also better lends itself to specialization (ML, natural language processing, etc.) so that is another opportunity.
Re:Reflections of an “Old” Programmer by bostonvaulter2 on Friday October 07, 2016 @03:37AM (#12658863)
But one of the downsides of doing Linux systems programming is that it is much more niche and really restricts your options for employers as well as where to live.
Re:Reflections of an “Old” Programmer by thesmallestcat on Friday October 07, 2016 @05:03PM (#12663886)
Is that meaningful? Even if they're hiring, it's not like I'm going to get a good senior web dev job (pay, challenges, respect, oppportunity..) in Boise or Nashville or wherever. Yes there are jobs, but unless you're going to work remotely, almost all of the good ones are clustered in a handful of metro areas anyway.
Re:Reflections of an “Old” Programmer by bboreham on Friday October 07, 2016 @04:01AM (#12658944)
Containers is an exploding field, and basically "Linux systems programming". Sure it's more niche than the web, but there are many many companies hiring, all over the world.
Re:Reflections of an “Old” Programmer by Zelmor on Friday October 07, 2016 @09:54AM (#12660646)
Maybe in 5-10 years I'll consider taking a look at containers. Currently, they are a fad not much unlike React.
Re:Reflections of an “Old” Programmer by Jtsummers on Friday October 07, 2016 @03:30PM (#12663338)
Hmm, why do you think they're a fad?

Virtualization as a way of controlling specific application environments has been around for decades. The current movement (kicked off by the hypervisor work over a decade ago) is towards running more virtualized environments now that hardware and software support is much better (reduced overhead associated with it, greater portability).

Do you mean that they're overused or that their value is overstated?

Re:Reflections of an “Old” Programmer by Zelmor on Monday October 10, 2016 @02:56AM (#12675506)
When Fortune 500s start adopting a technology, it can be considered ripe and stable. Big companies move slow for a reason. You wouldn't want your banking site to pull the newest javascript magick, but something to do dull-looking business logic, and be rock solid. You brought up virtualization. That started in the '60s. It too 40 years for the technology to get to a level where it is widespread and adopted by everyone and their cat.

We will see if Docker and other container technologies will get their hold in industries other than startups. For now, all the people who use it that I see are the cool kids on the block in their hoodies. I think boring technology is good technology in that it provides value and stability for everyone. I am yet to hear of one Docker adoption where at scale the company saved more than a three digit sum year-on-year. Remember that you also pay an extra for sysops folks who run these things, and they will ask a higher price because the tech is hip!

For me, I'll stick to VmWare and kvm for now.

Re:Reflections of an “Old” Programmer by Zelmor on Friday October 07, 2016 @09:51AM (#12660629)
>as well as where to live

Those very same companies offer remote work increasingly, as they struggle to find talent in the aforementioned field.