Anybody remember when we actually spent time writing code instead of debugging the tools? Specially the gazillion of crap that's out there for fucking Java shit?

Companies have capitulated entirely and worship at the altar of devops and CI. I get about 20% of the work done that I was able to do a few years ago. The acolytes would say that that time has been replaced with tasks more valuable to the goal of "faster delivery" or "higher quality" all the while ignoring that neither is "better" than it used to be. The acolytes are full of shit.

@monkeyboy Very true. Everyone used to complain C++ took a long time to compile. This motherfucking Java project is less than 10,000 lines (counting empty lines) and takes about 12 minutes to compile on my Surface Book. For comparison, compiling Unreal Engine 3 takes about 3 minutes on this machine.

Welcome to hell. I recall working much slower hardware and getting things done faster.
Now the only thing that doesn't bug me is dot net core, still smooth and getting better when debugging, a year it was painfully slow and buggy.

10 years ago only spend time configuring ur machine and then just focus on coding. but now, install this, handle conflicts, clear cache because things getting crazy like an error on an empty line....etc.

Although I hated them back then, but I miss eclipse and Dreamweaver days...

I rarely spend time debugging the tools.

Once every few months there are some more serious 3:rd party libraries out of sync but the rest is writing and debugging our own code.

Not that that cannot get tedious sometimes ;) but out own legacy code is the major time thief.

And at least in C# compiling around 1/2 million lines takes maybe 1-2 min.

A recompile of a single project can take as little as 10-15 seconds.

I clearly remember Turbo Pascal 5.5 would compile a commercial scale application from floppy disks in about 2 minutes. And by commercial I mean something like 70,000 lines of code

@Voxera You are lucky. Try working on a Java project with maven

@FuckJava 10k lines in 12 minutes??? Wtf?? 400k lines back from 2009 compiles in less than 2min for me. There must be smth wrong with your build config. Or you have long-running tests.

Fun fact, I only got to debug that very same product's libs. Other products, ones with newest lib versions, give me no such trouble. Libs just work

@FuckJava like stated before you have something fucked with your build config.

@vlatkozelka Actually, he did ask a very general open ended question first. Then he specifically mentioned Java. I addressed his general point, but not his specific Java rant. Admittedly, I did expand upon his rant by referring to how all of software development is being done (and not just tools).

@vlatkozelka Are you the person who used "Chrome" instead of browser in his other comment? FYI, this is a desktop Java application, and not an Android app. If you are that person who uses "Chrome" instead of browser, stop presuming things. If you are not, my mistake, but still, do not "presume" things.

@vlatkozelka LoL good for you