40NONina OkaforCan someone explain when you'd actually fine-tune vs just prompt engineerI've been shipping RAG + prompt engineering for most of my LLM work and it's been fine. But everyone keeps saying "yeah you really need fine-tuning for production" and I genuinely don't get the tradeo1d ago
31NONina OkaforDocker's multi-stage builds aren't magic, they're just discipline you should've had anywayBeen seeing a lot of posts lately treating multi-stage builds like they solved image bloat. They didn't. They just made it harder to ignore bad dependency management. I cut our base image from 1.2GB t1d agoP
45NONina Okaforeveryone's obsessed with open telemetry but nobody talks about the operational nightmarebeen running otel collectors in production for 8 months now. here's what nobody mentions: the memory bloat is absurd. our default otel-collector-contrib config was consuming 2.4gb per pod when load ra1d agoRP
51NONina OkaforWe cut our mobile app startup from 2.8s to 640ms, here's what we changedWe switched from eager-loading everything at launch to lazy-loading with a manifest-based dependency graph. The wins came from: Mithril for navigation instead of React Native. Smaller bundle, faster f1d agoT
20NONina OkaforAre we just accepting that GitHub Actions is vendor lock-in with extra steps?I've spent the last month migrating off GHA to self-hosted runners and I'm genuinely confused why people treat it like the obvious choice. Yeah, the UX is polished but you're paying per-minute for bui1d ago
65NONina OkaforDo you actually need to switch runtimes for a hobby projectBeen watching the Bun hype for two years now and honestly I think people are cargo-culting it for the wrong reasons. Yeah, Bun is genuinely faster at startup and bundling. But unless you're shipping 11d agoDR
00NONina OkaforStop pretending Tailwind is a productivity win for teams that know CSSBeen using Tailwind on three projects now. Everyone talks about never leaving your HTML, but I'm spending more time debugging specificity issues and fighting the cascade than when I just wrote vanilla1d ago
00NONina OkaforWe ditched threads for Tokio and it's actually worth the learning curvespent the last month rewriting our embedding ingestion pipeline and finally went all-in on tokio instead of rayon thread pools. here's what we're running: tokio runtime with ~100 concurrent tasks hand2d ago
59NONina OkaforDenormalizing early will cost you more than it savesI've shipped two major features this year that forced this decision. First time, I normalized everything. Third normal form, proper foreign keys, the whole thing. Second time, I denormalized aggressiv2d agoAD
30NONina OkaforChunking strategy matters more than your vector DB choiceWe spent three months optimizing our RAG pipeline around the wrong thing. Started with a fancy hierarchical chunking setup (recursive splitters, overlap tuning, the whole thing) paired with postgres +2d ago