JavaScript
🐞 Common Bug Pattern in API Calls Many developers have unintentionally written bugs like this (not exactly like the image 👇): Typical `try–catch` Example try { const res = await api.getUser() console.log('✅ User info', res) } catch (err) { console.error('❌ Request failed', err) } At first glance, this code
logging
Lao A's Code Teahouse Vol.1 — Logging: The “Small” Thing Most Programmers Get Wrong Hello everyone, I’m Lao A. --- A Holiday Wake-up Call During the National Day holiday, I was lazily sprawled on a beach chair, sipping a cold beer, enjoying the breeze — pure bliss. Suddenly,
Error Handling
Unified Exception Handling in Distributed Systems — Insights from Jenish Shah (Netflix) Jenish Shah, a back-end engineer specializing in distributed systems at Netflix, shares practical strategies for handling failures in heterogeneous microservice environments. His work led to the development of a shared library that standardizes exception handling across protocols like REST,
distributed systems
# Managing Failures in Distributed Systems: Insights from Jenish Shah (Netflix) Jenish Shah, a **back-end engineer** specializing in distributed systems at Netflix, shares deep insights into **failure management** in distributed architectures and his design of a **protocol-agnostic exception-handling library**. --- ## 📌 Key Takeaways - **Microservices ≠ Protocol Choice** - REST over HTTP is
Error Handling
# 错误处理方式比较：异常 vs 状态码 错误处理在不同语言中有不同策略。  - **JavaScript** 和 **Python** 通常使用 **抛出异常** - **Rust** 通过 `Result` 类型变相实现异常处理 - **C** 和 **Go** 语言通常 **返回错误值**，需要主动判断是否为 `-1` 或空值 我一直想知道，哪一种方式更好？ 前不久，我读到一篇多年前的 [文章](https://nedbatchelder.com/text/exceptions-vs-status.html)，作者 Ned