Including “And. And. And. And. And.” in a Google doc causes it to crash
281–290 of 441 posts
Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#282Earlier quoted context omitted.
There's a good deal of responsibility in writing code that is going to run over every single page (and PDF document, MS Word doc, the higher ranked Flash animations, etc.) in the visible web. For my part, I once made a bad assumption about how the Google SAX-style parser handled callbacks for zero-length XHTML start-stop tags. I presumed that would get a callback with the end-of-open-tag and start-of-close-tag pointe…
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…
One can never, however, be sure that someone really feels that way ("The secret to success is sincerity - once you can fake that, you've got it made!") Nevertheless, faking it involves never saying certain things, and that turns out to be hard, so the fallible approach that I aspire to is to assume sincerity unless given evidence to the contrary.
In this view, blameless postmortems are the right way to go, at least up to a point: neither embarrassment nor regret are things that can truly be imposed from outside, and definitely not sincerity.
Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#283Earlier quoted context omitted.
What a great story nevertheless.
It helped me empathize with young engineers dealing with their first high responsibility bug. About 4 years ago, I was managing a guy right out of school who pushed a minor bug that broke real-time risk calculations for a major multinational financial institution in the middle of the European trading day, prior to the NYC open, and people were yelling over email that they were trading blind. Someone had committed an…
This is outstanding advice, and very well put. I shall be borrowing it, thank you!
Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#284Discovered by Eliza Callahan triggered by a poem in the middle of her novel. (Friend of a coworker) That poem can be found here: https://durationandthebodyelizacallahan.cargo.site/ - if viewing on mobile you have to Request Desktop Site for some reason, at least on Android it initially shows up as a Lorem Ipsum page
Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#285Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#286Reminds me of an old joke; – I bet you a beer you can't make a logical, grammatical sentence with five ands in a row – I used to be a sign writer in a previous life and one of the jobs I had was to repaint the sign hanging over the door to this very pub. Except the publican was adamant that he wanted more space between the words. Where exactly I asked? In between the Pig and and, and and and Whistle he replied.
Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#287Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#288Relatedly, I have a string of text that, when pasted into Windows 11's Notepad, consistently causes it to crash. I don't know who to report this to.
Re: Including “And. And. And. And. And.” in a Google doc causes it to crash
#289Earlier quoted context omitted.
Some people might get off on that kind of culture. But this story makes me glad I don’t work there for some reason.
Conversely I would prefer to work in a place like that. Professionalism at scale isn’t achievable by tolerating idiotic behaviour and being nice to everyone no matter how dangerously stupid they are being. There is a point where someone has to put their foot down and demand things be done properly, otherwise the inevitable consequence is a giant mess leading to disaster. You might be used to small startup teams with…
What I've learned since then is that, with a healthy company culture, you can give frank feedback -- even about stupid mistakes -- without it being a rebuke.
It's also important that you target the right problem. It's only human for smart people do stupid things sometimes. In the specific DO...OD example, I'd be more interested in how it got through a code review than the mistake itself. (Funny enough, early versions of the C source for Bash itself had macros like that.)
Now, if someone exhibits a pattern of ignoring good, constructive feedback, that's a problem. The folks I've seen like that both gave terrible feedback and took feedback terribly. That's a behavioral problem, and you only get so many chances to correct that before it's time for them to find other employment.