A blocker exists here. I've personally talked to VPs and managers that are simply behind and refuse to acknowledge this is true. If you're applying to work and state this in an interview, they will immediately decide they need someone else, someone who can code better than AI every damn day. You cannot talk your way into a job after you say this and the decision-maker disagrees. Some things simply cannot be helped.
/goal exists for encouragement loops. If someone just needs an encouragement loop they are not hiring right now. The job is much more than coding and always has been much more than that.
But I'm very senior and so I haven't been predominantly a coder for a long time now. I keep things on the rails and headed the right direction, grease the rails, cajole teammates and stakeholders, etc.
examples: Managing your calendar, responding to emails from your students (with human in the loop review), sending invoices, following up on unpaid invoices, writing/updating your website, creating/managing your yelp/google business accounts, emailing past students for referrals, etc etc.
All of these things are very interesting from an "AI Orchestration, AI Software Factory, MCP to integrate several source systems, etc" perspective that can make your 2 years of unemployment really shine.
And the good news - you don't have to lie and say "I was building with AI the whole time", you can say "I made a career change to math tutoring for X reason, learned everything needed to run the business manually, then I recently started automating all of it like a Forward Deployed Engineer would do, and here's where I ended up so far".
You're narrowly defining coding as "writing lines of a programming language by hand." But coding, or programming as it is better called, is about creating software. It is about creating a program. A task for a computer to do. And whether it is done using English, Fortran, or assembly it is absolutely still a job.
So while you're right to point out that C# is not as valuable a skillset as it was before and people are concentrating more on higher level business and architecture requirements, the end of your post is outrage bait.
But even this is short-lived, and the writing has been on the wall for years. Hopefully you invested hard in companies that will grow as AI diffuses into the economy so your assets can throw off more income than you earned in the gravy train years of SWE. If not your livelihood is going to drop, even starting a business is unlikely to succeed as everyone else has AI to help them so you coding skills give limited advantage there.
This is represented by code too though. Or at least some form of written documentation.
Sure, you won't use anything lower level than typescript for it normally, but for complex relations and constraints, code built on your own abstractions (and with types) is still easier to reason about and make robust than some non-technical person vibecoding in English without any good workflows or collection of skills (that they actually know how to use).
Agreed, "coding" is not a job. But software engineering 100% is, design 100% is, and devops 100% is.
> check out the /wayfinder skill from Matt
How is the OP supposed to know what this means? Seems like borderline psychosis to think this is just known. Personal experience has been people who use these tools are kinda low skill, too.
Looks interesting.
Where is this mythical AI? I have not found it yet. I'm not doing C# with AI, but whenever I make AI code something (and yes this is with frontier models), both the quality and the quantity are visibly and significantly worse than a human engineer's. The code is frequently brittle and abstraction-breaking, and the tests are simply garbage. And I know this isn't specific to me because I also see this - consistently - with what other engineers send me to review too.
I would more readily buy "code quality doesn't matter now that we have AI" than "AI codes better than you."
Michelangelo's David took years to complete, many studies and iterations. The patrons that paid for it wanted the perfection such an artist could provide - that was not something to be rushed.
Software that is ergonomic, intuitive, fast, and maintainable takes time. To use the analogy - chipping away at granite is a slow and tedious process, mistakes in planning or approach are difficult if not impossible to recover from.
Taking time to do it right sometimes is the only way to achieve quality.
The problem is that, in the real world, people are neither competing for maximizing the code quality score, nor are they spending remotely the same amount of time with vs. without AI. They're spending a small fraction of the time with AI than they otherwise would have, and their goal is to ship the product. Hence why they commit bad code.
To put it bluntly, I've literally seen engineers who used to send excellent pre-AI code suddenly start sending trash for review when they use AI. And, when I push back and point out the problems and they actually put in the effort to improve it, their code quality improves to (or beyond) what they (or I, for that matter) would've written without AI. I don't know how you could get a more fair experiment than this.
So, to answer your question directly, no. (No for other reasons too, but this is the only relevant one.)
I simply don't believe you.
For personal projects where I have a deep understanding of what I want to build and genuinely care about the quality, even Fable can't touch me. Of course, AI would get a working system done 50x faster, but personal projects aren't about speed for me.
You don't care at all about (c) maintainability or fragility?
One of the biggest problems I see is LLMs duplicate sources of truth they have no business duplicating... all the time. E.g. if an internal constant in some code is X then they just hard-code X in fifty other places far away and code based on that. And it's not just constants, they often duplicate entire pieces of logic too. So everything is fine and dandy when the code is fresh, but the next time the original is updated, the rest of the code breaks, because nothing forces this update to update too. Of course the garbage tests they produce never test such hidden assumptions either.
And this is before I get to other things, like (d) test costs and (e) the limits of test matrices. That "inline assembly" you just inserted now requires you to test everything on older CPUs that may lack newer instructions. And on other architectures too. That's a huge cost and this kind of thing exponentially grows your test matrix. Or, more likely, you end up with a breakage on some CPU because you didn't care.
If you have unlimited tokens i guess this is pretty much true these days. I've noticed opus write write and remove the same piece of code in a session. They prefer to write a lot, a lot of defensive checks in python etc.
At my company I have around 4000 GitHub copilot credits per month. I cannot afford to just let the LLM finish a whole project by itself using just spec documents. I did that once, ran out of tokens and then found out i couldn't understand what was going on.
This will probably change in the future but right now I need to work with what's available to me
I'll be blunt: Claude Code using Fable High. But, it's not the only one, you can't hardly swing a stick without hitting an AI that is great at coding. If by coding you mean "produces working software". If your definition is "produces code that doesn't offend my sensibilities", then that's a different matter, and also likely something that a human expert developer likely couldn't accomplish either. ;-)
Or are you saying that the "mythical AI" is mythical because people are using it without putting in any effort, therefore producing poor results? If that's the core of your argument, it sounds like the mythical AI could be out there and you'd not know it because those around you are, to coin a phrase, using it wrong.
I'm kind of struck though that your experience seems to all be second hand (people are using AI and submitting bad code); do you not have any first-hand experience with using claude code and fable?
I'm saying that most code I see AI generate is frequently bad, in ways that nobody disputes, not even the engineers who sent me the code to review - they themselves previously always avoided those exact problems when they used to write the code by hand.
> Or are you saying that the "mythical AI" is mythical because people are using it without putting in any effort, therefore producing poor results?
This also happens.
> If that's the core of your argument, it sounds like the mythical AI could be out there and you'd not know it because those around you are, to coin a phrase, using it wrong.
If you hired a brilliant math PhD who always wrote bad code and you had to keep reviewing every single thing they did and getting them to rewrite their code until it met the quality bar every time, and they never learned from their mistakes from one project to the next so this was a persistent issue, but they were so fast that even micromanaging them let you achieve a better outcome faster than you would have alone, what would you call that? That's what AI feels like.
> do you not have any first-hand experience with using claude code and fable?
I certainly do. But for anything meaty I frequently end up rejecting most of the code they produce before they get to other reviewers, and even then, I frequently have to do more work on them by hand. In some cases I've quite literally had to restart a project half a dozen times from scratch - with different approaches each time - in order to reach results that I'm not disgusted with.
Note that I'm not claiming to be an expert in using AI by any stretch - I'm still very much learning - but that I'm not really seeing these mythical results from others either.
And shrinking the context bloat while maintaining intent and debugability is also something you'll have to get better at.
Even the experience of using a Terra-type model vs using Opus requires a different workflow because one can just go on longer and make reasonable decisions most of the time.
Kind of like driving a car doesn't require you to know how to do basic fixes on the road anymore.
Hahaha I spent hours yesterday attempting to build a solid multi tenant api with Claude code in .net. I refined it for a couple of hours, came up with a plan (wrote it to markdown files), used Opus and Sonnet to write it and used code review. It was a disaster. Loads of code but loads of terrible decisions, bugs and suboptimal data design.
14 day session expiry, active org ID in the cookie, single tables with nullable keys instead of splitting it up...I can't recall the other issues and bugs as every review for about 4 reviews in a row threw up 1-3 problems (and I don't have my laptop to view the git log)
It often just straight up ignored any hard parts of the plan.
The tests were brittle and slow despite running the tests for every change it didnt stop and fix it. When challenged it was sassy like "I think 15s isn't too bad"
Something 'super intelligent' trained on billions of lines of code should not need every single aspect of every single module explained. A secure Auth and multi tenant system is hardly novel
It basically generates so much code it hopes you won't notice all the issues bugs and footguns. Just like bullshitters like who don't shut up hoping you can't keep track of their bs
Again, it'll happily produce lots of code quickly to pacify people who want to stick their head in the sand and pretend lots of code which looks like it ticks some boxes must be correct. It seems to excel at that (I've been using Claude for various other small projects in different languages btw, this isn't my only experience with it)
"Fast, cheap, good - pick two" seems still to hold
This is all obviously false. Thinking that "coding is not a job anymore" is as delusional as being anti-AI.
But I guess this is what the industry wants to hear: sycophancy towards AI and hatred towards human programmers.
The best coder in the company I work for just said "I haven't opened an IDE in a couple months". He was a die-hard JetBrains guy, now he's talking about letting his subscription expire. I'm in SRE, and so I'm not a day-to-day coder, but I've been coding for 40+ years and it's really obvious in SRE.
I can imagine some corner cases where coding is still a job, but for the general case I think there's a good case to be made today, and can absolutely see we are on a trajectory where it's only getting more true.
If anything, coding may be something we do to FURTHER our job.