Context injection for the good? I listened to Adam’s voice memo about the awful reality and challenge the Tailwind CSS team is facing. Amidst that, I had an idea to help solve Tailwind’s marketing dilemma. Their docs site traffic has historically been a primary marketing channel for them,
I’ve made plenty of posts and comments that may read as bearish on AI. To be clear: I am extremely bullish on AI. AI has already proven to be a massive force multiplier. I’ll be sharing projects I’ve consulted on soon that demonstrate this definitively. Over the
What Happened to the Market While I was building Audetic slowly, most of the market did the opposite. Voice tooling, transcription, and AI-assisted workflows turned into a race. Companies optimized for speed to market, user growth, and valuation rather than durability. The finish line was either acquisition or collapse. In
Disclaimer This is not an anti-AI post. I use AI coding tools daily. Heavily. This is written from the perspective of someone who depends on them, understands their strengths, and has felt their limits firsthand. The critique here is not about capability. It is about incentives, misuse, and what happens
A brief disclaimer I’m still relatively new to Scala, I picked up Scala around 2 years ago and have not been able to put it down. I built a career leaning front end heavy, with plenty of back-end middle tier services in the mix (rest APIs, GraphQL, collection services,
Synopsis A comprehensive case study demonstrating 0-to-1 product development. I was tasked with leading an AI-native initiative spanning both product development and forward deployment responsibilities, building and validating a proof-of-concept prototype with Model Context Protocol integration within two weeks. Through customer testing and feedback across four enterprise customers, I believe
Coding agents often produce messy, unreliable code ("code slop"), and my goal with CodeLoops has been to inch us towards the holy grail: autonomous coding agents. You can get caught up to speed in my original article. Starting as a proof-of-concept, CodeLoops showed early promise with a JSON-based
As a software developer, I’ve been fascinated by the potential of coding agents to transform how we build software. These tools have made impressive strides, empowering non-developers to create greenfield projects and simplifying tasks for seasoned coders. However, for serious software development, they fall short nearly 100% of the
You see back in the day, deploying a single page app(SPA) or static site was dead simple. We had tools like now, firebase deploy, etc that offered one command deployments for any client side app framework. I loved those tools. But when I reached for them to build a
Reasoning About JavaScript Errors Used to Be Simple We had a dedicated channel in callbacks. We knew when something went wrong for that function. fs.readFile('file.txt', (err, data) => { if (err) { console.error(err); return; } console.log(data); }); You checked for the error. You dealt with
I was writing C# when Node.js came along. You could run JavaScript on the server now. I was in awe. It wasn’t perfect. But it was freeing and dynamic. I went all in. Then came React. Its mental model aligned perfectly with mine. It was simply the V
GoDeploy was created to solve a real problem I had while building Audetic's user facing apps and sites... You see back in the day, deploying a single page app(SPA) or static site was dead simple. We had tools like now, firebase deploy, etc that offered one command