Let me take you on a short journey to explore what futility looks like in software form. This morning, in a lapse of optimism that I can only describe as self-harm, I partnered with Cursor to implement a relatively simple analytics feature. We never made it out of the planning
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
For Audetic, I’m not just cranking out features as fast as possible, I’m crafting a platform that’s scalable, secure, and built for the long haul. My engineering approach is slow and steady for this one and in this post, I’m going to share a glimpse into
In a world that glorifies speed and relentless hustle, I’m charting a different course with my company, Audetic. After over a decade of crafting SaaS products for startups, I’ve learned that there’s immense power in slowing down. I’m embracing “slowification", a deliberate, thoughtful approach that
For years, the term "MVP"—minimal viable product—has been touted as the silver bullet for product development. In its early days, MVPs promised a lean, iterative path to market. But as the industry has evolved, so too have the ways in which “MVP” is interpreted and misused.