
When Speed Became Trust
When trust is set on the outcome, but not on the impact
Reader poll · Open now
AI & Unlearning
Things to take into account when building a web platform through... Vibe coding... (?)
Leadership & Scale
Should AI increase what your people can do, or decrease how many people you need?
Entrepreneurship
The things I wish someone had told me before building, leading, failing, adapting, and trying again.
Lessons Learned
Does AI amplify strong performers more than it helps weaker ones catch up?
Choose carefully, or not! Some topics will be vanilla; others will be controversial.
Essays, articles, books and posts I let sit for months. Some are series. Most started as journal entries that wouldn't let go.

When trust is set on the outcome, but not on the impact

The shift from a three-month to a three-day, end-to-end platform build is not a story of 30x productivity, but rather a re-shaping of work where AI removes constraints and renders traditional, slow development habits obsolete. By challenging assumptions like upfront architecture and long feedback loops, this change demands a new approach to software engineering where the process is no longer defined by old constraints.

Most organizations think they’ve made the transition to AI-native when they’ve only deployed AI into the organization they already have. The real crossing begins after the productivity gains—when companies have to confront a harder question: if AI changes the cost of coordination, context, execution, and organizational memory, which parts of the operating model still make sense? That reckoning reaches far beyond technology. It touches roles, seniority, rituals, team structures, hiring, leadership, and ultimately the way organizations compete. AI-augmented and AI-native may look similar from a distance. The difference is structural.

For years, I believed careful upfront design was an engineering discipline. I now think much of it was something else: a coordination tax. I realized that the agreement between people was the expensive part. AI doesn’t eliminate that need, but it changes its price dramatically. Once I saw that, I started questioning which engineering rituals are still earning their cost or price.

There’s a difference between an organization that uses AI and one that’s designed around AI. The first deploys new tools into an existing operating model. The second redesigns how work, coordination, memory, and decision-making actually happen. That’s the difference between being AI-augmented and being AI-native.
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.
Half-formed thoughts, weekly build logs, slow lessons. Updated when I have something worth posting — not on a schedule.
For a long time, I thought of sports and exercise as something that competed with work and family for my time
The older I get, the more I realize that family isn’t something that exists alongside the rest of my life—it’s the reason the rest of it matters
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...
Everything I knew about building software has a shorter expiration date now. Here's what I'm letting go of — and what I'm keeping.
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
Distilled from a decade of trying. The ones nobody really tells you because they sound either obvious or counterintuitive.
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.

Founder, engineer, and reluctant writer, but a heavy thinker. I think and write about AI, the unbuilding of old assumptions, and what it takes to stay useful when the tools learn faster than you do.
The places I keep returning to. The shape of them changes; the gravity doesn't.
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,…
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;…
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…
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
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.
Stepped into the director seat. Owned engineering direction, architecture approvals, cloud strategy, and the policies that turn good intent into shippable software.
Worked on customer-perceived latency in PayPal's payment + checkout flow. Direct line from a millisecond shaved to conversion saved.
Built the bridge between an Argentine technology shop and North American businesses. Mid- and long-term relationships, not transactions.
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.
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.
Two years across Nextel and American Airlines accounts. Web services, BPEL, weblogic queues — the messy plumbing that makes 'just call the API' work.
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.
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.