3,824 karma · joined May 13, 2009
Ex-Google, ex-Etsy
Writing: https://www.bitlog.com, https://www.clientserver.dev Email: jakevoytko@gmail.com Twitter: @jakevoytko
Obviously you need to consider both net worth and cash flow when making a decision like that, but don’t underrate the difference that improved cash flow makes!
What has changed in the past ~15 years? Many libraries and plugins have their own compilers nowadays. This increases the difficulty of successfully integrating with Bazel. Even projects that feel like they should be able to properly integrate Bazel (like Kubernetes) have removed it from the project as a nuisance.
Back when it was first designed, even compiling code within the same language could be a struggle; I remember going through many iterations of DLL hell back when I was a C++ programmer. This was the "it works on my machine" era. Bazel was nice because you could just say "Download this version of this thing, and give me a BUILD file path where I can reference it." Sometimes you needed to write some Starlark, but mostly not.
But now, many projects have grown in scale and complexity and they want to have their own automated passes. Just as C++ libraries needed special library wrappers for autotools within Bazel, now you often need to write multiple library compiler/automation wrappers yourself in any context. And then you'll find that Bazel's assumptions don't match the underlying code's. For example, my work's Go codebase compiles just fine with a standard Go compiler, but gazelle pukes because (IIRC) one of our third-party codegen tools outputs files with multiple packages to the same directory. When Etsy moved its Java codebase to Bazel, they needed to do some heavy refactoring because Bazel identified dependency loops and refused to compile the project, even though it worked just fine with javac. You can always push up your monocle and derisively say "you shouldn't have multiple packages per directory! you shouldn't have dependency loops!", but you should also have a compiler that can run your code just like the underlying language without needing to influence it at all.
That's why most engineers just need command runners. All of these languages and libraries are already designed to successfully run in their own contexts. You just need something to kick off the build with repeatable arguments across machines.
It's a shame. Twitter used to be the undefeated king of breaking news.
"Don't argue about the definitions of words online" is my "Never get involved in a land war in Asia." If people know what you mean but ignore it in favor of picking a fight, they're arguing for sport and I don't want to get involved with it.
In the past few months, I've learned that (a) writing a bulleted outline is a cheat code for producing decent work quickly, (b) every newsletter is a reminder that people could unsubscribe, so skip publishing issues that you're not proud of, (c) people really like stories, and (d) it's okay to have a mix of formats.
At this point, he basically started leaning into controversy for pageviews. He'd start linking to the controversial section of each post right at the top of the post. After a few months or so I had to unsubscribe, after years of reading his blog and Dilbert cartoons/books.
He's become such a gremlin that I won't be 100% sure he's serious about this until he actually dies.
r/programming is the only subreddit I regularly visit where there are a bunch of posts with 0 upvotes in the top 30. There are 16 right now on the Hot view.
My first 40 subscribers came from direct friends and my LinkedIn network.
I got about 150 subscribers from a single popular post on Hacker News, posted here: https://news.ycombinator.com/item?id=43461618
The remainder have come from regular posting on BlueSky, Mastodon, LinkedIn, Substack notes, and starting to get search traffic from Google.
I've gotten no traction from Reddit (wow, the programming subreddits are so much angrier than every other subreddit where I contribute!) Twitter (seems like it's pay to play, which I won't do) or IndieHackers (I post milestones just for fun, but it hasn't amounted to anything).
I've found that I need to post twice a week to grow. I had a period where I was sick and was putting less effort into posts, and another period where I was dealing with a mortgage and had to post only once a week, and my subscriber growth treaded water instead of gradually growing. Even casual visitors to the site can tell the difference between moderate and minor effort.
So in my mind, Bazel is no longer worth it unless the savings are so great that you can afford to staff a build team to figure these things out. Most teams would benefit out of using simple command runners instead of fully-fledged build systems.
I had a daughter almost 2 years ago, and for a while I didn’t have any free time. But once I started getting a few hours in the evening, I wanted to start up side projects again. I found it frustrating to work on coding projects in 1-2 hour windows. But writing is a little easier; I feel like progress is a little more linear with writing, and having the Monday/Thursday deadline has helped me just ship.
Our team also had a very grindy culture, so "I'm going to put in extra hours focusing exclusively on our top crash" was a pretty normalized behavior. After I left that team (and Google), most of my future teams have been more forgiving on pace for non-outages.
Outside contributors to our team absolutely hated us for it (and honestly some of the people on the team hated it too); everyone likes it when their product is fast, and nobody likes being held to the standard of keeping it that way. When you ask them to rewrite their functional coding as a series of `for` loops because the function overhead is measurably 30% slower across browsers[0], they get so mad.
[0] This was in 2010, I have no idea what the performance difference is in the Year of Our Lord 2025.
On the first playthrough when I woke up with amnesia, I simply played a cop with amnesia in all of my responses. It was goofy, I annoyed Kim for fun, I beat the game, etc.
On the second playthrough, I chose all of the dialogue options that honestly explained how the character became an alcoholic. It changed the vibe of the whole game to somber, and I was fascinated that the relationship with Kim felt different. It also felt natural to explore all of the lore and sidequests of the game involving the pale in this mood.
And then I went on a completionist binge and found some great social commentary in the "high-net-worth individual" sections.