Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@SortOfTested yeah 30+ poms. Maven parallel helped build faster though unit tests didn't work. Looks like no one touched it for 3 years while adding projects. We have the hw but no intent
-
@SortOfTested Monolithic legacy stacks can just get more and more junk added to them unfortunately - to fully compile the "worst" of our legacy Java stacks it's about 5 minutes on my desktop machine, which is no precision but no slouch either. I suspect on a "normal" laptop it'd be more like half an hour.
-
@AlmondSauce
Yep, I'm familiar. I was on the team writing the account and accrual program for USC in 2006, that was a fucking beast. I just like to block out the SE6 days. -
@SortOfTested Heh, I don't blame you in that case 😂
-
@Root I second this, sounds like they like the long compilation to avoid working.
-
@magicMirror multiple jars
-
@spongessuck @Root who could blame them for not wanting to work on this codebase though
Our best dev/arch just quit.
C dev lead & a dev staying late chatting.
Lead: am building, takes long
Dev: unit testing, time taking
Ask them y they r building on their latitudes when we got them linux precision with xeons/64gb workstation 1 each ?
Both: I code on latitude.
Build/test times. (pure Java/maven)
Latitudes=an hr or more
Precision=2m to 11m
Jenkins Infra we have =10 mins with test & push. Parallel builds support.
Am suposed to help with an open mind. They now want Mac pro
rant