I know local dev is hard in a complex system, but if tooling prevents you from working for an entire day something is seriously wrong.

I spent a few days fixing a build system to make it easier to fix in the future. This saved me weeks so far. Not sure what kind of control you have over that.

Spend 2 days automating it or spend weeks of your life doing it manually

Automate everything

Seemingly most devs today: "Hey, I can't work today, my IDE is messed up, not doing what it's supposed to, and my workspace is corrupt!"

Older lead devs: "Well, how about you just drop to a command prompt, re-clone the repo, and work in Notepad or some other basic text editor for the day?"

Seemingly most devs today: "What?! You can't do that! How would you know what to type without intellisense and Copilot and all the things an IDE does for me?! That's impossible! You can't even do a simple refactor without an IDE!"

Older lead devs: "Oh my sweet summer child..."

@fzammetti say all you like, but intellisense, syntax highlight and indexed mapping help a great deal.

It's not impossible to code in vim/npp, but it takes longer and wastes your time debugging simple code snippets for typos.

I wish, but we work with massive proprietary systems that are simply too hard to replicate

@ostream the rest of us, retards in your dictionary, make them

@ostream don't. We should be trying to be better, having you as a perfect example. Not the other way around.

@netikras You'll get no argument from me. I remember when IDEs started to become a thing, I definitely had that "get outta here with that shit" mentality... but that was, I don't know, 20 years ago or so maybe? I was obviously wrong then, and my tune has changed completely. I'm definitely not one of those "just use a text editor" people... I know -I- don't just want to use a text editor... but by the same token, my point is that some people literally can barely do their jobs without an IDE and all the tooling we have today. We have all these tools for a reason - and they for sure are valuable and definitely should be used - but if you are DEPENDENT on them, that's where I have a problem, and I've seen that A LOT, unfortunately..

@fzammetti I had IDE in DOS. Macs prob even longer.

@ostream indeed

@Demolishun Oh sure, they existed since, what, Dartmouth BASIC I think, in the 60's maybe? But usage of them before maybe the early 90's was, generally speaking, the exception, not the rule... and FOR SURE they were nowhere near the level of aid and automation they are now, which is really the point that matters. Before maybe the mid-90's or so, roughly, they were little more than glorified text editors with a little bit of added knowledge of said text, and project organizers.

@fzammetti has a point though.

IntelliSense and other things make things easier.

But one should understand and be able to live without them.

Kinda like the "it's nice to have a GPS navigation system, but don't follow it's commands without thinking - cause you might end up in a lake".

What pisses me off greatly is when devs don't even bother looking for a workaround, instead just go to crying mode and whine how they cannot work at all coz the mean system doesn't work.

... With sometimes really trivial issues like SSH host key changed and they couldn't follow the manual printed out in the app.

Instead they wasted 4 hours of time by crying, more crying, making an ticket in IT, more crying, more bitching, IT solves the problem by following the manual printed out in the app in 10 seconds.

Complex system set up is hard, yes.

Especially when multiple services are woven together like an Alexandrian knot, so I can definitely feel the rant.

But I also understand what @fzammeti said cause sometimes I wonder how some people managed to live after their parents threw them out, cause their ability to solve problems on their own is non existent.