421–430 of 441 posts
Earlier quoted context omitted.
I don’t speak hebrew but someone online said that this is an unnecessarily literal translation of "double colon" and it’s not what most developers would call it. Take that with a grain of salt though.
The history of that entire fiasco is quite comprehensivly summarized at https://phil.tech/2013/wtf-is-t-paamayim-nekudotayim/ .
Earlier quoted context omitted.
I don’t think laziness (in this comment or the ones about the bash-like C macros) is the right word. I guess there is some pressure/tiredness/newness/taste/external factors driving the choices, test count, and style guide aberrations.
Probably typing on a non english keyboard. When I learned C a long time ago, I read somewhere 'isnt it nice that one doesnt need a lot of keystrokes like for begin and end', and I thought pls give me begin and end instead of this unpleasent slow hand movement.
Earlier quoted context omitted.
Not many people know this, but similar to image alt text, the tag was originally introduced for accessibility reasons, so that people with autism and similar conditions can experience the web in the same way as more neuro-typical folks do. The tags should be invisible in the average browser, unless you've got sarcasm highlighting turned on. Unfortunately, the feature hasn't really caught on, and it remains unsupporte…
Why does this post appear in yellow?
Earlier quoted context omitted.
There wasn't a post-mortem in my case. I had thought of the case for but basically out of laziness talked myself out of writing a separate test case for it, presuming the test cases for a zero-length title and an un-closed title covered the corner cases. (The entire document was guaranteed to be converted to valid UTF-8, perhaps with invalid character substitution characters, by that late in the Content Converter pip…
I don’t think laziness (in this comment or the ones about the bash-like C macros) is the right word. I guess there is some pressure/tiredness/newness/taste/external factors driving the choices, test count, and style guide aberrations.
I think it was an issue of familiarity and comfort, not newness. The author joined Google before I did. If you're basically working with one other person, and you're rarely getting code reviews from outside your coding pair, and few other people interact with your code, it's easy to develop some bad habits and forget that your code choices have externalities. To be fair, the externalities were usually rather small.
Earlier quoted context omitted.
What does it mean that you were right to feel embarrassed? You were wrong to make the mistake, sure, but that happens. That’s what a mistake is. It’s not clear to me what shame helps in this instance. If somebody has a pattern of not meeting a quality bar with their code that’s one thing, but otherwise cutting people up for mistakes really seems like bad culture. Aren’t you supposed to practice blameless postmortems…
My recollection from my time there, as well as one of the biggest cultural differences noticeable between my and my workplaces since, is that big chunks of the company really do believe in the blameless postmortem ideal. But culture isn't a magic tool that completely neutralizes assholes, and there are assholes in _every_ organization of sufficient size, like the "[name redacted]" character in the previous post
And thus has Eliza Callahan suddenly found themselves a poet with a lot more name recognition among tech workers.
Earlier quoted context omitted.
Probably typing on a non english keyboard. When I learned C a long time ago, I read somewhere 'isnt it nice that one doesnt need a lot of keystrokes like for begin and end', and I thought pls give me begin and end instead of this unpleasent slow hand movement.
The author was born and raised in Brooklyn and went to Cornell, if I remember correctly. As far as I know, English was his only language, and he was almost certainly using either US QWERTY or Dvorak keyboard layout.
Jimmy: What do you call yourselves?
Derek: "And And And."
Jimmy: "And And fuckin' And?"
Derek : Well, Ray's thinking of putting an exclamation mark after the second "and." Says it'd look deadly on the posters.
Jimm: Psshh...
Outspan: You don't like it? You think it should go at the end?
Jimmy: I think it should go up his arse.
Outspan: Well, we're not married to it.
Earlier quoted context omitted.
> maybe a little training on why customizing a programming language with macros is bad Both the author and the reviewer had passed C++ style certification. They knew why it was bad. They just got a little lazy and wanted to write their code in a way that felt familiar to them, and figured it was harmless. I got a bit grumpy at having to drop what I was doing right away to fix their mistake due to their laziness.
also, just to be clear. the macro only included open and close curlies? if so that's silly, as it is literally 2x the work to type. if they also included some sort of state that had to be managed, then it starts to verge towards reasonable.
True on a US keyboard, not true on many others.
I still find this kind of preprocessor abuse horrific; I’m just responding to your specific statement.
Earlier quoted context omitted.
try /s at the end of "offending" sentence, most people will look at it more kindly.
I'm sure you're great. Nothing against you, but please don't do that. Just write what you mean if you can't handle some people misinterpreting a sarcastic remark. Let's think about this for a second. What's the point of sarcasm? If you have to tell people you're being sarcastic, are you still being sarcastic? Not sure what territory, "/s" blunders into, but I'm confident it's not sarcasm. It's something else that see…