Every blog starts with a first post, and every first post struggles with the same question: what do you say when you have nothing yet to say?
I've been meaning to start writing publicly for years. I have half-finished drafts on distributed systems, notes from rabbit holes into compilers, opinions about software teams that I've only ever shared in Slack messages that disappear into the archive. Time to change that.
What this is
This is a place for two kinds of writing: technical deep-dives and personal essays. They'll mix and bleed into each other, because that's how I actually think. A post about database indexing might turn into a meditation on uncertainty. A post about a trip might end with a piece of code.
I'm not trying to build an audience or grow a newsletter. I'm writing to think more clearly. If something here is useful to you, that's a bonus.
How this is built
The site is plain HTML and CSS — no framework, no build step, no CMS. I write each post as an HTML file, sync it to S3, and CloudFront handles the rest. The whole setup took an afternoon and fits in a shell script.
There's something satisfying about owning every layer. I can read the source of any page and understand exactly what's happening. No magic, no bundler output, no megabytes of JavaScript to deliver a blog post.
aws s3 sync . s3://blog.lucasprim.org \
--exclude "*" --include "*.html" \
--cache-control "max-age=300"That's the deploy. Roughly.
What's next
I have a few posts already taking shape. One on a performance debugging session that turned into an education in how Linux schedules threads. One on a decision I made at work that I'm still not sure was right. One that's just a list of things I've changed my mind about.
We'll see which one actually makes it here first.
If you have thoughts on anything I write, you can find me on Twitter or reach out by email. I read everything.