Fix. Or. Repair. Daily.
fuzzzerd
Such useful features. They should be built-in. But I'm glad they're serviced separately so we get updates outside windows update cadence.
It's a balance, but too many people don't even flag it to management because they're lazy and they write shit and ship it to get it off their own plate.
Now, if management says ship it anyway it's a balance of you as a developer making sure they understand they're throwing this technical debt on the credit card and it may (probably) need to be paid off later. If you fail to articulate the interest that'll be due later then you didn't do enough or management is bad.
You shouldt work unpaid to fix it, but sometimes you should just do it right even if it takes longer because it's how it should be done.
I have done it as my main job and I echo your sentiment. It's inevitable that sometimes you have to meet a deadline or get something more important working first, but if you write bad code because you are lazy or unwilling to read the docs to do it right, shame shame shame.
It's a never ending onslaught of beginner questions and experienced folks with domain knowledge burn out. I'm sure it's good when it's new and fresh and everyone is exited to participate, but that wears out. It's why things went away from mailing lists, or why mailing lists started getting archived, so they could be searched.
I guess with most things it comes in cycles, and we're at the on demand answers cycle right now.
Ephemeral discord servers are awful because they don't scale and they can only ever help the lowest common denominator of questions/issues. We need something else, but it has yet to present itself as a solution.
It's even weirder seeing it in person, because it has a similar effect yet you know you are seeing it for real. That's just how it looks.
Think of how stupid the average person is, and realize half of them are stupider than that.
George Carlin said it, but this is a great example of it in practice.
This looks really good. Thanks, I had no idea it was out there.
Regarding obsolete models, that's only partially true. There's loads of content that are effectively "finished" and won't be changing, and will grow obsolete at a fairly slow pace. Meaning they'll be useful in the models once trained for years.
Obviously new technology and similar ideas/content that didn't exist when the model was created won't be there, but the amount that changes and or is new is relatively small each year compared to all the historical content.
Vintage is 25+ years, antique is 100. That's the guidance of physical items typically. Seems to fit here as well, IMO.