Whee! Backticks in tweets get translated to code blocks when loaded by Slack.
Unfortunately for me, qr<>
is valid Perl, but it gives you a reference to a regex; it does not perform a match.
I’ve been away from Perl for too long. Was trying to use qr<>xms
instead of m<>xms
.
Ruby: %q<>
, Perl: q<>
Ruby: %Q<>
, Perl: qq<>
Ruby: %w<>
, Perl: qw<>
Ruby: %r<>
, Perl: NOT qr<>
, but m<>
Line of JavaScript I wrote today:
container.innerHTML = container.innerHTML;
The container
is an <svg>
tag that I’ve filled in from scratch via DOM manipulation. Firefox v90 won’t render any of it without that statement.
🙄
Always a weird feeling when you do a significant refactoring and all the tests pass on the first run afterwards.
Parallel correlated subqueries make for some insane looking code.
Database design tip: instead of a boolean column, use a nullable timestamp. This way you get your boolean value, plus the time when you set it.
-
Write failing test.
-
Spend a bunch of time trying to figure out how to implement the feature being tested.
-
Decide that the test is not complicated enough.
<blink>
and <marquee>
eat your heart out. https://twitter.com/bzamayo/status/1405882986072051725
“Another Biafra sticker!"

Shortcuts on Mac? Pffft. I want Terminal on iPhone.
… if you are a telecom executive or regulator in the United States, […] Starlink […] is a sign that reads YOU FUCKED UP AND EVERYONE HATES YOU. Read the sign. This is your fault.
Using mass nouns in APIs is a bit of a pain. Ah, the fun of translating inconsistent English into a consistent, discoverable scheme of REST endpoints.
Happy Hindenburg day!
Lately I’ve been using “update" instead of “upgrade” in commit messages, etc. because I want to say “this is newer” instead of necessarily saying “this is better”. I might actually being making things worse.
Playing Cozy Grove reminds me of reading PJF’s foraging tweets.
One more step down the road to a Web monoculture: tenfourfox.blogspot.com/2020/04/t…
Firefox is going to start trimming cross-origin “Referer” headers: blog.mozilla.org/security/…
I would prefer that they drop support for it entirely, but it’s a start.
Had a merge conflict so difficult that I copied the HEAD part into one new file and the other branch part into another new file, ran gvimdiff
on the two files, figured things out in there, then copied the result back into the conflicting file.