@user400654 Code should be descriptive and self-documenting.
@Tinkeringbell I write 90% of my code in Programmer's Notepad. If I need a debugger, I use and like Visual Studio on Windows. I also use WinDbg when necessary.
A lot of the code I write these days is cross-compiled (meaning, I write on Windows, but target embedded ARMs or something like that), so a Windows debugger doesn't do me a whole lot of good.
(In Jewish canon, he's just another emissary of God doing his assigned job of essentially being a prosecutor in a trial. Not evil, that's just his function.)
"Satan" is only mentioned once in the Jewish Bible, and that's in Job, where God assigns him to test Job with hordes of misfortune (you know, like killing everyone he loves). In the Talmud and Rabbinic tradition, he's the prosecutor - the assigned agent who presses charges against humanity.
The snake is also only mentioned once, and that's in the creation story. There's no connection to Satan AFAIK in any of the traditional sources; the snake simply was an entity that got punished for causing Eve to disobey.
@SonictheAnonymousHedgehog Yes. You. If you want to tell @πάνταῥεῖ that it's actually a site-recommendation and ask that they should reconsider their vote, that's one thing... but apologizing for their behaviour in public like they're some unruly toddler isn't okay.
As a side note - the current composition of close votes means that the last user to vote will get to choose which close reason to close the question with (out of a selection of three).
@SonictheAnonymousHedgehog Both the off-topic votes are wrong. I picked “unclear” because we cannot make site recommendations without more details about the question to be asked.
@AndrasDeak Thanks, I’d missed the context. Wow, that’s....surprising.
@DavidA Then that sounds like a good answer. Regarding whether you should upvote it, that’s solely up to you. We only have general guidelines recommending to upvote content that you think is clear, correct, and/or useful.
But obviously you cannot upvote everything that meets that standard, because you have a limited number of votes per day.
@It'sOver Imagine all the time that must save you over the course of your life! Every time you make a cup of tea, boom, a free minute added to your life.
I picked duplicate because while there aren't that many details as to what the author wants to ask about, they can check to see themselves whether they can ask it by reading the duplicate target. I felt that that would be more helpful to the author.
@SonictheAnonymousHedgehog Yeah, it’s an understandable instinct. But sometimes I worry that it gets interpreted as “you can’t ask for specific advice because one time someone already asked for general advice.
In general, though, I do tend to prefer closing as dupe when possible because that does provide some help.
@CodyGray Per policy here, questions can be closed as duplicates of of FAQs if that FAQ addresses the question entirely. I do make the additional point of editing the autocomment to point out where and how exactly it's answered (in this case, to point out that it might be acceptable on Code Review but they should read the guidance to see if it would actually be.)
@CodyGray I've seen people editing the autocomment back into the original form, but I've been telling those users to not do so since editing it will prevent it from being auto-deleted once the question is closed (for good reason).
@CodyGray I have another question: the question is currently closed as off-topic, which both you and I believe is wrong. The policy states that you should only vote to reopen with the intention of changing a close reason if the question should be closed as a duplicate but is not, and leave it otherwise. If, as you say, the question is unclear, I should leave it, right?
@SonictheAnonymousHedgehog Yes, I’m inclined to leave it. I don’t typically obsess too much over which close reason is chosen.
If I cared enough, and wasn’t on mobile, I might leave a comment explaining it was closed because not enough detail was provided, and encouraging them to [edit] to share a draft/outline of their question.
That linked answer is describing reviewing items in the reopen queue, which this is not, as far as I know.
It needn’t be there. Someone would have to vote to reopen.
I wouldn’t vote to reopen it. I already voted to close it.
@CodyGray I even had a custom "also duplicate: <link>" comment get deleted, without it being added to the question as a target. I doubt that it was manually deleted...
> Also dupe target (didn't notice the missing python tag) stackoverflow.com/questions/7487145/… – Andras Deak Jan 15 at 17:52 deleted by Community♦ Jan 15 at 17:54
Hmm, I'm on the list of mods that resigned after Shog and Robert were fired now. Not really accurate, but I really don't mind as I'd certainly have resigned on the spot if I hadn't already done that.
Right now the delay until a resignation is processed is longer than the time it takes for SE to make yet another terrible decision. So I can't really blame anyone for not getting the causality entirely correct here.
@terdon Well, in the interest of fairness, a lot of employees were off for a while during that time due to Thanksgiving Day in the U.S....it's not unusual to take several days time off during that time.
It's also a bit different (no positive/negative opinion) to see that local moderators were allowed to feature these posts here in the first place, despite a prior response (from Monica) indicating that they don't do so since they're merely local moderators and not "arbiters over what's featured network-wide".
On any other site, featuring a question on meta features it on that site (only). Moderators can and do use the "featured" tag locally to highlight things that are important to their communities.
Here on Meta, featuring a question features that question on every site on the network. We don't ha...
@SonictheAnonymousHedgehog My understanding is that they limited themselves to not featuring stuff in a sort of agreement with SEI. They decided that breaking that agreement was important enough.
I would assume that if they found it problematic enough, they would have already taken action against it. but here we are, with three still featured, for longer than the declared 2 day limit for mods. (they're employees, so i guess it's fair to think maybe the period is longer for employees vs mods?)
But has the company acknowledged anything about firing Shog and how? Until they do it's just gossip. But proactively unfeaturing his farewell post is hard evidence of "a dick move"
Shog9's departure announcement on MSE is still featured, along with Robert's and Jon's. Shog's simply isn't shown because there are only two slots for MSE posts to be featured, and it chooses the newest ones first. (Shog's is the oldest of the 3.)
There are also 2 questions featured on MSO. Those are the only two questions featured on MSO, and they consume the 2 slots.
On Stack Overflow, therefore, you see 4 featured Meta questions: two from MSE (Robert and Jon), and two from MSO.
FWIW. I decided to feature all three. While we did not normally feature things, I am a human exception handler. The staff could probably not have featured it. So I decided to do it
Even if the staff could have done it, it isn't necessary that they do it, since there are community moderators to do it.
It's the same reason that I mark stuff as [status-declined] on our Meta that I know won't get implemented. Stuff like, "make it mandatory to leave a comment when downvoting".
On any other site, featuring a question on meta features it on that site (only). Moderators can and do use the "featured" tag locally to highlight things that are important to their communities.
Here on Meta, featuring a question features that question on every site on the network. We don't ha...
