I completed a full-stack bootcamp around 2022 or 2023 and was hired soon afterward by a small local company. It has been a great place to grow: I work with supportive people, get broad experience, and several colleagues also came through nontraditional paths. Before that, I was a professional orchestra musician, but I changed careers because I did not want to spend another decade struggling to find stable, well-paid work.
I have been doing well and already use AI coding assistants regularly. However, my supervisor is now running agents that can create features for unusual requests, essentially doing much of the work I do, even if the results take longer and still need oversight. That has made me worry that my career could become obsolete just as I am getting established.
I am anxious enough that it is affecting me despite taking medication for anxiety. I am not necessarily asking anyone to solve my life, but I would appreciate practical advice. Should I deepen my current skills, focus on AI, learn infrastructure or another specialty, pursue more education, or consider starting over again? I am also struggling emotionally with the idea that the time and money I invested in learning to code could become worthless, especially if the future only offers work as an 'enter-pusher' or prompt writer.
4 Answers
It is worth strengthening the parts of development that require a broader view: backend systems, databases, deployment, cloud architecture, security, authentication, monitoring, and reliability. AI can help with all of those areas, but generated suggestions still need to be checked against real constraints and production risks.
At the same time, do not assume that learning infrastructure makes you completely safe from automation. Every technical specialty will change. The goal is not to find a magically protected niche; it is to become adaptable, understand systems deeply enough to spot bad output, and keep learning without getting trapped in online doom discussions.
The job market is genuinely rough, especially for people without a traditional computer science degree, so your anxiety is not entirely imaginary. But you already have several things working in your favor: real professional experience, a successful career change, exposure to different kinds of work, and practical experience using AI.
A supervisor's agent that can make a mostly functional feature is not the same as an autonomous engineer who can safely maintain a business-critical product. Production systems involve unclear requirements, legacy behavior, security, testing, incidents, and accountability. Those problems still need people.
Most importantly, the repeated thought that you want to 'lay down and die' deserves serious attention. If that reflects more than dark humor or becomes an immediate risk, contact a trusted person, your clinician, or emergency/crisis support right away. Career planning can wait; your safety cannot. For the career question, you do not need to start over today. Keep your job if possible, use AI deliberately, build a portfolio of meaningful work, and choose one area to deepen rather than throwing away everything you have learned.
I have already changed careers once, so I sometimes forget that adaptability is itself evidence that I can handle change. I still find the uncertainty frightening, but the reminder that production responsibility is different from generating a demo helps.
Do not try to compete with AI by becoming a faster version of a machine. Learn to use it, then build strengths around product judgment, communication, debugging, architecture, and ownership. Ask to join customer conversations, clarify requirements, and help decide which features are actually worth building. Technical knowledge combined with an understanding of users and business trade-offs is much harder to replace than implementing a narrowly defined ticket.
You should also use AI in your own work if your company permits it. Let it handle repetitive tasks, documentation, test scaffolding, code review, and investigation, while you verify everything carefully. Being the person who can direct and evaluate these tools is more valuable than refusing to touch them.
That is where I have been trying to move too. I still write plenty of code, but I spend more time reviewing designs, checking assumptions, and thinking about what the system should do.
Your bootcamp experience is not wasted. AI can produce code, but someone still has to understand the problem, decide what should be built, review the output, test it, and take responsibility when it fails. Try to move from focusing only on individual lines of code toward understanding the larger product and system—the 'forest,' not just the trees.
Your background as a musician may help more than you realize. Pattern recognition, practice, listening carefully, and making decisions under constraints all transfer well to software work. You have already shown that you can successfully reinvent yourself.
The larger-system perspective is a useful way to think about it. The job is increasingly less about typing every line and more about making good decisions with the tools available.
AI is getting surprisingly useful for infrastructure too, so I would not treat DevOps as an untouchable refuge. It is still valuable to understand those systems, but the durable skill is being able to reason across the whole system and verify what the tools do.