Java spring boot developer specifically - maybe not. But I just say that because if you are specifically developing spring boot applications, then if anything supersedes it you’ll obviously be left behind those who use the new shiny better frameworks.

That being said, tons of applications use spring boot right now, so there’s plenty of room for growth, but see yourself as a backend developer who is proficient with Java and spring boot, and be open to using other tools if they’re better for the job.

As for AI, I don’t feel it will replace the role, but it will be something that will help you accelerate your development. More productive developers will be more in demand, so therefore it’s worth learning to work with AI.

As an example, there’s been a big push at my company to start using AI tools. Here are some cases where I’ve found use for it, that aren’t just writing code for me.

• those times where you run into an error you don’t fully understand and go digging through google/stack overflow for 2h trying to piece it together? I feed the relevant code snippets and error logs into our chatbot and ask what I’m doing wrong as a starting point.

• we have business analysts write up requirement docs for new features. I’m a little disorganized, so I’ll feed that into our Ai and ask it to break it down into a development strategy, then tweak it from there.

• if I’m working with a new library, I may ask a basic “how do you do x in y” then go from there. Not a whole “write this for me” but just a basic case to get a feel for how it works

• if I’m weighing two different approaches, I’ll think through and write down the pros and cons, then describe the feature, give the two different approaches and ask the Ai to give the pros and cons. I’ll go back and forth on each point mentioning why it is or isn’t relevant, add in my points, etc which helps consolidate things into one cohesive comparison

All of that is just to explain that AI won’t eliminate all of the roles, it won’t be writing entire applications (or at least if it does then there’s a risk of running into issues no one knows how to fix). What it does do, is enable a team to be way more efficient, instead of meeting with a coworker for an hour to chat about the pros and cons, you can use it to turn that into a one person conversation. Instead of digging through stack overflow posts, you can feed your specific situation in and get some ideas to try out and iterate on. But the common theme there, is that you need to understand what it’s telling you, if pros/cons apply to your case, if suggestions are relevant to your use case.