So here's what's been happening lately. After my contract ended with my last client, I decided to take a different path than usual. Instead of immediately jumping into the next opportunity, I'm working on NeoHaskell full-time while living off my savings.
I know that might sound concerning to some, but there's actually a solid plan behind this decision. The goal is straightforward: turn NeoHaskell into something that can sustain itself financially. Not just as a hobby project, but as something I can actually live from.
The approach I'm taking is very production-focused. I'm starting with the core infrastructure that any real application needs - an event store built on PostgreSQL. Nothing experimental or overly clever, just reliable technology that works. After that comes the command handling and read models. These might not be the most exciting features to talk about, but they're what you need to actually ship software.
To help make this sustainable, I've opened several ways to support the project: Open Collective, Ko-fi, GitHub Sponsors, and a few others. Every contribution helps keep this going.
What makes me optimistic about this path is that I already have a prospect client who's committed to using NeoHaskell for their project. This is huge because it means every feature I'm building is being validated against real production needs. Instead of guessing what developers might want, I'm implementing what someone actually needs to ship their product.
This client-first approach is shaping the project in really positive ways. I'm focusing on the leanest possible changes that deliver immediate value. Every addition to the language and ecosystem is driven by actual requirements, not theoretical possibilities. This constraint is exactly what NeoHaskell needs right now.
I'm also offering consulting services around NeoHaskell and event-driven architectures. If you're curious about using NeoHaskell for your project or want help with event sourcing in general, I'd be happy to chat.
The next few months are going to be interesting. Working on NeoHaskell full-time means I can finally give it the attention it deserves. The event store is coming along nicely, and with real production use cases driving development, I'm confident we're building something genuinely useful.
Thanks for following along on this journey. Whether you're contributing code, supporting financially, or just keeping up with the updates, you're helping make this project real.
Top comments (0)