Due to a huge amount of feedback received on Meta Stack Overflow regarding the deletion of massively-upvoted but off-topic/not-constructive questions, questions locked for historical reasons have taken on new behavior that could be beneficial for Programmers (emphasis mine):
Last but not least, we’re experimenting with ways to keep some of the more useful – or even just fun – questions from the site’s history accessible in some way. To be clear: most of these are not great examples of questions that should be asked today… But some of them are, quite frankly, brilliant – and losing them entirely just because they aren’t a good fit for our strict Q&A format is wrong. For now, we’ve provided a “Historical Artifact” lock that completely freezes a question and its answers, preventing all further editing, voting, answering, and flagging. It will also remove it from the usual lists of questions on the site while allowing it to remain fully accessible and visible to everyone with a link to it.
This, to me, obviates at least in part previous guidance that locks should not be a substitute for closure and eventual deletion even on the whale questions.
Since these questions are unlikely to be deleted any time soon, I'd like to propose locking for historical reasons the site's most popular closed questions—and thus removing them from the site's top questions list and helping to mitigate some user confusion—that have 100 score or more.
This would be the following questions:
- I'm graduating with a Computer Science degree but I don't feel like I know how to program
- What is the single most effective thing you did to improve your programming skills?
- Is 4-5 years the “Midlife Crisis” for a programming career?
- Why don't all companies buy developers the best hardware?
- Perks for new programmers
- What should every programmer know?
- Will high reputation in Stack Overflow help to get a good job?
- Are there any famous one-man-army programmers?
- Windows Azure vs Amazon EC2 vs Google App Engine
- My boss wants a narrated line-by-line English explanation of our code
- Should developers accept overtime/weekend work/denied bonus payments?
- Are 9 to 5 programmers looked down upon?
- How to become a "faster" programmer?
- Is it "normal" for people to not work?
- What kind of innovative non-cash financial benefits do I offer to my developers to retain them along with a competitive salary?
- I still can't figure out how to program?
- Stuff every programmer needs while working
- Why are zero-based arrays the norm?
- Make a big deal out of == true?
- How do programmers in the West see programmers in the East?
- What's the most absurd myth about programming issues?
Doing so should substantially clean up one of the major broken windows on the site: the highest voted questions list.