If I'm being brutally fair to some of the garbage build times I've had in the past:
A lot of times, these are caused by me having to use 3 different versions of some library because of legacy code. Or we license some library that requires a fuck ton of dependencies that only the library uses.
But to build it all ourself would also be a complete waste of time.
I remember a big offender back in the day were those Microsoft Office file editor libraries. To upgrade would cost the company some ridiculous $20k license and offer zero additional features that we need.
And so, yeah, we keep including the old newtonsoft json because it needs it!
When visual studio finally went 64 bit, you thought the solution was bugged because it loaded so fast.
Not strictly this scenario, but I worked a job for a few years where every compilation took minutes. It was common practice to finish up a bunch of work and queue a slew of compilations before your lunch break.
Then I got a new job and worked with a bunch of tinier, discrete applications which would compile in a few seconds. I'd become so use to quick compilations only ever being the result of an error killing the job that for at least a week afterwards my blood pressure would rise whenever a compilation would finish in <10s.
74
u/mwax321 3d ago
The key to success is to have a monolith so large that it takes an hour to build and publish.
When visual studio finally went 64 bit, you thought the solution was bugged because it loaded so fast.