Solved Resurrecting old threads?

[Isaac]

AI won't hurt seasoned developers any more than MZ-Tools or similar utilities. You still need to understand the basics.
It's like putting two drivers in race cars, one a professional and the other a novice. The outcome will be vastly different.

I agree in the sense that I think you are literally correct , in "you still need to understand the basics".
Whether or not management of companies will comprehend and buy into that or whether they'll try to force vibe coding as they drool with excitement at the thought of the money they'd save from a layoff
But in the end, the truth must be vindicated by people's experience, as solely vibe coding for production assets will have enough catastrophic consequences that finally the Security department will say "Enough - you must have real programmers on staff to be safe"

 

[Isaac]

If this big experiment goes sideways, then they will hire humans as needed to fix the problems.

It will only take some data breaches/hacks to open their eyes that a PM armed with vibe coding tools is not enough.

 

[The_Doc_Man]

The reason we don't lock old threads is because sometimes the problem comes up again and a new round of developers need to ask questions. Some of us have been around long enough to maybe remember a little about the answer.

 

[amorosik]

From my point of view, there's no reason to set a time limit for responses
In fact, there's a specific reason to allow responses even much later, and that's the fact that, being a technical forum, keeping the initial question and all the answers within the same 3d is certainly useful for maintaining order and facilitating the search for information on a specific problem.

 

[Isaac]

The reason we don't lock old threads is because sometimes the problem comes up again and a new round of developers need to ask questions. Some of us have been around long enough to maybe remember a little about the answer.

I agree and something valuable can ALWAYS be added to ANY conversation. That's also (one of the many) good reason not to have a 'solved' tag, IMHO. I loved the UA threads that would go on and on with stuff not directly related to the original question, I learned the most from this

 

[Gasman]

I agree and something valuable can ALWAYS be added to ANY conversation. That's also (one of the many) good reason not to have a 'solved' tag, IMHO. I loved the UA threads that would go on and on with stuff not directly related to the original question, I learned the most from this

Yes, hard to find the wood amongst the trees.
Also Solved allows you to pinpoint that thread and see how it was solved?

 

[Gasman]

The reason we don't lock old threads is because sometimes the problem comes up again and a new round of developers need to ask questions. Some of us have been around long enough to maybe remember a little about the answer.

A link to the original thread, does not go amiss?

 

[dalski]

Is resurrecting old threads a bad thing? Especially if the poster has intelligently found a follow-up question to the exact subject matter at hand?

I agree, I'm surprised that the consensus is to post a new thread, on the same subject; leading to superfluity & detriment to Search Engine Results Page (SERP) for users. Millions of results for the same topic, opposed to a single answer with high-calibre solutions.

 

[The_Doc_Man]

A link to the original thread, does not go amiss?

I agree 100%, but too many new members just tack on a response to a less-current thread because they don't know our ways yet. Not to mention that "newbies" are less than fully familiar with our "Search" function and "Related Topics" lists. They post in the older forum because they might not have yet figured out how to post a link within the forum - besides which I think the "link posting threshold" doesn't differentiate between external and internal links, so newbies CAN'T post that link.

 

[Vassago]

Answers also change over time as technology changes. The correct answer 20 years ago may not be the most efficient way to accomplish the task today.