I joined Twitter in 2007 and my brain slowly morphed over the next 15 years from hopelessly verbose to nihilistically pithy. I've kicked the Twitter habit, but the takes keep flowing. That's why I post them here and format them as a social network of one. They're also cross-posted to my Mastodon account. You're welcome to bookmark any of these takes, though I'm not sure why you would.
By the way, the hearts and like counts are fake. They're just there to make you feel safe.
The Breaking Change mailbag is starting to run low. Email podcast@searls.co and ask me literally anything and I will maybe possibly answer it in the next episode! 🤞
In hindsight, when I was under a lot of pressure to drop CoffeeScript a decade ago in favor of "modern" JavaScript (defined as using tools like babel and webpack), I wish I'd held my ground.
Without a doubt I'd be better off today if I'd just gone straight from CoffeeScript to real ESM and import maps. Just spent three hours dealing with bitrot in a webpack config with no end in sight. The JavaScript Dream was always a house of cards.
Just used my Apple Vision Pro for anything other than screen sharing in over a month because my Mac was installing an OS update.
This isn't how I expected DHH would declare 2024 the year of Linux on the Desktop world.hey.com/dhh/vscode-wsl-makes-windows-awesome-for-web-development-9bc4d528
Spent all morning trying to figure out why every postcss plugin that has anything to do with color conversion can’t handle CSS Colors 4 rgb() calls (even the two that claim to do exactly that).
Now I have my own custom postcss plugin named 'these-colors-dont-run’ that I have to drag around until the end of time. Great gist.github.com/searls/d9ca494792736f94d765223c6ba98d33
A weird consequence of Japan spanning a single time zone is that lots of apps stop working outside business hours for "maintenance".
I lost an hour today freaking out over error messages that my account was locked right around 11pm JST because (I now realize) their servers were only partially shut down.
Feels weird knowing—100%, not a doubt in my mind, knowing—that humanity will have cured cancer before it creates a system that can autonomously maintain an accurate inventory of the food available in one's kitchen.
This month’s Searls of Wisdom newsletter just went out — it’s all about how to travel well in an era of high prices, poor service, and crowded destinations. Sign up now and you'll get it: justin.searls.co/newsletter/
Just realized it's much more acceptable to say I'm too busy writing to have time for reading than it is to admit I'm too busy talking to have time for listening.
I started a new Rails app in January and I’ve now been hit by damn near decade-old bugs in 3 of Ruby’s most popular gems. Who did I piss off? github.com/paper-trail-gem/paper_trail/issues/1464
Until yesterday, I had never heard anyone but me in the Ruby community express confusion over the fact that Rails produced both paper_trail the audit log gem and Papertrail the logging SaaS.
But seriously, how the hell did everyone else keep these straight in conversation? (My bet is that they didn’t, actually)
I just wrote this utility class for my Rails app to ensure my Rake tasks logged their output to my terminal without screwing up anything else.
Was this actually necessary? gist.github.com/searls/a2a642520b36594bb9002e2f75761eec
Breaking Change v6 includes a (rather spicy) PSA detailing how Stripe may be inadvertently giving your product away for free—oops! Probably my best episode yet. justin.searls.co/casts/breaking-change-v6-pausing-doesnt-pause/
One of the most valuable things about writing automated tests is that they force you to run your code very many times in very many ways.
It’s important to understand this is not a value of testing per se, though, and that there are other valid ways to achieve the same goal.
Two decades as a programmer hasn't made me any better at estimating how long it'll take me to write software, but it's made me MUCH better at estimating how long other things will take. I'm a master at intuitively timing multiple dishes to finish simultaneously, for example.
In hindsight, I think I may have spent a large number of years misdiagnosing myself as having a push notification management problem when I actually had a "too many people in my life" problem.
What's a framework feature you probably ought to use but you nevertheless avoid?
For me, it's file generators. I can barely remember why, but with the sole exception of database migrations I never take advantage of any of Rails' generator commands.
A lot of people are surprised Vision Pro’s field-of-view is so narrow, but it makes sense if you think about it: even if Apple invents all the technologies needed to release a Vision product in an eyeglass form factor, it’ll never be much wider than 90º.
Apple’s resistance to proper VR features suggests they don’t want us getting used to anything that wouldn’t be possible in their ideal version of the product.
I thought programming was hard so I learned Japanese.
I thought Japanese was hard so I learned golf.
Golf was hard so