To AI or not to AI.
Some things I will write with AI, using AI, but one thing I promise.... Every single journal entry I will proof read, probably tweak, and probably change to my voice...

Founder, engineer, and reluctant writter. I write about AI, the unbuilding of old assumptions, and what it takes to stay useful when the tools learn faster than you do.
Not a homepage so much as a small lobby. Pick the door that fits the day.
Start with Founder Notes. Then read the 2022 timeline entry — that's the year I stopped pretending.
Read the AI & Unlearning series, then Build Logs. Pull requests on my essays are welcome.
Skip the takes. Read 'The engineer's new instrument', then the three Kraken build logs.
Open the Knowledge Garden, click a node at random. That's how I think — pull on a thread until something gives.
A little bit how I think + a network of people whose core principles align with mine. Each node was invited by someone already inside — there is no public sign-up. The shared concepts that connect us are what trace the lineage.
The places I keep returning to. The shape of them changes; the gravity doesn't.
Half-formed thoughts, weekly build logs, slow lessons. Updated when I have something worth posting — not on a schedule.
Some things I will write with AI, using AI, but one thing I promise.... Every single journal entry I will proof read, probably tweak, and probably change to my voice...
Things I'd tell him about the year after the exit, the silence, the slow rebuild, the part nobody warns you about.
The version of Kraken I'm building in 2026 is not the one I pitched in 2024. I want to write down why, before I forget the difference.
Distilled from a decade of doing it wrong. The ones nobody really tells you because they sound either obvious or terrifying.
A decade-old codebase is a love letter from a stranger. How I now write code I expect someone else to inherit on day 1.
If you need a daily ritual to find out what people are doing, the problem isn't communication — it's that nobody knows the plan or it's because a mindset was put there due to AI production over the team, the transformation cemented the practice instead of liberating the understanding of where the focus should be... team and collective-accountability
Essays, articles, books and posts I let sit for months. Some are series. Most started as journal entries that wouldn't let go.
A long essay on what it means to build software in the era of agents — and why the craft has changed shape, not died.
This piece is the start of a series. Each piece stands alone, but they're connected — each one picks up a thread the previous one left, building toward something specific. If you work on AI in real systems, follow along. I'm starting with a question: what assumptions in your work are artifacts of an old constraint set, and which of them are you still defending out of habit? I'd be curious which one comes to mind first. In my case, what I had to unlearn was essential to see, to learn, to understand... what? Well, that’s what these articles are about.
Notes toward a theory of why the best technical systems mirror the best social ones.
A field manual for founders who built the company before they finished building themselves.
Strategies, tactics, and small rituals for the months your old playbook no longer applies.
Not case studies. These are alive — some growing, some retired, all still teaching me something.
Led business development, operations, technology delivery, and team growth for a custom software development consultancy, helping drive revenue through the successful acquisition, delivery, and management of over 18 software projects across multiple industries.
Built and mentored a multidisciplinary team of 10+ engineers and professionals, overseeing recruitment, performance, project execution, and long-term organizational planning. Managed client relationships from initial engagement through proposal development, solution design, estimation, budgeting, contract negotiation, delivery, and ongoing account growth.
Directed both onshore and offshore teams while leading software architecture, engineering, and cloud deployments across AWS, Azure, and DigitalOcean. Successfully delivered enterprise platforms, CRMs, mobile applications, social networks, blockchain solutions, customer experience systems, educational platforms, and industry-specific software for sectors including government, energy, finance, retail, hospitality, healthcare, and professional services.
Played a key role in company growth initiatives, including acquisition activities, internal valuation processes, business turnaround efforts, and strategic planning. Acted as a bridge between business, product, and engineering, translating customer needs into scalable technology solutions while ensuring profitability, delivery excellence, and long-term client success.
A SaaS for people who run personal blogs and want to be part of a real network without the noise of public sign-ups. Each blog is a node; each invite is a thread in the lineage. There is no signup form — you arrive because someone you trust vouched.
The Universe layer (codename Stellis) projects every connected blog into a single cosmos. Topics orbit a sun. People sit in bands by trust depth; activity gravity pulls the active ones closer. Resonance scoring surfaces "people you don't know yet who think like you" without ever flattening the chain that got them in.
Built on Apache AGE so the graph is real, not a side-table. Codename: Stellis.
The site you're reading. A cinematic, interactive home where the work is the door — long-form writing, a working journal, a portfolio that breathes, and a constellation of people I trust with the questions I'm actually sitting with.
The aim isn't reach. It's resonance: a small place that signals what I'm doing right now (the Emission System) and a Universe that lets a handful of trusted blogs cross-pollinate without anyone needing to chase followers.
The story I tell myself when I need to remember why I started. The companies are footnotes; the years between them are the chapters.
TBD
Splitting time between scaling Core Sports past 50 federations and spinning Kraken out of internal use. Writing weekly. Trying to do less, better.
Took ownership of the platform org. The work now spans cloud-native infrastructure, distributed systems, and the AI layer that's reshaping how we operate at scale.
Took a year off, then made the dumbest, most necessary decision: build the boring infrastructure under a sport I love. First customer in week six.
Stepped into the director seat. Owned engineering direction, architecture approvals, cloud strategy, and the policies that turn good intent into shippable software.
Wrote 60+ essays, no startup. Therapy. Long walks. Re-learned why I started building things in the first place.
Worked on customer-perceived latency in PayPal's payment + checkout flow. Direct line from a millisecond shaved to conversion saved.
Six years of work compressed into a 90-day diligence and a strange spring of decompression. Learned the difference between an exit and an integration the hard way.
Built the bridge between an Argentine technology shop and North American businesses. Mid- and long-term relationships, not transactions.
Stepped up from CTO when our CEO left. Read every operations book I could find. Threw most of them away after six months.
Eighteen+ custom software projects, ten-person team, on/off-shore coordination, and the unglamorous craft of running a company: budgets, valuations, acquisition. The single biggest jump from engineer to operator.
Started as a small consulting project for a regional airline. Became a company by accident, then on purpose.
Two and a half years building for Southwest Airlines. Java + Spring on the back, React on the front. The shape of "enterprise frontend" before that phrase meant anything.
Where I learned what real production traffic feels like. The first time I deleted a database in production. The first time I told the truth about it.
Two years across Nextel and American Airlines accounts. Web services, BPEL, weblogic queues — the messy plumbing that makes 'just call the API' work.
A weather widget that 11 people used. I refreshed the analytics every six minutes. I haven't really stopped since.
Started as a Java programmer on the Nevada CRM project. Same year I started my Systems Engineering degree at IUA. The two would feed each other for the next five years.
Profiles, talks, repos, and the small public things I keep maintained.
One letter per month. Notes from the desk: what I built, what broke, what I'm rethinking, and the one thing I'd undo if I had the year back.
This isn't a quiz, and there are no wrong answers. A few short interactions — you'll be done in less than two minutes. What you find depends on what you choose.