43 ms·
Developers are the autoworkers of our generation
- deleted 13y ago[deleted]
- mbesto 13y agoautoworkers == un-skilled labor managers == skilled labor From Drucker's The Practice of Management: A scant twenty years ago, it was widely believed that the mass-production technology—yesterday’s industrial revolution—threw people out of work. Today we know that wherever it has been introduced, it has rapidly increased the number of job opportunities in industry. But it is still widely believed that mass production replaces skilled labor by unskilled labor. We know this today to be a fallacy. In the United States, for instance, where mass-production methods have been applied on the broadest scale, the class of employees that has been growing most rapidly in numbers and proportion is that of skilled and trained people. And the truly unskilled laborer of yesterday, who contributed only his brawn, has become the semi-skilled machine operator of today—a man of higher skill and education, producing more wealth, earning a vastly higher standard of living.[1] I think Drucker would argue that "Developers" are the new class of "Managers". [1]Drucker, Peter F. (2010-04-02). The Practice of Management (Kindle Locations 490-496). HarperBusiness. Kindle Edition.
- stephanos2k 13y agoA chill went down my spine reading this. That's a good sign.
- mkr-hn 13y ago> Don’t get too comfortable. Don’t get locked into a language. Don’t burn bridges for short term gain. Keep your tools sharp. Learn soft skills. Build an audience. Save some money. Network. Read. This is great advice. The big issue with the rust belt is that building cars was all car builders knew how to do. Most didn't have the sustained practice with learning new things to adapt to a changing environment. I wouldn't keep it to programming languages and technologies, or even auxiliary skills like marketing and advertising. Keep your mind sharp with as much depth in as many different topics as you can stand.
- tluyben2 13y agoThis is a problem with most professions though; most people feel they learnt something (in or outside of the educational system) for years and they are automatically entitled to a job for life. As a programmer I try to have enough hobbies which can be used to make money; making/selling icecream (made enough with that this summer for 7 month of living including the working months), making/selling beer, making/selling cheese, welding, creating little RVs out of normal vans, electronics... And that is next to me not seeing anyone 'hacking a bit of WP' replacing any but mediocre coders anyway.
- jakejake 13y agoI agree this is great advice to keep your skills sharp. But, as far as auto worker and programmers being the same, I totally disagree. My hometown is a factory town and, actually, one of the few auto plants in the area that didn't get shut down or moved to Mexico. The average plant worker (I know many, many of them - most of my high-school class in fact) is someone who may or may not have finished high school. They have no job skills except a very specific skill for their particular station on an assembly line. They hate their jobs and they don't generally spend any time trying to learn anything new. I don't say this to judge or criticize because it's their life, they make a decent wage (a fantastic wage, in fact) and it doesn't matter to me what they choose to do. But, I do see them as being at extremely high risk of losing their comfortable lifestyle because if the factory were to ever get shut - they would be completely unable to get a job at their salary level. They are totally dependent on the factory and their skill is completely worthless anywhere else. This is nothing like any programmer I know. You can't get decent at programming with this mentality and you can't remain a decent programmer without continuing to learn new techniques. Most programmers that I know tend to always be curious and want to learn more. Although some of them don't want to take their work home, at least they like to learn new ways to be more efficient. I would liken programmers more to a mechanic or a carpenter. It's a more general skill that you can take with you from one place to another. I think the value may go down if more people go into it, but the industry is not as likely to cave in so fast as it did for unskilled plant workers.
- cpp900 13y agoLoad of carp.
- sker 13y agoIt's already happening. As a freelancer, I often find people who want their "corporate" site built in WordPress for less money than what they would pay to a car mechanic for a similar amount of time worked. Sames goes for Magento and similar platforms.
- karlkatzke 13y agoThat's been the case since I entered the development field in the early 00's. I wouldn't say it's anything new. The polite thing to do is to explain to them your hourly rates and then allow them to make a decision. The impolite, but safer for you, thing to do is to run without looking back. It's not a case of developers being automated, it's a case of the customer not understanding that they get what they pay for.
- MichaelGG 13y agoOr in the case of a simple content site that WP could easily do, perhaps they do understand what they're paying for. (Excepting security holes in WP...)
- tluyben2 13y agoIf you are talking about the front end of a corporate site then sure, you can do that in WP. Don't think many would though; maybe for the grocery shop, but other than that? Even relatively small businesses in my neighborhood with not much cash to spend start out with a 'cheap WP' site, but then they want reservation systems integrated with their CRM. They want a live chat system. Integrated with their CRM. They want their reservation system connected to online partners. Etc. In a few months after starting out with this site, WP or anything else is no longer relevant; existing solutions need to be integrated manually anyway and custom solutions made by, for instance, the CRM/reservation system which do not use WP are a better fit. At a much higher price. And people pay it, because custom integration is even more expensive. Even with all it's plugins, WP is only a good solution if you like to do a lot of work manually or you want to spend a lot of money having every plugin and external package nicely integrated. And no inexperienced programmers is going to bring that to a good end without landing on reddit/hn as being responsible for making some epic security holes along the way.
- nohuck13 13y agoHold on a minute. You can't discuss labor markets without discussing productivity. In the heyday of the automotive industry, the best auto worker in the world produced about the same output as the average auto worker. Maybe they messed up less, but being a genius autoworker didn't let you tower head and shoulders above the competition, because car factories are designed with auto workers as interchangeable parts. We've tried that with developers. If it had worked, all development would be outsourced to India and the Philippines by now, and developers would be forming unions to lobby for higher pay. The reality is that the market pays for productivity, in the long-run. Maybe having more junior developers coming out of bootcamps puts downward pressure on wages, but as long as development is a meritocracy where the best performers are much better than the worst performers, there's always going to be a premium on people that really know their stuff. Maybe one day we'll live in a world with lots and lots of really good devs. I don't mind living in that world as much, because I can control my fate to a far larger extent that someone who moved to Detriot in 1960 and was unfortunate enough to stake their whole life on a company pension and a single industry. EDIT: typo
- mkr-hn 13y agoI think the argument is that the skill level and number of people needed for most development jobs will be lowered with platforms and tools that make it easy for a minimally trained user to do it. Someone still has to make the tools and platforms, but implementing them won't take as many people. Think about how many wildly popular websites run with a handful of people. How long will it be before you don't even need more than a few people in a datacenter? Robots will eventually be able to change out dead drives on a RAID array and inspect the backup generator as well as a technician. People saying things like "everyone should be a developer" are coding the same people they're encouraging out of a potential career path. Which is fine, but the contradiction gets annoying.
- nohuck13 13y agoI think that's a key question, but I've never been a fan of the notion that robots (or efficient frameworks) are going to put us all out of jobs. If you look at what we've actually seen in the last 20 years, efficient frameworks enable entrepreneurship and wealth creation on a scale that wasn't possible in the past. Sure, there are fewer people employed doing nitty gritty stuff, but the size of the economic pie is far bigger than it once was, largely because of labor-saving technology and frameworks. If you want to argue that better frameworks will drive down wages, the argument to make is that better frameworks will reduce development time without facilitating wealth-creation. EDIT: maybe this will happen, I can't predict the future. Rereading your post, I guess this is more or less what you were saying. But then the question is, what's going to change to reduce growth?
- rprime 13y agoSo the baseline is, and this applies to almost all kinds of jobs, stay relevant and be good at what you do.
- luu 13y agoAs usual for HN, all of the most upvoted replies disagree with the article. Let me play devil's advocate and not disagree. Sure, the analogy isn't perfect, but what happens if we take the idea seriously? [1] Isn't it amazing, the lack of sacrifice necessary to make fat stacks of cash writing software? Even when law school was thought of as a golden ticket, it was a lottery, and to win, you had to sacrifice your personal life for a decade before you made partner. And those hours looked relaxing, compared to medicine and investment banking. Back when auto jobs were a sure thing, they were also sure to use up your body by the time you could retire, and that's if you were lucky enough to avoid a career ending (not to mention crippling) injury. I just met a kid who graduated with a BA in philosophy who was offered 4x the median U.S. income [2] at a software company. A prop trading firm offered him 50% more, and the software company matched the offer. One reason he turned down the offer at the prop trading firm is because people there regularly worked 50+ hours a week. The most upvoted article on HN from a couple weeks ago was full of comments debating whether 20% time is really 120% time, at a company where mid-level ("senior") engineers can have total compensation that's something like 8x the median income in the U.S. And was outrage! Outrage! Last year, coursera ran a course on deep learning from one of the guys who's widely credited with inventing deep learning. The pre-requisites were some basic programming, and, either, google + wikiepdia, or a basics of machine learning course, like the one that's offered on coursera regularly. After taking the course, you'd have enough understanding of deep learning to reproduce papers published that year, on the state of the art in machine learning. Never have we had a privileged class that's so easy to enter. It's genuinely surprising that this is the case. You don't have to be born into the aristocracy. There's no licensing body limiting the number of developers, and no hazing process that makes requires giving up the best years of your life. The knowledge is available to anyone with a computer and an internet connection, and those are cheaper than they've ever been in human history. You might say that there's just not enough "smart" people in software, but, that's part of what's surprising. Why do so many people who want a career involving intellectual curiosity study philosophy or mechanical engineering, when CS also gives you interesting problems, and happens to pay much better? Why don't people switch? Unlike with ME, CE, etc., you don't have to take the PE and get all sorts of licensing to find work. You just need to be able to pass some interviews. I met folks at Hacker School [3] who switched from econ, ME, OR, and other quantitative fields to CS, because you have more freedom to pursue ideas, can do more without being part of a huge team that makes you a tiny cog in a giant machine. And, by the way, it pays twice as well. But, it's still not common to see people switch. What's the barrier to entry that's keeping us from being flooded with supply? I'm told that CS enrollments are now at record highs, past even the numbers we saw during the dotcom era; perhaps the answer is that there is no barrier, and we're about to get flooded with supply. [1] In his notes, Lectures on the History of Moral Philosophy, Rawls talks about how his students eagerly come up with clever refute the propositions of great thinkers. He takes the opposite approach. It's been a long time since I've read this, so I'm very loosely paraphrasing, but it's something like, if you disagree with someone who's clearly very smart, maybe it's worth taking the time to figure out why they hold their opinions rather than just dismissing them. [2] median personal income in the U.S. is about $30k/yr. [3] https://www.hackerschool.com/ https://www.hackerschool.com/
- RougeFemme 13y agoI agree with all of this, but - and this doesn't take away from the key points - autoworkers could get entry-level positions with little to no skill. . .and no specialized education or training (formal or independent). The same is not true of entry-level coders. Some level of skill is necessary, attained through some level of training.
- kellros 13y agoI agree with you that this is the direction in which we are heading, but not that professional developers will become obsolete. I believe if we ever reach that point where programming is common-skill; the real developers will stay ahead due to demand. I honestly don't see corporates with millions/billions of revenue trusting newcomers with a few weeks of experience to handle core business automation; in the same way as you don't trust a clerk to sort out your legal issues. Perhaps when the time comes; professional developers will become like the attorneys in the law system; where specialist skills demand even a higher rate and requires less time invested (which might mean the same salary as now but only working 'part time'). I don't have any issues with people wanting to learn to code; I even mentor some myself. It really comes down to hours (or rather years) invested in learning and fine-tuning your skills; which I see the majority of new developers not willing to invest in. As such, I believe the demand for better developers will increase. Look to the tech companies with open positions looking for 10x/star developers - even though there are developers available, they just don't make the cut.
- greenyoda 13y ago"Perhaps when the time comes; professional developers will become like the attorneys in the law system; where specialist skills demand even a higher rate and requires less time invested" Isn't that happening today with the substantial number of developers who do freelance contracting/consulting?
- skyebook 13y agoOne comment on the post goes after the analogy not being fully sound because unions helped to prop up wages. Whatever you think about unions, I'll be sort of curious to see if some segment of developer jobs do unionize ever. I get the sense that the rugged individualism that seems to be far more prevalent in developer/engineer/hacker sort of circles would be less for it; what about h1b workers who seem to feature quote often in stories about not great companies overworking employees and threatening their jobs (and with that, their legal status in the States) Yes, a tangential thought to the article but an important part as people continue to evangelize the great opportunities in the tech industry and Hacker School, Code Academy, WikiBooks help them to get up to speed
- anonymousDan 13y agoInstead of unions, I'd much prefer if there was an organized push by developers to force governments outside of California to make it illegal for companies to claim they own the rights to every idea an employee has. In the UK it seems to be standard practice to do this, even when the employee comes up with an idea on their own time and using their own resources that's not directly related to the company's line of business.
- NKCSS 13y agoToo bad .nl doesn't pay Silicon Valley salaries; the norm here is more like 1/3rd of that.
- mberning 13y agoI have a few problems with this article. 1. The author points out all of the services which now exist, but says nothing of people and talent it takes to create and support such services. I think the tail for 'software enabled services' is rather longer than factory automation robots. 2. The author seems to have a somewhat narrow view of what developers actually do these days. Yes, it is true that people are not typically employed to roll their own e-commerce or blog sites. Very few people are doing this nowadays. Most of the software getting written for business today is highly specialized. Highly specialized software = no out of the box solution. 3. The author ignores the fact that a major drop in demand for software talent would probably coincide with some revolutionary change in technology. I'm talking about ubiquitous self driving cars and planes, robots that teach themselves, ad-hoc on site manufacturing via 3d printing, software that writes itself, etc. Should any of those things come to pass, having a nice job as a developer will be the least of anybody's worries. While I do agree that the industry is changing, I really don't see it as being that similar to the auto industry melt down. The differences and flaws in such an analogy are easily spotted.
- smk11 13y ago>Most of the software getting written for business today is highly specialized. Highly specialized software = no out of the box solution This is one part of the developer community that doesn't get publicized as much. The Startup web companies are not the only place where developers work, but they are the most competitive. I work for an Assessor's office as a developer, and we develop our management information system in house. There are only about 7 developers that know how it works, and each one is specialized in certain areas of it. There is no way that someone could come in and replace us without spending years working with the software first. There is no out of box program that could take the place of this specialized and customized software. And even if there was a company this department could out source too, they would not get bug fixes and new builds as fast as they do now.
- illumen 13y agoThe uncle of a company leader (CEO owner etc) owns a software company. Through a complex deal involving government grants, and a development deal with another company, the software if developed through them actually makes them money to build. Three of the developers are hired to the other company as consultants for a while, so they can explain how it all works. The rest of the developers are let go. Finally the original consultants are let go, at which point everything is outsourced to a team based out of Lithuania, India, and Brazil.
- shuaib 13y ago> At this particular moment in history, demand for developers outpaces supply. I thought it was demand for "good" developers that was outpacing supply. Otherwise there are many developers (even with the professional degrees) that can't pass the Fizz Buzz test (http://c2.com/cgi/wiki?FizzBuzzTest http://c2.com/cgi/wiki?FizzBuzzTest).
- grumblefoo 13y agoI've been using this metaphor for a couple years now, and I think that it can be taken further. Developers are like the car mechanics because they build the thing. There are an increasing number of tools being created to make developers lives easier, and as such, the bar to entry lowers. This is not the only career in computer science, though. Just like the auto industry, we need research to push the whole field forward (developing a new, more efficient programming language; or a better fuel injection system). We also have mechanics called IT people that help people with day to day problems that they encounter with their computers. Moral, if you want to stay relevant, make sure you know the things that push research. Learn the lambda and pi calculi. Learn category theory. Web development is an overpaid field, software engineering is not. Enjoy the easy money while it lasts, but know that its days are numbered
- gfodor 13y agoI'd argue that if you are going to focus on keeping abreast of research, you should focus on things that have much more obvious applications than various niche topics in programming language theory. For example, advances in machine vision, computer graphics, machine learning, and distributed systems seem to be much more meaty than category theory and lambda calculus for ensuring you do not get left behind in the next big wave of innovation.
- unono 13y agoProgramming is fundamentally different from most other occupations. We are actually building factories - automating manual tasks. If developer jobs start to become scarce, we'll be nearing a situation where there are no jobs at all for anyone. So, as a programmer, you're never at risk of falling into poverty.
- btilly 13y agoSo, as a programmer, you're never at risk of falling into poverty. I'm guessing you aren't old enough to remember the dot com bust then...
- simias 13y agoProgrammers fell into poverty after the dot com burst? That seems a bit extreme. Lost very high paying jobs, maybe.
- btilly 13y agoI personally knew competent programmers who, a couple of years after, I would describe as living in poverty. I believe that I am able to judge programming competence, and my bar for labeling poverty is not inaccurate.
- unono 13y agoI wasn't working then, but from my understanding (might be wrong), it was 'html coders' that had difficulty finding jobs, not actual coders.
- btilly 13y agoI personally knew a number of competent programmers who ran into extreme financial difficulty in that time period. However they didn't like to talk about it then or now, so I can't give names. They were, of course, a drop in the bucket compared to the number of people who had no business calling themselves programmers having trouble. But there were still lots of them. How do I know this? When I went to move from New York to the west coast in 2003, I took the precaution of taking a month to travel up down down the coast, so I could meet with people I knew and respected from online interactions. What I learned was that at the time, Portland was a disaster zone, Seattle almost as bad, Silicon Valley still had a huge hangover but was slowly on the road to recovery, and I should have no problem landing a job in Los Angeles. I therefore moved to Los Angeles and landed a job in about a week.
- johnfuller 13y ago> When the most frequent complaint you hear is “I wish recruiters would stop spamming me with six-figure job offers,” life’s gotten pretty good. As other have said many times here, a six figure job in some places is just enough to possibly be compared to a middle class lifestyle elsewhere in the U.S. Go look at the database of BART salaries, and as big as their pay appears, these guys went on strike. > WordPress does in fifteen minutes what once kept a freelancer busy for two months. And yet, you can still easily spend two months plus on a Wordpress project. Compare what people were building then compared to what people are building now. The great thing about web development is that we can continually move up the value chain. As some components get easier, that frees us up to work on something else, always pushing the boundaries outward. As those boundaries move, we are probably creating more work to do, not less. > Maybe you don’t think a total n00b can walk out of a nine-week training program and do your job. That noob better learn how to learn on his / her own. Really, who learns how to be a developer from a school? I don't have a computer science background, but does a computer science degree even teach this stuff? The bottom line is that it's a relentless grind to continue to learn and build on that knowledge. Not everyone has the drive to do that. It's far easier to pay for someone to feed you knowledge and pretend that you are getting somewhere. > To upset the labor market, one of two things needs to happen: an increase in supply, or a decrease in demand. I don't see supply outstripping demand happening anytime soon, if ever. I have been waiting for the hordes to come for years, but this hasn't happened. I would think it would have happened by now. And demand doesn't sit still either. As other markets emerge, they eat up their local talent.Sure, this local talent may work for far less than their U.S. equivalents, but for how long? When you have cost of living in certain regions of developing nations ratcheting up to be as high as any U.S. city and companies like Alibaba hitting huge numbers, then developers in these regions will get paid. They just have a bit of catching up to do, that's why we call them "developing." > No profession stays on top forever… just ask your recently graduated lawyer friends. Isn't that a crazy comparison though? This article mentions how low the friction is for getting into development, and then makes this comparison with a profession with a relatively huge friction. The development industry looks nothing like law. Part of the problem there is that the law profession built walls up that technology is tearing down. The development industry has no walls.
- learc83 13y ago
- logn 13y agoYes, programmers keep automating their own work. And we keep trying to find ways to bring in new programmers. But software keeps eating the world. I don't see an end to this. The auto-industry was largely reliant on a very specific vertical. Also, programmers (unlike auto workers) have not locked in long term benefits that hamstring a company. In fact, we've embraced taking on the risks of the company and staying nimble, hopping around and trying new things. If Google's whole workforce were guaranteed some sort of long term compensation for retirement, we might worry, but their long term promises are only via their stock price.
- smk11 13y agoprogrammers (unlike auto workers) have not locked in long term benefits This is true in many of the developer communities. But I work for a local government agency as a programmer. So, I have long term benefits and a retirement plan, and I assume there are lots of programmers in this category, they just aren't publicized like the start-up and web community. I am thankful for the influential programmers that live more risky and work at start ups, but there is also a place for programmers that have a secure job, working at companies/organizations with specialized software. However, I know that many bad workers have been created from these environments...there is always a group that will ruin it for everyone.
- michaelt 13y agoThe vehicle industry covers a lot of verticals. You've got your cars and motorbikes for consumers. Your 18-wheelers that stock large retailers. Your smaller trucks for home deliveries. Pickup trucks and vans for tradespeople. Special logging trucks and refrigerated trucks and vehicle transporters. Backhoes and bulldozers and oil tankers and cranes and RVs and quadbikes. Look around you right now - if it isn't air or water, chances are it travelled on a vehicle to get to you. And that's just vehicles that travel on the roads, there's also rail air and water vehicles. Covering a lot of verticals does not exempt you from price competition.
- RossPenman 13y agoThey are different because if developers were replaced by robots, developers would still be required to create and maintain those robots. The same can't be said for autoworkers.
- MichaelGG 13y agoYeah, automating all software development is probably equivalent to inventing general AI. At which point we're probably all very well off, or all screwed.
- klepra 13y agoDepends on where you live.
- ayush_gupta 13y agoThe comparison isn't even on the demand side. Auto industry is a single vertical. Software development is needed horizontally across most industries.
- jebblue 13y agoThe points seem all logical on the surface. There's just one thing that makes me disagree with the article as a whole. The software industry doesn't behave like any other industry. The industry changes and fluctuates as often as software gets refactored. It's like a billion springs permeating a billion sponges. It's silly putty for computers. I saw this coming reading articles about software as a kid. The one rule that hasn't changed in the 30+ years I've been writing software as a hobby or for pay is that the software disobeys all the rules of all the other industries. With software and compute power, if you can dream it you can build it and someone, somewhere, will want it.
- walshemj 13y agoYes production line industry with semi skilled labor is very very different beast to the IT industry trying to use two wildly different industries and draw analogies is a losing game. web development which the author comes from is a tiny part of the IT industry as a whole.
- gdy 13y agoCan someone who has experienced "social stigma of being a programmer" share what's it like?
- walshemj 13y agowell the NO 2 guy at BT labs (the uk equivalent of Bell labs) was confused with a car mechanic when he said he was an engineer.
- johnfuller 13y agoThe bottom line is that there is an infinite number of things to build and while software won't build these things alone, it's still a big component. Software didn't build the Space X rocket or the Google self driving car, but there is a lot of code which is a big part of making those things possible. All of the things that we can imagine in 50 years needs to have the foundations laid in part by software developers today. A factory worker has limited contribution to this future because of the constraints of the job, but software development is wide open. We may not be able to build the deathstar right now, but we can start working on the code for it. cd deathstar git init
- grandalf 13y agoOne difference is that new kinds of software exist every day and old ones become obsolete. Shopify is only suitable for a fraction of e-commerce sites, and before Shopify there was oscommerce, volusion, yahoo stores, magento, and dozens of other web 1.0 e-commerce platforms. If you are starting an e-commerce business and have $30 per month, Shopify is a great idea, but if you have a larger budget its limitations start to become impactful. Skills will definitely become obsolete, but code moves quickly and allows new ideas to become realized. What the author erroneously thinks of as a stable business model (e-commerce) is not, and there will be lots of people trying to improve upon it in ways that existing platform abstractions are insufficient for.
- samatman 13y agoI don't always seize my means of production. But when I do, I close it, stick it in a case, and put it in my backpack.
- samatman 13y agoTo follow up with something less pithy and more thoughtful: I'm from near Detroit. Auto work is a bad comparison, because auto workers need millions of dollars worth of equipment to do their job. Software developers are more like the film industry. Big operations need millions in equipment etc, but the individual actors, well, they just have to know how to act. Given that software as a service solves a problem the film industry is still wrestling with, and given that the film industry is still very much solvent at present, I think we're going to be okay.
- smk11 13y agoPlus, anyone can jump into the place of an auto-worker with very minimal training. That will never be the case for programmers.
- eli_gottlieb 13y agoI don't always seize my means of production. Why not?
- samatman 13y agoOften, I'm busy typing on it.
- warcher 13y agoThe thing about development, and it certainly may slow down eventually, especially as Moore's law staggers to a halt and broadband peaks, is that no matter what I build, everybody always, always, always wants more. Every framework I ever developed or integrated was met with a doubling of people's expectations. Make it better, make it slicker, give me this feature, et cetera. I think we've got between 40 and 50 years before we can even suggest hitting saturation with our current technical capabilities.
- GotAnyMegadeth 13y ago> especially as Moore's law staggers to a halt It hasn't even begun to slow yet, has it?
- hershel 13y agoFor the last 5 years , or even more it has slowed considerably. Nvidia even claimed in a famous article that next generation manufacturing processes have no price benefit.
- VLM 13y agoAn interesting shift in the market can be observed in that demand is dropping at the high end compared to in the past. Partially greater economic effect, partially lack of demand. The law might say the transistor density will increase, but if the market isn't willing to buy it, or the companies can't financially offer them, the law will fail but not for technical reasons. I think its a safe prediction the law will fail not for technical reasons but financial.
- hershel 13y agoI don't think demand for silicon(measured by area) for high end manufacturing processes had dropped. It might have shifted from pc to tablets/smartphones. but it's there. According to darpa , the end would probably come due to money. But even assuming unlimited money, 6nm is the size of a silicon atom. to go below we'll have to split the atom :)
- gfodor 13y agoWeb developers are the COBOL developers of this generation. Software engineering at its core is a universal skill whose applications will almost certainly have a shelf life of hundreds of years, though the various particular demand curves for specific applications of those skills is sure to vary wildly over time. Now would be an advisable time to start expanding your horizons if your core skill set revolves around creating web applications.
- BigBalli 13y agoToo bad autoworkers never made $100k+/yr even with inflation adjustment. Very far fetched.
- walshemj 13y agoI know of pit deputies and shot firers who make £100k in the UK
- Mc_Big_G 13y agoI worked in the auto industry for 10 years and I can tell you that, before the industry crash, I knew a guy who put the owner's manual in the glove box and made over $100k/yr. This was not uncommon and the guys that worked a lot overtime were millionaires. I remember one gentleman who was 72 years old and still working 7 days a week. I can tell you a lot of stories about the automotive industry that you probably won't believe.
- ufmace 13y agoThere are a few good points in this article, but I don't think it's all that insightful overall. A particular developer can be a lot like an auto worker, or they can be very different. The difference is continuous learning. The trouble with being an auto worker in the heyday of the industry is that, as far as I know, people generally learned a relatively small set of skills early in their career, and then expected to coast along on those skills for their whole life. All skills have a limited lifetime, and in the modern era, that lifetime can be very short indeed. If you got in and out at the right time and handled lifetime investments well, then you could do all right for yourself. If the timing of your one skill being obsolete doesn't work out well for you and you don't do anything about it, then you could find yourself broke and possessing no marketable skills when you were expecting to hit the peak of your career. In development, I have worked with people who view their career like this. They learned C++/MFC or some other technology stack that's getting rather long in the tooth decades ago, still work in it now, and show no interest in learning or trying anything new. I think these guys are in the same shape as the autoworkers. I think they'll do all right for the foreseeable future, but there's always the risk that the bottom will fall out of the market for the tech stack they know, and then most employers will see them as useless. There's no need to be like that, though, especially in a time when getting your hands dirty with new technology is so easy. The developer who can do good work in 2 or 3 tech stacks and is always learning more about his main ones and any others that look interesting will always be employable - if one goes dead, you can get a job working in another one, or learn whatever the new one is yourself. I'd say it generalizes even more. Anybody who has the drive and intelligence to continuously learn new things will always be able to make money. Anybody who wants to learn one thing and coast on that their whole life will always be at risk of losing it all.
- VLM 13y agoThere tends to be a lot of demonizing and blaming the victim in general on HN for people who won't learn new skills. I've coasted by for a couple decades really only having two "tech" skills. I'm really, really good at systems analysis, and I'm pretty good at translating user requirements into code more or less on time and more or less with few bugs. Sure the tools and techniques have changed a bit, but much less than some would claim. After you learn your 5th or 6th language the 7th isn't a big deal. I really don't see any deep need to learn new skills beyond those two as long as I stay in the field, after all, its worked very well so far... Eventually due to ageism I'll have to do "something" else. Maybe learn the skill of management, or sales, or something like that. Donno. What does a good techie do when no one will hire him for non-tech related reasons? Maybe start a tech company, thus the interest in HN... On resumes the "no new skills" crowd knows you can just make it up in six months if you want. For a software dev who's any good, how long does it take to learn something, contribute to an OSS project, etc? Not very long, thats for sure. New stuff comes along at every job I've ever had, and I have to implement it in a month or so. Not hire a new guy, not go take a class, production code. Its so not a big deal. There's no point in learning a new skill and telling anyone at work about it, unless you think its funny to get escorted out... after all, why update the resume unless you're looking? The other big mistake is virtually none of the detroit workers had the skill of making cars. There are people who have the skill of making cars. I have a cousin with that skill, who's a large diesel mechanic who has a hobby of tearing down cars and rebuilding, all by himself, bare metal components up, including (obviously?) engine assembly. He's stripped and rebuilt two classic corvettes and a ancient jeep, so far. Virtually no autoworkers can do that other than coincidentally as a hobby. They can tighten a bolt on a line, or align an assembly, or insert/stack partially finished parts, or press a e-stop button if the robot goes nuts. They suffer from HR doing "keyword selection" just as much as we do now. Oh look he worked on a car line, well he is totally unqualified to tighten the same bolt on our truck line. Anyway, none of them can build a car. Once, a long time ago, I worked in IT at a large regional printer. That doesn't mean I was a "press worker" or I could do much of anything with putting ink on paper other than program ethernet switches for embedded control devices. "autoworkers" are the same way.
- deleted 13y ago[deleted]
- wavesounds 13y agoHappy Labor Day!
- MichaelMoser123 13y agoAutoworkers used to earn a decent salary, now it is programmers; Wow, now you need to have a degree in order to be somebody. And in a hundred years you will absolutely need to have a PhD in order to make ends meet ? Maybe its all about supply and demand: only rare skills are worth something; if the once valued skills get common then all the advantages go out of the window (tm).
- stewartjarod 13y agoThere will be another distinguishing mark on programmers. Those that can write their own code and those that can fumble the pieces of other's code together to create a product. There will be a lot more of the latter in the future than there has ever been.
- scotty79 13y agoWhy more programmers are no threat to programmers jobs? Because more programmers create more programs and more programs need more programmers (for updates and maintenance).
- shubb 13y agoI'm not sure I recognize this privileged world you describe. Maybe you won't recognize mine. It's 7pm. About half the team is in the office with me (although all the people managers have gone home). We will be here a while. No one in the room earns more than 10% more than the UK median salary. The highest paid is a front end guy who sits to my right. The two behind me earn less than the median, and live with parents. They have been writing software for 3 years. On external contracts, the customer pays about double what they get paid, 150 a day. Given that rate also needs to support sales and admin, they could get a little more but not a huge amount. Sales tell me our day rates are too high, and it's costing work. Other companies in our industry (defence contracting) pay a bit more, but not a huge amount. I got offered about 50% more to work on consumer electronics last month, but that is still 50% more than median, not 800%. I think what you describe has already happened. Edit - I think this is overly negative. Programming remains a really nice job. You solve interesting problems, you work in a comfortable office, and the culture is nice (people usually treat eachother well). It's just not paid that well now.
- jaymzcampbell 13y agoI'm interested to know where you're based, I take it it's not London? A day rate of £150 per day to the customer sounds very low; it's hard to find contract rates that low on the likes of Monster across the UK and typical to see £250-500, so double that for the company hiring out. I've seen rate cards for agencies in advertising charging out developers on projects from £500 to over £1,000 depending on what exactly is being worked on. If £150 a day is too much and costing work anything lower seems unsustainable to run anything more than a lifestyle business for a few select people at the top. If it's 7pm and the developers are likely to be still there for a while - is that "the norm"? Then you are in effect taking a pay cut already on what sounds like below market rate wages. This sort of practice is toxic. It's ok to work late but when it's expected as part of the job but not without any compensation (can be extra time off, not just money) then this really annoys the hell out of me. Someone higher up is making money out of this. That might be the status quo but I would really consider working on the C.V. and widening out skills and look elsewhere - there's no harm in it. The guys behind you paid less than median (£21.3k in 2012 according to Wikipedia) and that have been at it for 3 years - from that I get the impression they were fresh out of university and this was the first job? And the highest paid guy at just 10% more, so around £23k, is there no CTO or senior developer? To me it sounds like someone's taking advantage of young, enthusiastic energy here. More so with the "we will be here a while" comment - you should work out what your effective annual salary is based on that; otherwise you can just let it slide and fall into acceptance. If your contact states 9 - 6 the company needs to appreciate the above and beyond work. That's what it is, no matter what others might tell you. We recently hired for a mid-level developer role at our office in Hoxton and that was around the £40k mark which seems to be around right. As the tech director there I regularly get unsolicited CVs via recruiters and salary ranges requested typically range from the £30k mark up to around £60k. I don't mean to come off as in anyway 'know it all'y or 'just do x' - I'm genuinely interested in the situation as a fellow UK based dev. Your situation contrasts starkly with my developer friends (based in London, Belfast, Hertfordshire & Leeds) so I'd like to hear more if possible. I often extol the virtue of learning developer skills to younger folk who I interact with and have always painted it as a pretty good way to get a good head-start financially over many other occupations. When I started out at just above the median I was so thrilled that I was actually getting paid to do what I started out doing in my bedroom as a young kid. After passing the 30 mark I've come to realize it's about what value you can provide to the company, there's no shame in wanting to be out at 6, for one thing realistic timing plans that actually reflect reality are far more useful than ones papered over with hours upon hours of hidden overtime - I'm not saying that hard, late nights are out of the question - I just don't expect it to be treated as the norm' or assumed unless it's also reflected in compensation of _some sort_ (we've in the past traded late nights for conference & flight fees for instance). There's also no shame in taking a look what else is out there and moving if you have to - there is some give and take on your part in progressing. Moving jobs is usually the easiest way to significantly bump your pay grade. It's hard work but can really be worth it in the long run.
- ghostdiver 13y agoThis article is so true, software dev job market will implode in long run.
- adw 13y agoGeneralizing from the Valley to anywhere is insane. The Valley, right now – like it or not – is the NFL for geeks. (For better and worse.)
- Aqueous 13y agoThere are some parallels but the analogy falls apart. Even the most perfect car does only one thing very well: get people from point A to point B. That is, there is a finite amount of autorepairs and new car manufacturing that is done and will ever be done, and that ceiling is related to how many people own cars or want to own one at any given point in time. But the potential domains for software automation are unlimited. The demand for software programmers will keep increasing, continually, until all the work that people do in their lives is automated by software. The time to enjoy being a software developer might be finite, but I don't see the plateau happening any time soon.
- Killah911 13y agoSo, I don't know if people remember the early 2000s, but it wasn't a terribly great time to be a programmer. All the jobs were going out to India. However, I learned a very important lesson. You have to be competitive. If you were someone who couldn't see past cobol, you did become obsolete. While programmers in India are still relatively less expensive than their counterparts in the US, top programmers are still sought after and make significantly more than the rest. Sure the barrier to entry is "low", but it isn't that low. I think one of the main problem is, calling someone a programmer is an extremely "broad" term. I know some who can barely string together a few lines of PHP code and other who design and build complex systems which run the world and improve people's lives. If you're a programmer who just "codes" HTML, which you learned over one weekend and haven't take the time to improve your craft, sure you may be working now, but you're likely to get wiped out easily since the barrier to entry into your line of work would be very low. In a sense the OP is right in that programmers shouldn't be complacent. I know a lot of C coders who have serious BS ego issues and refuse to do anything but C and then complain that they can't find work after being laid off. BUT, I'm not shivering in my boots due to Stripe and Wordpress. Any programmer knows there's a bunch of crap that's tedious work which can be automated away. The good ones automate them and improve their craft and focus their energies on building better systems. I think that even with Wordpress, Stripe etc, there's a lot of room form improvements in the way we develop. I recall spending days getting a dialog box UI just right in MFC. I thought it was stupid then and after using C#, never used MFC to build a dialog box ever again. Result wasn't that I'm out of a job. I actually have been able to produce a lot more. Programmers are in ever more demand than before. Sure the field will probably get tapped at some point, but to say it's going to be due to "automation" which has been a staple in our profession since the very beginning is simply inane. Going with the autoworkers analogy, there are people who turn wrenches and people who figure out six sigma. If you're doing something as simple as turning a wrench, sure, you will get easily replaced by robots. But if you're innovative and competitive, you'll be significantly harder to replace and you can probably find applications for your skills in many more places. There are certain skills you just can't automate away so easily. I would argue that programmers/developers will have jobs long past even doctors (maybe). Repetitive tasks can easily be automated away, creativity and innovation on the other hand aren't quite as easy. (FYI, the reason all programming jobs aren't just in India is because the US still rocks when it comes to creativity and innovation, based on my own experiences as an employer/manager and in speaking with others in the same position who have programming staff worldwide)
- diydsp 13y agoA point repeated here has been "keep your skills flexible." A lesson we could learn that would improve upon the auto industry disaster would be to consider the "product line" itself. The auto industry was notoriously monofilamental in its innovation, as its CEOs preferred it. Their conservative operation proved a great long-term investment, with an eventual crumbling down hitting hard in the 1980s and hardly recovering. Innovation represents hours sweated and is always rewarded. So far the computer science industry has been well-motivated to continue innovation, as computation becomes one of the world's standard utilities. But once it's all up and running _and_standardized, it will only take a smaller number of people to run it, like the power grid, water supply, phone system, etc. It is all like plumbing, and like plumbers, there are household ones for household needs like web storefront/office/communications desks and industrial plumbers, but most of the unique, research-y plumbers are in a small, elite group who are innovating on their own and sharing their work with the public and are well-compensated. I think that's the effect we'll see, a narrowing or thinning of the industry somewhat, but it definitely won't settle until after use-cases are standardized and we're still a zillion miles from that. Imagine NASA doing a shuttle lunch with everyone from the control room at home in their backyards cooking BBQ with their family :) Cell phone in one hand, spatula in the other.
- deleted 13y ago[deleted]
- MisterBastahrd 13y agoAn autoworker needs an entire factory around him to do his job, along with a couple hundred other developers. He's nothing more than a cog in a wheel, made to do one specific thing over and over again to bridge the gap when there is a task a machine can't handle. A developer just needs a computer, a compiler, and some motivation.
- kenster07 13y agoMany commenters are too lost in their own egos to speak rationally about this issue. CS is not a "cool" major in colleges, and programming is not a cool profession among tweens. Until there is a significant cultural shift, which I would bet will not happen any time soon, the labor pool will not be commoditized in the USA. On top of that, the skill cap for programming is substantially higher than it is in assembly line manufacturing. Programming may be more comparable to engineers who actually design the cars, but those jobs are not commoditized either.
- quaffapint 13y agoIt's not a good time to be a developer as it used to be. That was 10+ years ago, now the pay is much lower than it used to be. You used to be able to hop jobs and make good jumps, now around here you hold on to those old jobs so you don't end up with a pay cut. So, it's much more limited, though it encourages more side work I guess, just so you have something interesting to work on.
- eliben 13y agoI used to feel uncomfortable after reading articles like this. But as the years went by, I gained more experience, and understood what programming is really about. I no longer worry. But if you spent a total of 2 months on your programming education and are now gainfully employed copying and pasting answers from Stack Overflow into your editor, perhaps you should.
- pearjuice 13y agoIs it really the golden era of programming in America? In Europe we still get underpaid for what we do yet there is an extreme shortage of good engineers. I have seen a lot of my network move to America and haunt software engineering positions in SV but always thought they were chasing a lottery ticket. People drop out of school here and move to the States because there is so much demand and half of what they learn is not even applicable in real life jobs "In America you can actually get a job if you can prove you can program - without a degree!" is what I hear a lot. How true is this? Is it a gold rush or are we not even close to the peak? Are they exaggerating? What is the demand like? Is a degree worth it if you are just in it for the paper?
- nvarsj 13y agoI'm moving to the UK from the US in a few months. I'm taking a pretty big salary cut, but from my research, salaries have increased quite dramatically in the last 3-5 years. So I'm cautiously optimistic that they'll keep growing.
- FurrBall 13y agoThere are 2 kinds of work. 1. Execution of a process. 2. Creation of a process. Execution can be automated. A factory can be automated with robots. Someone who makes backups can be automated with a script. But creation (of a process) cannot be automated. Until we have a major breakthrough in AI our jobs are safe. Most programming is the creation of a process, not the rote following of a process. "Programmers" making cookie-cutter-CRUD apps may need to worry! Our only threats are over supply and under demand. We are currently on the winning side of supply/demand. Competition with low-wage countries has not been able to significantly hurt us they way it has with factory work. We are in a good spot.
- DigitalSea 13y agoWhile it seems many don't agree with the article (as usual) I do. Developers are sitting pretty at the moment because the Internet in the greater scheme of things is brand new. It wasn't really until the early 2000's the Internet exploded in popularity and got a whole lot more complex. There is always some new hot language startups and companies are clamouring to use, every new language or framework seems to create a gold rush of sorts (Rails developers were once white hot property). But the sad matter of the reality is, more and more people are learning how to create a website. And while little Timmy who knows HTML and a little CSS won't be taking your jobs any time soon, as the supply rises there will always be a plethora of small jobs that Timmy would be able to do leaving the few actual big and complex jobs for the many developers fighting for the job. I personally think we are a very long way off oversupply in the development sector (especially web). My advice would be to continually learn as many new skills and techniques as possible so if the day ever comes you are at risk of being replaced by a WYSIWYG editor that generates the code for you, you might have a chance of keeping your job. Software is a lot harder to automate for the moment, but with websites it's at the point where content management systems like Wordpress already make it easy for people from kids to senior adults to make a website without even having to touch a line of HTML, CSS or Javascript. Automated tools can only get you so far, we'll always need designers to design the look and feel of a website, developers with a grasp of modern web technologies and languages to program whatever it is that's creating the website to ensure its output is up-to-date. I've been preparing myself now for the future. If automation does happen and it will, nothing can truly be 100% automated, but if it does happen, I'll be the guy running the automation stuff, not living out on the street because I was too naive too think it could never happen to a developer like me. PS. Send some of those recruiters offering six figure salaries my way please...