Recent launch of Basecamp’s Hey service made me realize how much I love email. Their pitch is actually on point:
Email gets a bad rap, but it shouldn’t. Email’s a treasure.
Damn right it is.
Email is a set of open protocols. We can argue about the “implementability” of IMAP clients and such, but it remains the only widely used, open communication system we have on the internet. XMPP was supposed to become its equivalent for instant messaging, but failed, and no other protocol took its place because it’s in no messaging platform’s interest to give its users freedom of choice. There are multi-protocol messagingapps, but they are essentially UI hacks. Even Twitter, which arguably isn’t an IM, is gradually limiting what third party clients can and cannot do.
I went to music school as a kid. Ages 7 to 13 I studied classical violin and basics of music theory. I played in duos, trios, and orchestras. Even as a college student, despite my amateurish skills, I’d still find decent orchestras I would join and play many concerts with. All this, despite my slight disdain for classical music with its pompous ethos and pretentious audiences. I stopped playing after moving abroad about a decade ago, leaving my violin behind me, thinking the music performing chapter of my life was over.
Imagine my surprise when some years later I found myself jamming cave music with my friends, now a software engineer at the age of 34.
What if you are, like me, a classically trained musician who’d, too, like to indulge themselves in cave music? What’s your path? And how hard would it be?
The other day I’ve been looking at a Raspberry Pi 4 that’s been laying around, thinking of what to do with it. I quickly googled around how to setup AFP on it, so that I could put it by the router, connect all the portable hard drives and just use it as my “stash drive” from any device in the house. A tiny NAS-like thing.
I quickly realized there were some problems with my hard drives, namely that they all used different filesystems, so I spent a couple of hours (oh yeah) juggling data between them, formatting them onto reasonable file systems that both Linux and macOS can easily read, and setting them up as mount points for Netatalk to serve. I then started exploring other options for my photo library, which I was managing with iCloud at the time. I remembered that I strongly preferred Google Photos for cataloguing and managing albums and shares, so I figured perhaps it’d be a good opportunity to move all my photos there, and perhaps explore a backup system? You know, a backup for my backup, some software that fetches photos from Google Photos periodically (say, daily), puts them on one of the Pi’s external volumes for rclone to later pick up and store safely on b2. That’s when the clock showed midnight and my wife asked why wasn’t I going to bed yet.
In January 2019 I bought an 11-inch iPad Pro. It’s a magnificent piece of hardware that you can readmanyreviews of online. The screen is brilliant, the portability and battery life are unmatched, the performance is swift (until you’re trying to perform a long-running CPU-intensive operation, that is).
The iPad Pro was always meant to be my “personal computing” device. I don’t really code in my free time anymore, so issues of not being able to run VS Code on it are not my issues. I do some music production, lightweight photo editing and I write, that’s all I require from my personal computer. (ah yes, and the “occasional Netflix”) So at first glance the magnificent iPad Pro should be amazing, shouldn’t it? Turns out that for me, it wasn’t, for many tiny reasons. Tech reviewers sometimes refer to this as “the 10%” of things you need to be able to do on your computer, because indeed the iPad Pro can often handle that 90%. Yet even with iPadOS (aka iOS 13), which made it much more a real computer than any previous software upgrade, there’s still a ton of things that it either doesn’t do well, or doesn’t do at all. I agree with Gruber: the iPad didn’t fulfill the potential that was always in the hardware itself, even after 10 years of being on the market.
After some years of self-hosted statically-generated websites, I am back with the love of my life that is WordPress.com. Reasons are as follows:
I deal with technical problems 8 hrs a day. I don’t want to troubleshoot CI, AWS, SSL or whatever other issues that stop my website from being successfully built or deployed in my free time.
I cannot stress this enough but the new editor that WP 5.0 comes with is just amazing. I ❤️ it so much that I don’t want to be writing markdown anymore, even if it means I can’t compose my posts in vim. (does anyone really want to write blog posts in vim?)
WordPress.com’s personal plan is actually amazingly good value considering what you get for the money.
I’m not a designer, I can’t frontend well. Themes I was able to find for my static generators didn’t please me, and I want my website to look good.
So there, I’m not a hacker anymore. But hopefully I’ll become an amateurish writer again.
Marc Andreessen writes about how ill-equipped the United States is to handle the ongoing COVID-19 pandemic, and concludes that it’s due to the fact that the America lost its ability to “build” things, be it medical equipment, infrastructure, or financial mechanisms that’d allow the federal government to support its citizens better.
There’s a particular paragraph that stood out to me and made me think about a particular lack-of-readiness aspect of COVID-19 epidemic, not only in the US, but all over the world and in particular in Western Europe:
We see this today with the things we urgently need but don’t have. We don’t have enough coronavirus tests, or test materials — including, amazingly, cotton swabs and common reagents. We don’t have enough ventilators, negative pressure rooms, and ICU beds. And we don’t have enough surgical masks, eye shields, and medical gowns — as I write this, New York City has put out a desperate call for rain ponchos to be used as medical gowns. Rain ponchos! In 2020! In America!
I am slowly beginning to grasp the concept of “walkability.” It’s not about whether there are wide sidewalks (although there better be). Spending my second week in California I realize the absolute key part is whether you need to cross multi-lane streets/roads every 50 meters. Nothing kills the joy of walking around than having to stop all the time.
(hint: in Amsterdam you can usually just walk through the street without paying attention to lights, because there’s either no traffic, or the traffic will let you do that)
It also helps if I’m not the only pedestrian within a 5 mile radius. The other day a lady in a huge SUV pulled over to ask if everything’s ok because I’m walking down the street; she thought my car broke down and I needed help. 🤦🏻♂️
Stallman affair touches on something else: a simmering resentment about the treatment of women by the scruffy brainiacs who built our digital world, as well as the Brahmins of academia and business who benefited from the hackers’ effort. With the Epstein revelations that resentment has boiled over.
It’s incorrect to think that the controversy around Stallman’s CSAIL emails is about “political correctness” or that his opinions have been “mischaracterized”, as he himself puts it.
Decades of silencing critics that were pointing out creepy behavior towards women have to finally come to an end. It has nothing to do with his achievements or contributions to free software, nor does it diminish them. Great works do not grant immunity.
A couple of weeks ago I went to Paris to attend dotGo (thanks, MessageBird!), one of the biggest Go conferences in Europe. dotGo lasts only one day, and it’s single-track, but it’s a solid offering with great organization, excellent venue and awesome talks. I realize I sound like a dotGo commercial, but as a former academic I remain amazed at how much better professional conferences are, and in the case of dotGo we’re talking orders of magnitude.
Not all of the dotGo 2019 talks were brilliant, but I see even that as an advantage; it’s easy to make a good conference by putting an all-star speaker line-up. It doesn’t allow for younger, less known people in the community to present anything, though, and I think dotGo organizers’ decision to present a mix of established engineers and newcomers was very successful. They also succeeded in having a variety of topics, and many of the talks weren’t necessarily Go-specific. Sure,