10 ms·
The uncertain future of coding careers and why I'm still hopeful
- billy99k 1y ago"What I see is a future where AI handles the grunt work, freeing us up to focus on the truly human part of creation: the next step, the novel idea, the new invention. If we don’t have to spend five years of our early careers doing repetitive tasks, that isn’t a threat, it’s a massive opportunity. It’s an acceleration of our potential." The problem is that only a fraction of software developer have the ability/skills to work on the hard problems. A much larger percentage will only be able to work on things like CRUD apps and grunt work. When these jobs are eliminated, many developers will be out of work.
- anilgulecha 1y agoIMO, if this ends up occuring, it will follow how other practitioner roles have evolved. Take medicine, and doctors for eg: there's a high bar to reach to be able to do a specialist surgery, until then you hone up your skills and practice. Compensation wise it isn't lucrative from the get-go, but can get so once you reach the specialist level. At that point they are liable for the work done. Hence such roles are typically licensed (CAs, lawyers, etc). So if I have to make a few 5 year predictions: 1. Key human engineer skills will be to take liabilty for the output produced by agents. You will be responsible for the signoff, and any good/bad that comes from it. 2. Some engineering roles/areas will become a "licensed" play - the way canada is for other engineering disciplines. 3. Compensation at the entry level will be lower, and the expected time to ramp up to productive level will be larger. 4. Careers will meaningfully start only at the senior level. At the junior level, your focus is to learn enough of the fundamentals, patterns and design principles so you reach the senior level and be a net positive in the team.
- turbofreak 1y agoCanada?? They can’t build a subway station in 5 years nevermind restructure a massive job sector like this lmao
- bluefirebrand 1y agoYou're being downvoted but you're actually spot on Calgary was supposed to have a new train line, planning has been in motion for years. Back in 2019 when I bought my house, the new train was supposed to open in 2025. As far as I know not a single piece of track has been placed yet. So... Yes
- turbofreak 1y agoYes this is status quo in Toronto but it’s a Canada-wide corruption issue. https://www.cbc.ca/news/canada/toronto/eglinton-crosstown-opening-june-ttc-1.7400691 https://www.cbc.ca/news/canada/toronto/eglinton-crosstown-op...
- gnabgib 1y agoHey, they knocked down Eau Claire. So.. progress?
- chii 1y ago> At the junior level, your focus is to learn enough of the fundamentals, patterns and design principles so you reach the senior level and be a net positive in the team. I suspect that juniors will not want to do this, because the end result of becoming a scenior is not lucrative enough given the pace of LLM advancement.
- AbstractH24 1y agoThere’s a sweet spot right now to be in. Early enfough career to have gotten in the door, but young enfough to be mailable and open to new ways.
- deleted 1y ago[deleted]
- fn-mote 1y agoHad to laugh at #4… that’s where I thought we were now.
- gitgud 1y ago1. Already true, no company will make the AI agent liable for its output, it’s always the programmer 2. Unlikely, as most software won’t result in death/injury… whereas a structural engineering project is much more life threatening. 3. I actually think entry level engineers will be expected to ramp up to productive levels much much quicker due to the help of AI 4. Already true
- 123yawaworht456 1y ago90% of real grunt work is "stitch an extra appendage to this unholy abomination of God" or "*points at the screen* look at this shit, figure out why is it happening and fix it". LLMs are more or less useless for either of those things.
- zeta0134 1y agoAn LLM can certainly try to consume an extremely poorly specified bug report, in half English half the user's native language, then consume the entire codebase and guess what the devil they're actually referring to. My guess is the humans are better at this, and I mostly speak from experience on two separate support floors that tried to add AI to that flow. It fails, miserably. It's not really possible for an LLM to pick up on the hidden complexities of the app that real users and developers internalize through practice. Almost by definition, they're not documented! Users "just know" and thus there is no training data to ingest. I'd estimate though that the vast, vast majority of bugs I've been assigned originate from one of these vague reports by a client paying us enough to care.
- csomar 1y agoLLMs are very good at fixing bugs. They do lack broader contexts and tools to navigate the codebase/interface. That's why Claude Code was such a breakthrough despite using the very same models you run on the chat.
- xarope 1y agovery good at fixing bugs like these, which requires a senior developer to address and prompt? https://news.ycombinator.com/item?id=44159166 https://news.ycombinator.com/item?id=44159166 or this about MS pushing for more internal AI usage, and the resulting hilarity (or tragedy, depending if you are the one having to read the resulting code)? https://news.ycombinator.com/item?id=44404067 https://news.ycombinator.com/item?id=44404067
- danielbln 1y agoI disagree, agentic LLMs are incredibly useful for both.
- chii 1y ago> A much larger percentage will only be able to work on things like CRUD apps and grunt work. which is lower valued, and thus it is economically "correct" to have them be replaced when an appropriate automation method is found. > When these jobs are eliminated, many developers will be out of work. like in the past, those developers will need to either move up the value chain, or move out into a different career. This has happened before, and will continue to happen until the day humanity reaches some sort of singularity or post-scarcity.
- bugglebeetle 1y ago> which is lower valued, and thus it is economically "correct" to have them be replaced when an appropriate automation method is found. Textbook example of why this “economic” form of analysis is naive, stupid, and short-sighted, (as is almost always the case). AI models will never obtain the ability to completely replace “low value work” (as that is not perfectly definable or able to be defined in advance for all cases), so in a scenario where all engineers devoted to these tasks are let go, what you would end up with is a engineers higher up the value chain being tasked with resolving the problems that result from when the AI fails, underperforms, or the assessment of a task’s value was incorrect. The cumulative effect of this would be a massive drain on the effectiveness of said engineers, as they’re now tasked with context switching from creative, high-value work to troubleshooting opaque, AI code slop.
- chii 1y ago> AI models will never obtain the ability to completely replace “low value work” if this were truly the case, then companies that _didn't_ replace the "low value work" by ai and continued to use people will outperform and outcompete. My prediction is entirely predicated on the ability for the LLM to do the replacement. A second alternative would be that the cost of the "sloppy" ai code is externalized, which is not ideal but the past history has any bearing, externalization of costs is rampant in corporate profit struggles.
- blackbear_ 1y ago> AI models will never obtain the ability to completely replace “low value work" Maybe, but this is not the meaning of replacement in this context and it need not hold for the "economic" reasoning to work. All that matters is that AI makes developers more productive, as measured by number of (CRUD or whatever) apps per developer per unit of time. If this is true, then the current supply of apps can be provided by fewer developers, meaning that some of the current developers aren't needed anymore to sustain the current production level. In this scenario lower level engineers still exist, they are just able to do more in the same time by using AI.
- csomar 1y agoThis. There are millions of software developers. There are hundreds (thousands?) that are working on the cutting edge of things. Think of popular open source projects used by the masses, usually there is one or a handful of developers doing most of the work. If the other side of the puzzle (integration) becomes automated, 95% or more of software developers are redundant.
- nyarlathotep_ 1y ago> The problem is that only a fraction of software developer have the ability/skills to work on the hard problems. A much larger percentage will only be able to work on things like CRUD apps and grunt work. It's also availability of those jobs, even for those who would otherwise be capable. Some of the highest-skill software jobs, things like writing a cross-platform renderer for a AAA game engine, or JIT compiler optimizations or something else esoteric are very scant jobs and only ever needed in very small quantities at very specific places. The overwhelming majority of work is some variety of CRUD with a website, and all of the "supporting cast" (CI/CD things, cloud stuff, etc). Ironically this is why LLMs are so successful at automating it, how many React repos are there on GitHub?
- Arainach 1y agoThis is a rational take, which is why it is wrong. I agree that we're not about to be all replaced with AGI, that there is still a need for junior eng, and with several of these points. None of those arguments matter if the C suite doesn't care and keeps doing crazy layoffs so they can buy more GPUs, and intelligence and rationality are way less common than following the cargo cult among that group.
- simonw 1y agoThe C suite may make some dumb short-term mistakes - just like twenty years ago when they tried to outsource all software development to cheaper countries - but they'll either course-correct when they spot those mistakes or will be out-competed by other, smarter companies.
- reactordev 1y agoThe market will always respond. When it happened before, younger - smarter - more efficient competitors emerged.
- ringeryless 1y agothis. i mean, look at xerox or big blue
- jimbob45 1y agoHR can remain irrational longer than I can remain solvent.
- deleted 1y ago[deleted]
- shikon7 1y agoUntil someone makes the idea fashionable to replace HR with AI.
- 1y ago
- smallstepforman 1y agoGoogle search is giving us a taste of AI summarised results, and for simple things its passable, but ask a serious question and you get good looking garbage. Yes, I know its early days, but looking at the current output quality we have nothing to worry about. It will be used as calculators, offload some menial repetetive task which can be automated, but the next gen of developers will still be tasked to solve complex problems.
- readthenotes1 1y agoTry asking Perplexity for a real taste. It works far better than google's--good enough to make searching fun again. Try coding with Claude instead of Gemini. Those that do tell me it is well beyond. Look at the recent US jobs reports--the draw down was mostly in professional services. According to the chief economist of ADP "Though layoffs continue to be rare, a hesitancy to hire and a reluctance to replace departing workers led to job losses last month." Of course, correlation is not causation, but everyone white collar person I talk with is saying AI is making them far more productive. It's not a leap to figure out that management sees that as well.
- simonw 1y agoGoogle's AI overviews is the single worst AI-driven experience in widespread use today. It's a mistake to make conclusions about how good AI has got based on that. Have you tried search in ChatGPT with o4-mini or o3?
- cwalv 1y agoI don't use it that much, but I have noticed these AI overviews still seem hallucinate a lot, compared to others. Meanwhile I hear that Gemini is catching up or surpassing other models, so I wonder if I'm just unlucky (or just haven't used it enough to see how much better it is)
- input_sh 1y agoOne is their state-of-the-art model, the other one's the best model they can run at scale and speed people expect from a search engine.
- deleted 1y ago[deleted]
- lawgimenez 1y agoI just recently inherited a vibe coded project in iOS (fully created with ChatGPT), and not even close to working. This is annoying.
- grogenaut 1y agoI helped my brother a few times with iOS apps he had folks from upwork build. They also didn't work beyond the initial version. They always wanted to rebuid theapp from scratch for each new requirement.
- lawgimenez 1y agoEverything's a mess, a thousand commits and PRs from ChatGPT. Code won't compile because Codex it seems doesn't seem to understand static variables. And now this error The project is damaged and cannot be opened due to a parse error. Examine the project file for invalid edits or unresolved source control conflicts.
- simonw 1y agoQuitting programming as a career right now because of LLMs would be like quitting carpentry as a career thanks to the invention of the table saw.
- chii 1y agoMore like quitting blacksmithing due to the invention of CNC.
- globular-toast 1y agoCNC produces something no blacksmith could. The same cannot be said of LLMs.
- bluefirebrand 1y agoI agree, but it doesn't matter what we think Execs are convinced LLMs produce something that no programmer ever could. Or at least the same thing, faster than any programmer ever could So they will drive us off a cliff chasing it
- globular-toast 1y agoLuckily people who know better are allowed to found companies and compete with them. I look forward to large companies with several levels of clueless execs going under, especially because I'll still be here to pick up the pieces in exchange for a tidy sum.
- guappa 1y agoThey are, but right now it's a hard sell with VCs
- globular-toast 1y agoYeah. I would recommend everyone to budget for being able to "weather a storm" for a few years regardless of what they do. If you have liabilities requiring you to maintain your current income indefinitely then you need to fix that. Personally I sleep at night knowing I could take a 33% pay cut tomorrow and not even make any lifestyle changes, let alone struggle with any liabilities. Live way below your means. Be Stoic.
- Animats 1y agoIt's hard to see manual coding of web sites remaining a thing for much longer.
- globular-toast 1y agoMost people younger than 30 probably haven't "manually coded a website" anyway.
- throwaway0123_5 1y agoI doubt there's any age bracket where most people have manually coded a website tbh.
- sublinear 1y agoIf you're talking about personal websites I think that ship sailed almost 20 years ago with the rise of social media. If you mean business websites, they are just about the most volatile code out there with crazy amounts of work that never stops. It's still a form of publishing after all. Every marketing decision has to filter through design agencies, legal and compliance, SEO, etc. before it gets handed off to web devs. Then the web dev has to push back when a ton of details are still wrong. Many decisions after testing are left unresolved by the time it goes live and those pages still need maintenance until its expiry. Smaller businesses also have these problems with their websites, but with less complexity until they get more attention from the public.
- bluefirebrand 1y ago> I think that ship sailed almost 20 years ago with the rise of social media Well forget social media even. Wordpress, and now Shopify have definitely eaten the personal website
- sublinear 1y agoThe best part about a personal website is that you can do whatever you want. A part of my mind is more convinced by the day that people don't want all this complexity and the AI nonsense might be the final straw. By comparison, just writing the damn HTML yourself is a breeze. I get that most people don't really want to write code, but I'd compare it to cooking. You don't have to be a chef just to eat a decent meal made the way you like. No, what's really wrong here is a lack of simple build tools and collections of stable libraries for web that don't try to lock you in. This is what pushes people to use crapware instead. I can't find a decent pre-made pizza crust at the grocery store either, so sometimes I just order delivery instead of kneading dough.
- Apocryphon 1y agoAI is a red herring. The current malaise in the industry is caused by interest rates. Certainly, AI has the potential to disrupt things further later down the line, but the present has already been shaken enough by the whiplash between pandemic binging and post-ZIRP purging.
- ifwinterco 1y agoThis is my read as well. Hard to say for sure because chatGPT came out at almost exactly the same time the post-covid wheels where starting to fall off anyway, but I think it's fair to say that as of right now you can't really replace all (or even many) of your engineers with AI. What you definitely can do though, is fire 20+% of your engineers and get the same amount done simply because more is not necessarily better
- disambiguation 1y ago> We are all, collectively, building a giant, shared brain. "Shared" as in shareholder? "Shared" as in piracy? "Shared" as in monthly subscription? "Shared" as in sharing the wealth when you lose your job to AI?
- jbs789 1y agoAs this started with career advice, two points: the world values certain things (usually making people’s lives easier, one version of that is building useful tools) and the individual has a set of interests and skills. Finding the intersection of that for you should help guide you toward a career that the world values and interests you (if that’s important to you). I’m looking at this as the landscape of the tools is changing, so personally anyway, I just keep looking for ways to use those tools to solve problems / make peoples lives easier (by offering new products etc). It’s an enabler rather than a threat, once the perspective is broadened, I feel.
- sota_pop 1y agoThe japanese concept that neatly encapsulates your first idea is called ikigai.
- mirsadm 1y agoInitially I felt anxiety about AI and it's potential to destroy my career. However now I am much more concerned about what will happen in 5 or 10 years of widespread AI slop. When humans lose motivation to produce content and all we're left is AI continually regenerating the same rubbish over and over again. I suspect there'll be a shortage of programmers in the future as people are hesitant to start a career in programming.
- octo888 1y agoI wasted 2 days using Cursor with the 3.7 thinking models to implement a relatively straightforward task (somewhat malicious compliance with being highly encouraged to use the tools, and because a coworker insisted I use their overly complex mini framework instead of just plain code for this task) It went round in circles doubting itself. When I challenged it, it would redo or undo too much of its work instead of focussing on what I'm asking it about. It seemed to be desperate to please me, backing down to my challenging it. Ie depending on it turned me into a junior coder. Overly complex code, jumping to code without enough thought etc Yes yes I'm holding it wrong The code they create seems to be creating a mess that also is solved by AI. Huge sprawling messes. Funny that. God help us if we need to clear up these messes if AI dies down
- bluefirebrand 1y agoIf it helps any, this is not just you. I'm having the same kinds of problems, both with "being pressured to use the tools" and also being completely run around in circles when I try
- zkmon 1y agoIt's not just the grunt work going to AI. Actually it is the opposite. Grunt work of dealing with mess is the only thing that is left for humans. Think of legacy systems, archaic processes, meaningless workflows, dealing with other teams and people, politics of work, negotiations, team calls, history of technical issues... AI is a new recruit that has massive general abilities, but has no clue about the dingy layers of the corporate mess.
- asimpletune 1y agoSoftware engineers should unionize. We’re not real engineers until we have professional standards that are enforced (as well as liability for what we make). Virtually every other profession has some mandatory license or other mechanism to bring credibility and standards to their fields. AI just further emphasizes the need for such an institution.
- bdcravens 1y agoA substantial amount of our field would then be unemployable. A significant number of whoever was left would be complaining about the new standards.
- Fendy 1y agoI think a lot of people are feeling this, not just engineers. Engineering already has a high entry bar, and now with AI moving so fast, it’s honestly overwhelming. Feels like there's no way to avoid it—we either embrace it, actively or passively, whether we like it or not. Personally, I think this whole shift might actually be better for young people early in their careers. They can change direction more easily, and in a weird way, AI kind of puts everyone back at the starting line. Stuff that used to take years to master, you can now learn—or get help with—in minutes. I’ve had interns solve problems way faster and smarter than me just because they knew how to use AI tools better. That’s been a real wake-up call. I’m doing my best to treat AI as a teammate. It really does help with productivity. But the world never stop changing, and that’s exhausting sometimes. I try to keep learning, keep practicing, and keep adapting. And yeah, if I ever lose my job because of AI... ok, fine, I’ll have to change and try getting another, maybe different job. Easy to say, harder to do—but that mindset at least helps me not spiral.
- skydhash 1y agoThe true value of experience comes in two ways: Knowing when not to do something; and knowing the shortest path to produce the result needed. More often, the result of juniors using LLM is a frankenstein ball of mud that is close to its implosion point. Individual features are part of a system and are judged based on how they contribute to its goal, not how they are individually correct.
- Fendy 1y agogreat point
- AstroBen 1y agoAnd a person's contribution to a business isn't their one-day or one-week productivity. Those juniors eventually learn how not to create that ball of mud.. well at least they used to If LLMs short circuit our growth as developers I can see the longer term quality and output being much worse than it was pre-AI
- rightbyte 1y ago
- 3D30497420 1y ago> We are all, collectively, building a giant, shared brain. Every time you write a blog post, answer a question on a forum, or push a project to GitHub, you are contributing to this massive corpus of human knowledge. I would be more excited about this concept if this shared brain wasn't owned by rich, powerful people who will most certainly deploy this power in ways that benefit themselves to the detriment of everyone else.
- gruez 1y ago>if this shared brain wasn't owned by rich, powerful people [...] There are open weights models
- moritzwarhier 1y agoBut so far, the point stands, as far as I'm concerned, as these are not competitive (in my humble experience). And the platforms where valuable input comes in (StackOverflow, Reddit, AI tools themselves) all have licenses that would allow them to become rent-seekers on AI models and challenging open models to not provably train on "their" data (the user contributions). This giant clusterfuck could only be avoid when the major social media platforms and coding agents would each use CC0 license for the content they collect. Take this with a huge grain of salt as I'm not a lawyer, not even a well-informed layman. But recent news seem to demonstrate that knowing law is not important anyway, only having capital is. More specifically, I still don't know what the current situation with "fair use" is around training data.
- gruez 1y ago>But so far, the point stands, as far as I'm concerned, as these are not competitive (in my humble experience). Source? The popular narrative, at least a few months ago was that Chinese AI models like deepseek were not far behind models from OpenAI, hence the stock market crash. eg. "DeepSeek’s models are much cheaper and almost as good as American rivals" https://archive.is/2yNzH https://archive.is/2yNzH >And the platforms where valuable input comes in (StackOverflow, Reddit, AI tools themselves) all have licenses that would allow them to become rent-seekers on AI models and challenging open models to not provably train on "their" data (the user contributions). Is there any evidence this actually caused open weights models to be worse? As much as you hate this "rent seeking", it's mostly a sideshow. If open weights models are competitive, then the proof is in the pudding, no need to fret about the morality platforms "rent seeking" over UGC. >This giant clusterfuck could only be avoid when the major social media platforms and coding agents would each use CC0 license for the content they collect. This makes no sense. You can't take some copyrighted content you scraped (eg. some blog post), relicense it as "CC0", and then redistribute it. That's straightforwardly copyright infringement. Search engine and AI companies get away with this because they're not redistributing the raw data itself, but rather a transformed version (ie. snippets and AI models respectively), which helps it pass as "transformative" under the "Purpose and character of the use" part of the fair use test. >More specifically, I still don't know what the current situation with "fair use" is around training data. There was a recent court ruling in the US that basically ruled it's fine to train on copyrighted books without permission, but you can't pirate books to obtain them. This hasn't reached the supreme court yet, so it's not final.
- GardenLetter27 1y agoI feel exactly the same way. I just wish they were forced to publish open weights in return for using copyrighted materials in the "brain".
- guappa 1y agoNo no… you see we in the west are all about freedom. That's why we ban companies that do publish the weights! https://www.aljazeera.com/news/2025/2/6/which-countries-have-banned-deepseek-and-why https://www.aljazeera.com/news/2025/2/6/which-countries-have...
- anovikov 1y agoSad truth is that we probably don't see any AI effects on hiring yet, or maybe only minimally so. For now, this is just normal cyclic shit. The worst is yet to come.
- pclowes 1y agoWhy are software engineers paid well to date? Successful software uniquely benefits from operational and financial leverage. Which creates the term "software margins" Financial leverage: It is cheap to write code, experiments are inexpensive. A million dollars in funding for a B2B SaaS gives many more shots on goal vs a million dollars in funding for drug research or manufacturing. This increases probability of ROI and permits aggressive investment. Operational leverage: Scaling code is cheap as well. It is free to copy. Solving one problem with software well often enables solving immediately adjacent problems very cheaply. Do LLMs decrease or increase the leverage here? Writing code is cheaper, a single engineer can now do much more. Does that endanger engineers? Yes, if their job is "take requirements and implement to spec". No, if their job is "solve important business problems at scale". The former are already typically not valued or paid exceptionally highly. The latter are likely to be valued and paid even more than they already are. Or put another way, if software engineers are going to be hurt by LLMs who is going to benefit? This is assuming a zero sum game which I would disagree with here. But if not software engineers than who is better positioned to wield LLMs effectively?
- Workaccount2 1y agoWhat is being missed here, and the actual blindside of LLMs, is that software devs will not be the sole gatekeepers of computer utilization in the future. I cannot overstate this enough. It is the main thing to watch for. Even if LLM progress halts today, there will be 5-10 years of fundamental changes in how end users interact with computers.
- dboreham 1y agoMeanwhile my phone still can't autocorrect my typing and my email provider still can't identify spam.
- jajko 1y agoIts cheap to write some code, but still big software projects cost massive amounts of cash, take forever and are often a failure. There are visible bugs or at least big missteps in design in literally all software I use - Windows OS, Office, browsers and specific webs like ebanking, desktop apps. I dare say making software work well consistently is not a skill thats easy to acquire. Also "solve important business problems at scale" - thats an extremely narrow mostly SV-based view on how most software out there is built, no company I ever worked for in past 20 years across 3 countries ever needed that from me nor anybody around. I'd say a junior view but that would ruffle some feathers. Seniors talk about team and client and budget communication, processes, delivery pipelines, support etc. Lets put it this way - real world is a tad more complex than your simplification make it look like.
- cardanome 1y ago> What I see is a future where AI handles the grunt work, freeing us up to focus on the truly human part of creation: the next step, the novel idea, the new invention. If we don’t have to spend five years of our early careers doing repetitive tasks, that isn’t a threat, it’s a massive opportunity. It’s an acceleration of our potential. Yeah, no that is always promised but historically this has never been true. On the contrary. Every technical revolution ever has brought great short term suffering to the majority and in the long term served to alienate people from their work. It has been creative people, translator, writers, editor, artists, musicians who most fear to lose their jobs due to generative AI. What is more fulfilling? Creating had crafted items or just being a cog in the assembly line? Writing your own code or micromanaging an AI? Doesn't mean that progress is inherently bad but that it is a political question. Will the productivity gains allow us to work less and enjoy life more or will they make rich people more rich? Currently rich people are winning but the wind can change.
- cherryteastain 1y agoIf we followed this logic every time we got a labour saving innovation, we'd be still living in the stone ages. Using a bow and arrow to kill an antelope from afar is more efficient, but nothing gives the artisanal flavour of meat developed by hours of persistence hunting.
- cardanome 1y agoYeah that is why I wrote: > Doesn't mean that progress is inherently bad Progress is inevitable. And while it leads to short term suffering it does also lead to higher standards of living or at least it can. Still, the claim that tech would safe us from the "mundane" tasks and would allow us to focus more and more on creative and fun work is often claimed but never fulfilled. Especially we software devs seem to be complete suckers for that kind of thinking always searching for that silver bullet, the new hot framework, the new language, the new way to deploy servers, the complete rewrite that will make everything better. No, it wont.
- kiba 1y ago
- alcorr 1y ago[dead]
- lordnacho 1y agoCoding was always a temporary profession. Back 200 years ago, most people were illiterate. If you could read and write, there was work. You could become part of the machinery of the beginning industrial revolution, actually quite an important cog. Just by knowing how to read and write, someone would need your skills to coordinate stuff, mostly mundane. But it meant you had a way into a business. You might convert your clerkship into accountancy or law, or you would become a manager, knowledgeable about whatever business you were working in. As time passed, everyone became literate. Knowing how to read and write stopped being the only thing you needed to get on the career ladder. When I started working, my boss had no degree. He had energy, and he could do arithmetic. This got him a job as a young man running around with slips of paper in the LIFFE pit. Eventually he learned how option trading worked. He got older and hired me. By this time, you could easily find a highly numerate graduate, and only such people were considered for finance roles. It was enough to have an Oxbridge degree and just sort of be smart enough to figure out coding on the job. Now, when I look at the new grads, they blow me away. They can already code quite well. They already have internships in the business. They already have an idea of what alpha is, and how to find it. They are well on their way to just being quantitative trading professionals. We are in an interim period similar to the expansion of literacy. The school system has not ramped up computer literacy in the way it successfully got most kids to be able to read and write. Until there are lots of people able to code, there will be lots of programming jobs. That is, jobs where the person is in the seat because they can code. Much as in 1825, there were clerking jobs for guys who could read and write. Or so we thought. Now there is a tool that allows the business side to make code. It's not even that terrible code in my opinion, and it will only get better. It's here, and if you know what the business needs, you can use it to further the business goals. The great divide that will open up is that developers who got into business because they could code are now in a bit of a wonderland. They not only know what code is needed, they can implement it without their friends who are further down the chain. People who are just finishing a course in how to code, well, they face a bit of a struggle. On one hand, it's an important skill. On the other hand, for that skill to pay, you need to jump the gap that was once a stable existence. It might not be its own skill any longer, you might need the domain knowledge on a whole higher level.
- sota_pop 1y ago
- freedomben 1y ago> Look closely at every major breakthrough, even those in AI-driven medicine. It’s still humans pointing the AI down the right paths. Human creativity is the spark. In the short term yes, but we're already seeing nearly autonomous agents get impressive results. It won't be very long until the average person can be that guiding hand, rather than a software engineer who knows how to code by hand and design software. This is good for the world, terrible for the software dev
- d3ckard 1y agoI call bullshit. This is like saying an average person can be the driving hand for legal documents or medical diagnosis. The whole point is that as a specialist you vouch for what has been created. Yes, your time moves away from writing code to reviewing it, but it still requires competence to figure out whether what code is doing is exactly what is supposed to be doing.
- tranchebald 1y agoSoftware is a bit unique in that the vouching process is really worth nothing at all. A licensed structural engineer, attorney, or doctor has professional liability for acts of negligence and malfeasance. The last time I checked, most commercial software is expected to have large numbers of defects. There are some costly products I can think of that are barely fit for purpose, and yet somehow the bad actors responsible for them aren’t sued out of existence or prohibited by law from practice. I think if the industry trend is toward paying developers to verify or certify programs are logically sound and fit for purpose, then users will be getting a lot more value for the cost of developers’ time.
- ozgrakkurt 1y agoReliability is worth everything. You never ever want to do work with unreliable people. If someone is convincingly lying without any incentive, you have to check every single thing they do and this is even more difficult than doing the work yourself.
- 1y ago
- starchild3001 1y agoExcellent blog post and thinking. We all need to create that personal and project context document(s) to benefit maximally from AI.
- coolThingsFirst 1y agoStay away from CS. There are barely any jobs left and it will get even worse. It's not only AI, it's rampant ageism as well where you are old late 20s for this field. It's a hype driven, youth obsessed career.
- geofffox 1y agoI am a meteorologist and I know a little about how programming works. I'm going to be 75 this month. My last computer class was the '67-'68 semester of high school. That being said, AI and I have written some amazing programs to produce beautiful graphics I use on-the-air. And it's all in Python, a language I can read and not write. If I can do this you should be scared.