4 ms·
The big picture is not going to change. There are two broad categories of programmer. 1) people who build applications by gluing libraries and APIs together to
by phkahler 11y ago
The big picture is not going to change. There are two broad categories of programmer. 1) people who build applications by gluing libraries and APIs together to get what they want. There is no shortage of things people want the machines to do, and this is by far the biggest swath of programmers and will remain so for the foreseeable future. 2) The people who do deeper dives and build high performance subsystems and components and wrap them in APIs for the first group to use. The older components will see slow replacement by newer/better versions of the same, while new areas are opening up all the time. Vision, voice, image processing, genetic analysis, communications, payment systems, medical records, you name it.
If you're the first kind of programmer, do some programming with some of the tools that interest you to learn new things and broaden your experience/understanding. If you're the 2nd kind, pick and area that interests you and roll your own. It doesn't matter if there is a big commercial code or even a big open source version out there, chances are if the right person does their homework they can build a better mouse trap. Just because something is big doesn't mean it's the best that can be, some things just have a lot of momentum.
But no, I don't really see much changing other than the list of things people build and then glue together. That basic pattern (build tools, apply tools) seems to be very persistent. Rather than worry about the future, you should open your eyes to just how wide the field is today.
- AlexeyMK 11y agoI refer to the above types as (1) Application Developer and (2) Systems Engineer
- phkahler 11y ago>> I refer to the above types as (1) Application Developer and (2) Systems Engineer I try to avoid the word "System(s)" because of confusion between what we're talking about, system administrators, system architects, and control systems folks. But if you're certain the person you're talking to uses the same definition then it's fine.
- minthd 11y agoI divide the categories a bit differently: It seems that machines are much faster at learning how to do low level stuff(compilers, generic problem solvers, etc) - than they are at doing the high level stuff - understanding the problem and build a high level spec/system for the solution. And of course we're becoming more capable of letting the domain users enter more and more details of the system themselves, either by visual programming, scripting or giving data to machine learning systems, etc. So if those trends are to continue , professional programmers will specialize in creating more and more , highly abstract generic solutions.
- microcolonel 11y agoIt's not like the machines are just /learning/ how to do low level stuff. People are doing deliberate research, modifying them, and testing them to make that happen. Low-level optimizations are the least automated process I can think of.
- minthd 11y agoI'm talking about trends , not absolutes(not a sith). The share of programmers who are doing high level stuff(understanding users and encoding that ) versus those who optimize the low-level is always growing. Maybe it's ~90% today , vs less than 10% in the early years of computing when every byte counted and systems were less complex. > Low-level optimizations are the least automated process I can think of. And compilers automate low-level optimizations every day.
- microcolonel 11y agoNo they don't, humans write compiler optimizations every day, and toil over them. Compilers can only run existing optimizations.
- mcbrogrammer 11y agoFor skilled, experienced and dedicated developers - the future will be business as usual. For all the fakers, the ones who followed the cash into software, the wannabees and their one week bootcamp for ruby on fails, I have a phrase that will help your future careers: "do you want fries with that?"
- Phlarp 11y agoI agree with the sentiment, but making a novelty account just to post flame with as little tact as this deserves every downvote it's getting.
- elevenfist 11y agoFrom talking with hiring managers and upper-level managers & executives across many different startups and big companies, there's an important caveat to "The big picture is not going to change." Application engineering is getting easier and easier to the point where people no longer need a degree or even extensive training to be able to do application engineering work. Employers are aware of this, startups especially, and often prefer unskilled individuals (or people with only domain expertise) who are willing to work extra hard to teach themselves the skills on the job. They often pay these people less as well. This was explicitly stated as a good strategy by a ycombinator partner, and the executives of several successful, well-known, mid-size companies. Honestly I hope this isn't true, maybe someone else can shed some light on this. What will change is who is doing the work, how many people are employed, and how much they're compensated for their work. I also want to mention that a number of my friends have gotten job offers from Google, and they're much lower than the offers other friends received just a year ago for similar positions (at least $20k less).
- jaegerpicker 11y agoHonestly this isn't even close to true. It's can seem that way if all you look at is startups that fail fairly early on but the vast majority of startups that grow beyond the early prototype stage end up rewriting the app using solid engineering principles or they fold under the load. That requires people who really know what they are doing. Is it easier to prototype an app now? Certainly. Is it easier to build a scalable stable app now? No, not really at all. It's not breaking new ground anymore but it certainly requires a great deal of experience and hard earned knowledge to get there.
- MichaelGG 11y ago>. Is it easier to build a scalable stable app now? No, not really at all. What? It's vastly easier. 10 years ago, you'd often buy servers. Getting a HA DB required a bit of knowledge (especially if you weren't using SQL Server's easy cluster stuff). Backups were another hassle. Now? Click "New Database" and select a performance and HA level. Done. Look at StackExchange - they just scaled the DB up cause RAM is cheap enough to put a TB in a server. That's vastly easier than dealing with scaling out. And even to scale out, "cloud" DBs like SQL Azure have sharding and auto-scale built-in. On top of that, servers are MUCH faster. Look at the RPS that some sites are claiming. They simply aren't that high. 1000 RPS? 10 years ago that required some planning. Now, so long you don't do dumb things, it's not an issue. (Source: I ran a system that did hundreds of millions of transactions a day, and the hardware requirements were rather light. Each transaction ended up in an ACID DB UPDATE, in addition to archival, auditing, HTTP requests, etc.) It's simply incorrect to say it's not easier to scale today. It is.
- seiji 11y agoThe paradox these days is "people who build applications by gluing libraries and APIs" are ending up more highly paid/rewarded/recognized than the developers who create the glue and APIs they are actually using. So, all the "two week programing camp" developers launch their 12-hours-from-idea-to-launch apps on top of the work of _actually_ skilled people, and all the reward goes to the final layer, not the underlying support. Right now we're in an environment where, if you do build a better mouse trap, you get $1 while people using your better mouse trap to build Social Mice Death Sphere get $1 million just for adding fancy graphics on top of other people's work. Is the only reason our entire zero-reward open source system stays alive is because nerds are economically irrational and just want to have fun while turning a blind eye to being exploited?
- andresmanz 11y agoActually, that's one of the things that bothered me for a few months now. I can't see where this is going, yet. And to be honest, it scares me quite a bit.
- seiji 11y agoThere are options. I think it's disingenuous to think every open source software component should be a VC funded company operating off support contracts to get any reward. That's essentiality the only avenue to "greatness" right now. In a proper world, VCs would recognize all their darling, bespoke, hand-picked companies depend on the public infrastructure of open source (and unaffiliated) developers to super accelerate the growth of their portfolio companies. In a sane world, VCs would see it's in their best interest to create a "public benefit" pool of cash where they fund open source developers to create, maintain, and grow open source projects/platforms at full time senior-engineer salaries. Such a pool of cash (contributed to by multiple VC firms) would be administered by a neutral third party (to avoid nepotism as VCs are wont to do) and have "board-like" oversight and project prioritization (maybe each portfolio company gets X votes towards ranking which features to create next) so resources (cash/salary/infrastructure) go towards projects companies are using and needing to grow. A different option is to encourage VC-funded companies to set aside, say, 5% to 15% of each round for hiring full time open source developers. Open source developers working at a company would be loyal to their open source projects first and foremost, but would accept direction and feature prioritization from the sponsoring company. Just because something isn't a company doesn't mean it's not valuable and doesn't deserve compensation for services rendered, but in the current environment that's the only way forward until more fundamental change appears.