[crazygringo]

My point wasn't that the bugs don't exist anymore. Obviously they still do.

My point is that I can frequently figure out how to work around them in 5 minutes rather than 2 days, because someone else already did that work. I can find out that a different function call is the answer, or a weird flag that doesn't do what the documentation says, or whatever it is.

And my problem of it taking two days to debug something is eliminated, usually.

[lisbbb]

I don't know that it's that much easier today. I ran into lots of odd issues with Next.js and authentication and there wasn't a whole heck of a lot of useful info out there about it. Github does help, but you have to wait for the devs to reply.

There are tons of obfuscated Java jar libraries out there that are not upgradeable that companies have built mission critical systems around only to find out they can't easily move to JVM 17 or 25 or whatever and they don't like hearing that.

[johnnyanmac]

>My point is that I can frequently figure out how to work around them in 5 minutes rather than 2 days

Guess I'm just dumb then. I'm still taking days to work around some esoteric, underdocumented API issues in my day-to-day work.

[crazygringo]

Guess you missed my use of the words "frequently" and "usually", which I intentionally used instead of "always".

[johnnyanmac]

I guess I should have used "frequently" and "usually" when describing that I constantly run into problems relating to API's that cause mini-rabbit holes.

The thing is these API's are probably just as massive as old school OS cosebases, so I'm always tripping into new landmines. I can be doing high level gameplay stuff one week. Then the next week I need to figure out how authoring assets works, and then the next week I'm performing physics queries to manage character state. All in the same API that must span 10s of millions of lines of code at this point.