jpalepu33

3 ms·

1. 1.▲
   by jpalepu33 8mo ago

   The title is misleading but the actual work is impressive - they optimized their Protobuf usage, not replaced it entirely. This is a common pattern: "We switched to X and got 5x faster" often really means "We fixed our terrib
2. 2.▲
   by jpalepu33 8mo ago

   The discussion around checked vs unchecked exceptions always comes down to ergonomics vs safety. Having worked extensively with Node.js (callback hell, then Promises), I appreciate how error-as-value patterns force you to think about failur
3. 3.▲
   by jpalepu33 8mo ago

   Great write-up on the evolution of your architecture. The progression from 200ms → 14ms is impressive. The lesson about "delete code to improve performance" resonates. I've been down similar paths where adding middleware&#x2F
4. 4.▲
   by jpalepu33 8mo ago

   This metaphor really captures the current state well. As someone building products with LLMs, the "you have to tell it where to turn" part resonates deeply. I've found that the key is treating AI like a junior developer who&#
5. 5.▲
   by jpalepu33 8mo ago

   This is a clear example of why building on proprietary APIs is risky for indie devs and small startups. I've seen similar patterns with Twitter's API restrictions and other platforms gradually closing down their ecosystems. For an