I completed a full-stack bootcamp in 2022 or 2023 after changing careers from professional orchestral music. I was fortunate to join a small company soon afterward, where I've gained broad experience and worked with a supportive team that includes several other bootcamp graduates. I've been doing well, and I already use AI tools regularly as coding assistants.
Still, I'm increasingly anxious about where the industry is headed. My supervisor is using agents that can create features for unusual problems, even if they work more slowly and still need oversight. Because of that, I worry that the skills I spent years building could become far less valuable. I'm also concerned that software development could turn into little more than supervising generated code or writing prompts.
Should I deepen my current skills, focus on infrastructure and architecture, move toward product and customer-facing work, or consider retraining again? I'd appreciate practical career advice as well as perspective on managing the fear of having to start over. This has been affecting my anxiety significantly, and when I say I feel like lying down and dying, I'm expressing how overwhelmed and hopeless this feels—not asking anyone to solve my life.
5 Answers
Your bootcamp education and experience aren’t obsolete; they become more valuable when paired with AI. The important shift is from focusing only on individual lines of code to understanding the larger system: what should be built, why it matters, how the pieces fit together, and whether the generated result is actually correct. AI can increase your output, but someone still needs to provide judgment, context, testing, and ownership.
You have already demonstrated that you can reinvent yourself: you moved from orchestral work into software, learned a new discipline, and found a job. That adaptability is a major career asset. Don’t frame the choice as either ignoring AI or becoming a prompt writer. Use it for reviews, documentation, prototypes, repetitive tasks, and investigation, while continuing to learn how the systems work and checking everything it produces. A competent developer with good AI tools can accomplish much more, but an inexperienced person still can’t reliably tell when the output is wrong.
Keep building depth in areas where generated code still needs careful human oversight: backend systems, databases, cloud architecture, security, deployment pipelines, testing, observability, and debugging. AI can often produce a plausible implementation, but production systems involve messy constraints, failures, migrations, permissions, compliance, and tradeoffs. Also, don’t treat online predictions about the industry as settled fact. Real teams adopt tools unevenly and still need people accountable for what ships.
AI is improving quickly in infrastructure too, so I wouldn’t assume any specialty is permanently protected. The safer approach is learning to use these tools effectively while developing broad technical judgment rather than betting everything on one niche.
The anxiety in your post sounds serious. Career uncertainty is real, but it’s worth discussing the worsening anxiety with your doctor or therapist rather than trying to solve it entirely through career planning. If the thoughts about dying become immediate, feel like something you might act on, or you don’t feel safe, contact local emergency services or a crisis hotline and tell someone you trust right now. You don’t have to wait until it becomes an emergency to ask for help.
Consider moving closer to product work. Talk with customers, understand their real problems, suggest useful features, and learn to translate those needs into reliable technical solutions. A developer who understands both the business and the technology is harder to replace than someone who only implements a detailed specification. Your music background may help more than you realize because pattern recognition, practice, and interpreting human intent all transfer surprisingly well.
The bigger-picture perspective is a useful way to think about it. I’ve started using AI for repetitive work while spending more time on design decisions and problems that require context.