Thoughts, stories, ideas and programming
I got a lot of mileage out of my 2015 MacBook Pro. For years it just worked — until it didn't. Apple stopped shipping updates for it. The hardware, which was already at its ceiling running a heavy JetBrains IDE alongside a handful of Docker containers, started to buckle. It wasn't a sudden death; it was a slow decline that I kept patching around until I couldn't anymore.
A father of two reflects on a quietly uncomfortable truth: the men society finds most magnetic and desirable tend to be those free from the weight of domestic responsibility. Through personal observation — at social gatherings, on dating shows, in his own mirror — he traces how fatherhood and the demands of providing gradually erode a man's time, identity, and social currency, leaving him with little to offer a room beyond talk of bills and children. He is not bitter about it. He has accepted that sacrifice is the price of purpose, framing his responsibilities not as a loss of self but as a discipline — a Samurai's devotion to the sword. The essay is honest, understated, and names something many men feel but rarely say out loud.
AI has made it tempting to clone any SaaS tool you use rather than pay for it — and if you're a developer, that temptation hits even harder. In this post, I walk through how I almost fell into that trap trying to replace Buffer with a vibe-coded clone, and why the real cost isn't the code — it's everything that comes after: hosting, pipelines, and the ongoing maintenance you never accounted for. Before you reach for the AI prompt, there are three questions worth asking yourself first.
Whenever purpose is unknown, there is bound to be abuse.Not always out of malice—often simply out of misdirection. When we don’t understand why something exists, we improvise uses that feel convenient in the moment, even if they slowly erode its value. The same is true of our time, our gifts, our relationships, and even our challenges.
If you are like me, you are tired of seeing 'AI' and 'Agent' plastered across every corner of the internet. My LinkedIn and YouTube feeds are drowning in it. Yet here I am, writing about how I went from skeptic to convert after adopting an agent-driven software development workflow.
When starting a new greenfield project, choosing the right technology stack is one of the most consequential decisions you make. Cost, operational overhead, performance, and long‑term maintainability all play a role.
From costly VMs to a self-hosted Kubernetes cluster: Discover why I finally ditched manual server management. Learn how thinking in 'Compute' instead of 'Servers' can save you money and headaches on your next hobby project.
In this candid and practical blog post, I share my evolving workflow for building software with AI as a solo developer. From debugging cron job overlaps to designing multi-channel webhook systems, I explore how AI acts as a tech fact-checker, idea validator, and learning agent. With real-world examples and iterative prompts, this post highlights the joys and efficiencies of prototyping with AI—without the hype, just hands-on experience.
Explore the complex relationship between success, sacrifice, and sustainability in this thought-provoking article about the hidden costs of achieving our goals. This piece delves into the challenges of balancing professional ambitions with personal well-being, family life, and time management. Through personal experiences and insights, it examines how modern professionals navigate the demanding journey to success while maintaining a healthy work-life balance. The article offers valuable perspectives on making smart sacrifices, managing expectations, and finding sustainable approaches to pursuing success without compromising life's essential aspects.
AI is everywhere, but skepticism remains—especially when tech hype takes over. While many claim software development is easier than ever, seasoned professionals know the truth: it’s still a challenge. A recent struggle with a session-related bug proved that AI isn’t always the magic fix. After days of troubleshooting, the solution wasn’t in fancy code rewrites but in a small detail—a capitalization issue that completely changed how cookies were managed. A reminder that experience and collaboration still reign in problem-solving.