Guides, tutorials, and insights on AI coding tools and API providers.
Last Thursday at 3 PM, our finance person dropped a screenshot in the company Slack. Our AI inference cost curve had gone nearly vertical — 4x increase over thr
Last week’s LeetCode contest, I hit a wall. A Hard DP problem. Forty-seven minutes of my life, gone. I submitted a solution that *technically* worked—then it ti
Honestly, I almost threw my keyboard out the window that night. December 11, 2024. 2 AM. I'm staring at a file called utils.py that's been haunting me for two y
Last Tuesday, I made a change that dropped our customer service bot's response time from 11.3 seconds to 0.9 seconds. My boss thought I'd rebuilt the entire arc
Last year I built an enterprise knowledge base Q&A system. During testing, the RAG accuracy was a miserable 67%. Users weren't gentle: "Why does your AI keep ma
You're going to think I'm exaggerating. I'm not. Last month, I built an entire e-commerce admin panel without writing a single line of SQL or calling a single A
Last year during Singles' Day (think Black Friday but bigger), our team's smart customer service system exploded. I mean literally three seconds past midnight
Last Wednesday at 2:47 AM, PagerDuty woke me up. The 43rd "JSON Parse Failed" alert. I squinted at the monitoring dashboard, and it suddenly hit me — we've been
Last December, I attended a rather unusual conference. Closed-door. About thirty AI founders crammed into a room. The organisers threw some numbers on screen th
Last Wednesday at 2 AM, my phone buzzed. PagerDuty. The kind of buzz that makes your stomach drop before you even look at the screen. Server CPU was pegged at 1
Last Wednesday, 3:12 PM. Our API aggregation platform went dark. For 47 minutes straight. The reason was embarrassingly stupid—one model provider's gpt-4-turbo-
Last Wednesday at 2 PM, we pushed our AI customer service system to production. I hadn't even settled into my chair when the messages started flooding in. Scree