<span style="color:#323232;">volatile int blackhole;
</span><span style="color:#323232;">blackhole = 1;
</span><span style="color:#323232;">const int X = blackhole;
</span><span style="color:#323232;">const int Y = blackhole;
</span>
Compiler is forbidden to assume that X == 1 would be true. It’s also forbidden to assume that X == Y. const just means the address and/or the data at the address is read only. const volatile int* const hwreg; -> “read only volatile value at read only address hwreg”. Compiler can assume the hwreg address won’t magically change, but can’t assume the value read from that address won’t.
Please, no, I get flashbacks from my 6-month journey (still ongoing…) of the code review process I caused/did. Keeping PR scope contained and small is hard.
From this experience, I wish GitLab had a “Draft of Draft” to tell the reviewer what the quality of the pushed code is at: “NAK”, “It maybe compiles”, “The logic is broken” and “Missing 50% of the code”, “This should be split into N PRs”. This would allow openly co-develop, discuss, and steer the design, before moving to nitpicking on the naming, formatting, and/or documentation details of the code, which is likely to drastically change. Drafts do work for this, but the discussions can get uncomfortably long and convolute the actual finishing of the review process.
Once both reviewer(s) and the author agree on the code design, the “DraftDraft” could be collapsed into a link in an normal Draft to be mocked next. The scope of such draft would be limited by the earlier “DraftDraft”.
There are some cases involving plausible deniability where game theory tells you should beat the person until dead even if they give up their keys, since there might be more.
I mean, I’d definitely do it to SBF if his crap wasn’t cleaned out already. Though admittedly I’d largely keep going just because this world DESPERATELY needs fewer SBF types in it…
most people don’t know how to properly formulate questions and it shows. 90% of new questions on SO are just bottom barrel which is why the rules are so strict about quality.
Absolutely true, but it’s also more difficult to ask a good question when you don’t know anything about what you’re asking.
People who know a lot about a topic can ask very good questions about that topic.
The problem I see with most questions people post online is that they make too many assumptions that their audience will will magically understand the context of their question.
Good questions require relevant context.
Determining relevancy requires expertise.
Expertise comes from experience.
No matter how many questions you ask and answers you get you’ll never “understand” something until you do it.
Instead of asking questions like “How do I do X?” people should be asking “I’m trying to accomplish X, I’ve tried Y, but I’m encountering Z. How could I resolve this?”
I guess my rule is that you should never ask someone a question without first trying to answer it yourself.
100% agree, and the new question page on SO makes most of those points but generally people dont read it. It would be kinda nice if they integrated an LLM to double check if questions need improvement before they get submitted.
I decided to be wrong because the correct joke would be too convoluted. I’ll work on that implementation and then you can inject it at runtime via reflection.
Thanks for preparing your comment for my dependency injection! I agree that refactorability of comments is preferable over prematurely optimizing for performance.
Forever Ago I Ran A Minecraft Server And 2 Friends Joined And One Typed Everything They Said Like This and the other managed to misspell every single word with more than 2 letters in it. They misspelled the word “the!” According to Sir Capitalizes Every Single Word, its just much easier to type that way, which raised far more questions than answers…
As someone who works in IT, and specifically networking and security, the “trade subs” are honestly what I miss.most from reddit. Places like sysadmin, Cisco, Fortinet, talesfromtechsupport, etc.
I presume OP works at a decently sized company, and they have magical people like PMs and CSMs that turn customer tantrums into neat little cards that he can push down the kanban.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.