A few months ago, I registered the domain sparkio.me. It wasn't the result of a business plan, a startup idea, or some carefully thought-out strategy. In fact, I wasn't entirely sure what I wanted the site to become. What I did know was that over the previous months I had started building things again, and I wanted a place where I could write about them.
That realization caught me a little by surprise. I've spent more than twenty years working in software, and for most of that time technology has been at the center of my professional life. I started as a developer, later worked as a systems analyst and technical lead, and eventually moved into management and leadership positions. As my responsibilities grew, the nature of my work changed. I spent less time writing code and more time helping teams make decisions, solve problems, deliver projects, and navigate the complexity that inevitably appears as organizations grow.
I don't see that evolution as a loss. Some of the most valuable lessons of my career came from those years. Understanding how people work together, how priorities compete for attention, how technology creates business value, and how difficult it can be to align different perspectives around a common objective taught me things that I could never have learned by focusing exclusively on code.
At the same time, something else happened, although I didn't really notice it while it was happening. The act of building became increasingly distant from my day-to-day life. I was still surrounded by software, still discussing architecture and delivery, still involved in technical decisions, but creating something from scratch for my own curiosity became increasingly rare.
Part of that was simply a consequence of life becoming busier. Anyone who has worked in the industry long enough knows how easily personal projects get pushed aside. An idea appears, seems interesting for a few days, and then disappears under the weight of work, family responsibilities, and the dozens of other things competing for attention. Another part of the problem was that experimentation itself carried a relatively high cost. Even small projects required enough setup, enough learning, and enough effort that many ideas never progressed beyond a note in a notebook or a paragraph in a document.
What has changed over the last couple of years is not that I suddenly became more creative or started having better ideas. If anything, I've always had more ideas than I knew what to do with. The difference is that the cost of exploring those ideas has fallen dramatically. Today it is possible to move from curiosity to prototype much faster than at any other point in my career. That doesn't eliminate the need for technical knowledge, judgment, or hard work, but it does make experimentation accessible in a way that simply wasn't true before.
The result is that I've found myself building again. Not necessarily large projects, and certainly not with the expectation that every idea will become a business. In many cases, the goal is simply to understand a problem better, learn something new, or satisfy the curiosity that comes from wondering whether a particular concept can actually work. Some of those experiments turn into useful products. Others reveal flaws in the original idea and quietly come to an end. Both outcomes are useful because both teach something.
That's ultimately why SparkIO exists. I wanted a place to document the process rather than just the results. Most people only see finished products, but the interesting part is often everything that happens before that point: the false starts, the technical trade-offs, the assumptions that prove wrong, the unexpected discoveries, and the small lessons that accumulate over time. Those are the things I want to capture here.
I don't know whether any of the projects I write about will become significant businesses. Most probably won't. What I do know is that after more than two decades in software, I still enjoy creating things, I still enjoy learning, and I still find satisfaction in turning an idea into something tangible. For now, that's reason enough to keep building and reason enough to keep writing about it.
— Diego Cervera