I saw this question and thought it was going somewhere. It was closed, and with good reason I believe, but I still think that there is a nugget of a usable question in there somewhere. Would I be justified in editing the question even if it requires almost a complete rewrite in order to get it off of a career question? I would just write my own question, but I don't want to ask a question that doesn't pertain to my situation since the FAQ says that we shouldn't ask "random" questions.
I don't see how any version of the question could be on topic for Programmers. Even a less localized version of it wouldn't really be about an issue that's unique to our profession.
The nugget of a usable question you see in there might be on topic for our sister site, The Workplace, but I'm not sure. You could ask around in their main chat room, The Water Cooler, verify whether the question could be on topic for them and get some suggestions on how to edit it or, if the question is blatantly off topic for them, point you to similar questions that might sufficiently answer the question in question.
I think you'll struggle to find a non-career question in there, but I don't want to discourage you if you see something I'm not.
There are some elements that tie in with Ambler's Generalizing Specialist, but it will be a fine line between career / "what technology next" vs. what is on-topic within the guidelines of the FAQ. There might be something in there from a methodologies point of view.
If you think that you can salvage the question through an edit and not destroy any existing answers (which doesn't apply in this case since it was closed before any answers were posted), go for it. It's called a "heroic edit" (search on Meta and you can find a few posts about them). The point of closing a question is to give people the opportunity to turn a poor question into a good question. After you edit, it might be a good idea to flag it for moderator review - if it's a good edit, we'll reopen the question.