Programming insights to Storytelling, it's all here.
I was sad when I heard Paramount axed the Comedy Central website. Twenty-five years of content, gone. Why couldn’t they just let the site run indefinitely, even on autopilot? The reason: cost-cutting measures. Disney+ made a similar move when Willow flopped. Instead of letting the show quietly live on the platform, they erased it completely. Again, for cost-cutting measures.
Earlier in my career, every single person on my team had a personal website. At lunch, we’d talk about how we built them, diving into servers, Fail2Ban setups, zip bombs, and the weird little quirks we each added. It was fun, it was ours, and it felt like building a tiny home on the web.
I might be alone on this, but I’m willing to stand by it: AWS is too expensive. Not only is it costly, but it’s also absurdly complex. If a product requires you to get certified just to use it effectively, it might not be the right fit for everyone.
On a video call, silence feels awkward. It turns a conversation into a performance where every moment, even a pause to think, gets judged. Neil Postman talks about this in Amusing Ourselves to Death, but let me try to explain it with an example.
No one was expecting me. We were a dozen or so new employees. After orientation, I was dropped off at my department. The manager and the lead dev were having a squabble, walking back and forth, cursing and yelling. In a row of cubicles, each dev buried his face between double screens and headphones, pretending to be deaf to the noise. And conveniently ignoring me. I stood awkwardly, the tension thicker than a keyword-stuffed article. Until the manager walked towards me and found me in his path.
I’ve worked at the forefront of an AI-first company. Our entire product revolved around using AI to improve customer service, and the company’s success was directly tied to how well the AI performed. You’d think that in a setup like this, AI would dominate the workload, but in reality, the AI portion of the job rarely made up more than 10% of the effort.
I was inspired by Obama’s Hour of Code initiative a few years ago. I've encouraged friends and family to learn to code. If you were caught by the bug back then, chances are you’ve already seen the benefits of diving into the tech world. Whether you learned JavaScript, frameworks, or experimented with jQuery, you saw the advantage. Understanding how code works gave you that huge advantage. Coding bootcamps were popping up everywhere, drawing in crowds eager to enter the tech industry. While they were complete beginners at the time, many of those folks now have years of experience under their belts.
The past few years have been a whirlwind. Work, personal life, and family life have all shifted, and this blog has understandably taken a backseat while I dealt with challenges that required most of my time. As I look back on my contributions here in 2024, I realize I only managed to write three blog posts all year. That is something I need to change. In 2025, things will be different for one simple reason: I have a plan.
When a customer finishes pitching the website or service they want you to build, the inevitable question follows: How long do you think it will take?
When I joined a tiny startup with big ambitions, I had no idea we’d be building an eCommerce chatbot from scratch. It was my first real-world dive into AI, and I was starting with zero experience beyond a few online courses. As the first engineer on the team and the third employee overall, I had a simple goal: figure it out and make it work.
