A year after Astro

It’s been about a year since my last commit to Astro, which feels strange to write down.

It wasn’t some massive chapter of my career, but it mattered more to me than the number of commits would suggest. It was one of the first times I got to work inside an open source project and actually get a feel for how it all fit together. What I remember most is that Astro felt active without feeling chaotic. There was a real effort to make the project understandable and approachable, and that stayed with me more than any specific contribution did.

What drew me in at the time wasn’t some grand plan to become a major open source contributor. I was mostly curious, and I liked what Astro was trying to do. It still felt early enough that you could watch ideas taking shape in real time, and contributing didn’t feel gated behind some invisible wall where only the people who already knew the whole architecture were allowed to touch anything. That made a bigger difference than I expected, because it turned the project from something interesting to look at into something I could actually participate in.

Open source gets romanticised a little

From a distance, open source can look like this clean expression of engineering craft where smart people build useful things in public and everyone benefits from the result. Some of that is true, but once you get closer to it you start to notice how much of the work is not the part people usually talk about. There is reviewing, triaging, documenting, clarifying intent, helping people get unstuck, and trying to keep the whole thing coherent as it grows. The code is obviously part of it, but it isn’t the whole thing.

Even a small amount of firsthand exposure to that changed how I think about open source work. It gave me a much stronger appreciation for the people who keep projects moving, especially the maintainers and contributors doing the less glamorous work that makes a project usable for everyone else. It’s easy to admire a polished release when you’re just consuming it. It’s a different thing to appreciate the ongoing effort that got it there.

I also have to give the Astro team credit here. They made open source contribution feel approachable in a way that was honestly a delight. A project can be technically impressive and still feel pretty hostile to outsiders, but Astro never felt that way to me. Part of that was the project itself, and part of it was the people around it. I really enjoyed the Discord banter, and for the early docs team Discord honestly became a bit of a crutch for how we got work done. It gave everything a more immediate and human feel than I expected, and working in and around that repo made me more familiar with open source contribution as an actual practice instead of just something I generally thought was good. More than anything, it left me with a lasting appreciation for the work people put into building software in public.

What I liked about it

I think what appealed to me most was that the work sat at the intersection of engineering, communication, and adoption. I’ve always liked that layer of software more than isolated implementation for its own sake. I like the part where architecture still needs language around it, where developer experience matters, and where documentation is part of how a tool becomes real to the people trying to use it. Astro was a good reminder that useful tooling isn’t just about technical correctness. It’s also about clarity and approachability, and about making somebody’s first interaction with the project feel considered.

That kind of work feels pretty close to how I naturally like to operate anyway. Not purely frontend, not purely backend, not purely infrastructure, but somewhere around the seams where systems, people, and workflows meet.

Why I haven’t found my way back yet

I’d love to find my way back into the world of open source in a more meaningful way, and I mean that pretty literally. Not in the vague sense of saying “someday when things slow down,” but in the sense that I still think about it and still feel the pull toward contributing to tools that other people build on. There is something satisfying about that kind of work because you’re not just solving a problem for one team or one client. You’re helping shape the conditions other people work inside.

But the practical reality is simpler than the aspiration: I gotta make money to survive!

Most of my time and energy have to go toward the work that keeps the lights on, and once that equation is in place it answers a lot of questions for you. Open source is meaningful work, but meaningful doesn’t automatically mean economically viable, and that’s a tension a lot of people navigate whether they say it out loud or not.

Maybe that’s part of why I appreciate maintainers more now than I did before. Even a brief experience contributing to a project like Astro makes it obvious how much effort gets donated into the ecosystem by people who could just as easily spend that same energy elsewhere. So I’m very happy Astro was able to find a sponsorship cycle that helps their maintainers keep their lights on.

For now, I mostly just carry the appreciation forward, and maybe that’s enough for the moment for me. Not as a permanent answer, but at least as an honest one.

A year later, what I still value most about that experience isn’t just that I got a few commits into a project I respected. It’s that it made open source feel a lot more human to me. Less like an abstract community and more like people doing careful work in public and making it easier for the next person to build something good.