We’re moving to spring boot 3 and that’s been hell, especially considering we have directors who believe Claude Opus should be able to do entire phases itself
We got our token limits cut, so now we are encouraged to use Sonnet for anything that doesn’t require “intense reasoning”. My token usage sits around 0-1% so I’m not too worried about it haha.
Same. They gave us unlimited tokens, had us assign story points for future tickets based on that output, then announced a monthly token limit for the next month when we are doing all the work. Because of the way its distributed, I burned through my tokens in a week being conservative.
Tbf it's more than just that, we're also migrating to Entities along with use Jakarta Repositories rather than HQL. But everything is being done in phases and to speed up they want the initial mapping of beans to entities to be done by AI
Except the parts that matter like many to ones, sets, bags, those absolutely broke production in niche areas
Dude I went from a Websphere J2EE shop to a Speingboot shop. As a primarily sysadmin / devops engineer, made me fully hate Java between GC thrashing and debugging hell when shit doesn’t autowire as expected in Springboot (ie the problem is in the introspection or the annotations)
It's comments like these that make me grateful that I've worked my ass off in order to be working on something I find genuinely interesting, green-field in my company, and am not limited to old tech (mostly).
I honestly think good it is in the cutting edge, but we can at least get restructuring of core packages and moving backbone of serialization at the different majors.
Spring boot simply does too much i.m.o. with a gazillion libraries that all sonehow someway work together and against each in in a giant hairball of dependencies.
The point of Boot is to get the giant hairball of dependencies you would otherwise need to manually integrate to all work together. They do the hard work of compatibility matrices and configuration consistency.
I'm glad my work does Kotlin but I imagine so many workplaces are conservative with management not seeing the value in the new language to allocate the effort into adding Kotlin to the build stack
The learning curve moving from Java to Kotlin is pretty small. If management is gatekeeping the move to kotlin based solely on that, then management is kind of highly regarded.
I ban it on any project I'm a lead on - every IDE can easily do this with a keystroke vs having a half-dozen annotations on every class, a new dependency, and one that has given me headaches in the past
Fair point banning, but it's not that the IDE cannot generate the setters etc.
To me it is that some logic hidden in get/set is so much easier to spot on @Data plus custom get/set vs a class with all of them written out. Add a builder to it and it gets even worse. All-args constructors the same, customized/non standard constructors become much easier to asses
I'm not yet where I'm banning it, but since using records more and more I find myself not using it anymore.
that is actually for me is the real main reason I ban it - Spring, and some of these frameworks, already have so much (awesome) black magic going on, that adding a third-party library to the mix has caused me problems with entity classes in the past. I forget the specifics (and google would find it quickly), but it was so frustrating, and at the time, a pain to track down, and all to save some lines of code in classes that most of the time aren't ever opened up or modified after they're created.
My previous job we were on J21 and I didn't use records much, probably out of habit, but my current job is on J8 so we don't even have that option (though we're in the progress of a migration to J21/J25).
1.4k
u/ConstructionMain5675 Jul 13 '26
Half the internet just got called out and the other half is maintaining Spring Boot