Live data from Hacker News

The Developer's Dystopian Future

the-pastry-box-project.net

71–80 of 209 posts

Re: The Developer's Dystopian Future

#71
post #3

I feel his pain, in a sense. I'm 24, and 'cloud' to me is 'a vps somewhere', I don't grok the difference, I've worked in elastic compute environments before, but that's definitely not what you're buying with things like EC2, and I simply don't see the value in it. other things like the 'DevOps' title; seems to mean either a sysadmin who can do configuration management, or a developer who can configure apache. everywh…

>I'm 24, and 'cloud' to me is 'a vps somewhere'

It is a VPS somewhere, ultimately. It's a VPS somewhere but it may be two of them or more. It may not be exactly where you think "somewhere" is, but it is somewhere. You don't know exactly what is running the VPS (or the bunch of them, somewhere), and what it runs, but it's running, it's a VPS, and it's somewhere.

We'll charge you 50% more to enjoy this uncertainty and to be able to use the word "cloud" alongside "synergy", "blue-sky thinking", "out of the box" and a few others when you describe your stack.

(On a less cynical note: with the "cloud" you're essentially paying to replace the known, common possible points of failure with unknown, usually rare points of failure, and some redundancy. Uncertainty can be a feature.)

Re: The Developer's Dystopian Future

#72
This post really resonated with me. The fact is, there used to be less to know to be a "full stack" engineer, and the expectations for what "good front end design" means were much lower 7+ years ago. I sense a widening gap between the realms of front end and back end engineering/design. It used to be you could write a small PHP app and put it on a shared hosting account to serve your small user base and people (stakeholders/users/peers) were mostly happy with that. Now, if you're not "infinitely scalable" plus doing TDD/BDD plus Continuous Integration or even Continuous Delivery right away, that's considered lacking. This does create opportunities for those of us who've been able to grow with the field and truly understand "how computers work", but I imagine it's frustrating for those who are trying to get into the field now or even just trying to broaden their skillset such as from front-end engineering to devops and system engineering/architecture.

Re: The Developer's Dystopian Future

#73

I'm not even legally an adult, and I feel like things are moving too fast for me. At 17 years. I guess I shouldn't feel like that, but I can't help it. I started with VB6 as a kid, 6 years ago. I moved onto C++, then learned about 3D graphics and game engines, then learned HTML, CSS, JavaScript, gotten into web development, learned Photoshop, some basic design, working with Linux, PHP, a little of C#. Recently tinker…

You've got plenty of time. Other commenters are right, focus on theory, and bolster that by building things. Constantly. If there's one lesson I could hope to impart to any budding developer, it's to never stop building. Learn a bit about genetic algorithms - then implement a simple one. Learn a little Ruby, then build something with it. This will teach you a lot of what you need to know - fill in the gaps with Google. Focus on building good abstractions, and you'll be fine wherever you go.

Re: The Developer's Dystopian Future

#74

I'm not even legally an adult, and I feel like things are moving too fast for me. At 17 years. I guess I shouldn't feel like that, but I can't help it. I started with VB6 as a kid, 6 years ago. I moved onto C++, then learned about 3D graphics and game engines, then learned HTML, CSS, JavaScript, gotten into web development, learned Photoshop, some basic design, working with Linux, PHP, a little of C#. Recently tinker…

You remind me of myself at 17. Your post tells me you have both the capacity and the appetite to learn, which is the foundation of success in this field. Keep chaining one body of knowledge to the next.

Re: The Developer's Dystopian Future

#75
40-ish developer here and I think the author is being at risk of being left behind.

I just think that when we choose this industry as our career, we have to go in with the knowledge that this isn't something where we can learn a set of skills once and then focus on that for twenty years. Our career is learning. Our value isn't what we've done before, it's what we're able to do.

That isn't to say you always have to learn the newest thing - definitely not. But it's important to stay current with the largest general trends. In the past it meant being facile with a handful of MVC frameworks (however you define MVC). In the more recent past it meant being familiar with some sort of RPC architecture (whether SOA, REST, "API-first", whatever). At present you probably want to be roughly familiar with at least one javascript framework that has MVC on the client side. And looking towards the future, you have to bone up on math concepts and functional programming, so you can move into parallel programming and concurrency concepts.

That's my sense of the rough direction. If in five years you haven't paid attention to that stuff, you'll still be able to find work, but it'll be grunt work that is at greater risk of being outsourced.

Re: The Developer's Dystopian Future

#76
Relax. Technology is part of a means to create value. Having skilled leaders is more important in value creation at scale than skilled engineers.

Projects fail because obvious risks are ignored - finding the integrity to fix those will maximise your value to anyone far more than learning AngularJS

This is not to say code should be ignored, but that code is software literacy - and soon "everyone" will be literate and the supply/demand curve will balance back out, but with a new higher baseline for entry.

Re: The Developer's Dystopian Future

#77
Y2K was solved by "out of date" programmers who still knew the code behind the stuff that would only take 2 digit years getting hired to fix it so banking and what not would not implode.

Some guy who made bricks found himself very in demand when he was older because he was the only person who knew how to make authentic historic bricks with which to restore historic properties in the nation's capitol.

Being old(er) can be an asset. It can be a feature, not a bug.

(shrug)

Re: The Developer's Dystopian Future

#78
I relate to this quite strongly. Whether you like it or not, a software career forces you into being a generalist eventually. Technology changes dramatically every few years - unable to improve what we have, we do entire revolutions to make incremental progress, and in the process, we make everybody's skills stale. The only things that survive are the principles that are common to everything. There's nothing you can do about that. And once you end up a generalist it is very hard to be appreciated for your wide breadth of general skills. People want the best person for exactly the job they are about to do, very few take a long view, very few even have the luxury to do that.

From another perspective, we are in unknown territory here. Us 40+ developers are at the vanguard of a generation of software people who have no trail blazed before them to tell us where our careers should go. There simply isn't a widespread professional software industry of 50+ and 60+ years old for us to look at and say "that will be me in 10 years". We were largely the first generation for whom software was a major industry. I take comfort from this because in all likelihood it will work out better than our worst fears would have us imagine. It is as much the lack of example and uncertainty as the reality that makes us feel insecure.

Re: The Developer's Dystopian Future

#79
I agree with you completely man. I'm working on my senior thesis to wrap up my degree and I have to use the Microsoft stack to write a real-time web app.

I haven't use MS stack since MVC2, and now we're at MVC5. I'm looking over the new things and now there's this new stuff called OWIN and Katana. Wat?

Buzzwords galore: iterative, modular, lightweight. Ugh. It used to work fine and now I have to learn some new thingamajig again.

Re: The Developer's Dystopian Future

#80
Be and keep worried, but don't let your angst control you!

The post describes a peripheral vision of progress, but no relation. It doesn't matter shit what new software, libraries and technologies are out there. What matters is that you have your own goals and advance in that! The rest doesn't matter, don't worry about others, you cannot help anybody, if you cannot help yourself.

I always tell me friends who don't know anything about computer science that my job is to make everyone else's job obsolete. After convincing them how their career might one day be replaced by software, robots and algorithms, I explain how they don't need to be alone with that fear. Of course I know how this makes me look like either a freak, an asshole or both. But the important part about the discussion is to communicate what really is going to happen. It happens, but the progress advances as slow as the growth of a tree. One day, it will be large, it will be a forest and then there will be no way to ignore it anymore. This is why it matters to open someones eyes. Of course only those who you deem worth, most people still won't listen and let time pass.

So yes, I share the same fear. Our destiny and true job is to make ourselves obsolete. Creating Software that can create machines, products and manage people, schedules and ressources. Creating Software that can create better versions of it's own or even create other Software to fulfill it's goals. This sounds like a big stretch, but we're talking about a time-span of 20 to 30 years.

We write code that will one day replace the need for us as a regular' work-force, but not as an actor in the process. The Future won't stop there, it'll instead create new markets and jobs where we proceed as architects using our creativity and intelligence, until our machines create hardware that surpasses the constraints on the software, which were set by us.

This will require us to allocate new resources for energy, either beyond earth using SpaceX like programs, the invention of a replicator (using quantum teleportation and molecular re-organization) or light to mass converters.

Post reply on HN