1,742
1,740
1,7371,7371,7361,7361,736495495
435431314314
1884d ago · 7 min read · You've got a 200-line JSON response. You need the email of every user whose lastLogin is older than 30 days, but only from the team department, sorted by id. You start writing a .filter().map() chain and twenty minutes later you're debugging an undef...
Join discussionApr 21 · 3 min read · JSON.stringify() looks simple. You pass it an object, you get a string back. But there are a handful of behaviors that catch people off guard, usually when the data you thought you were logging just shows up as {} or a field goes missing from a POST ...
Join discussionApr 21 · 3 min read · If you have ever had to pull a specific value from a deeply nested API response, you have probably written something like this: const city = response.user.address.city; // works fine, until user.address is undefined Or a chain of map and filter call...
Join discussionApr 21 · 6 min read · You call JSON.parse() and get a SyntaxError. The message says Unexpected token < at position 0. The JSON is coming from an API. Position 0 means the very first character is wrong. Most of the time, it is not your JSON at all. It's an HTML error page....
Join discussionApr 17 · 7 min read · Sometimes I want to examine in detail a JSON document that is stored in the database. I just want an overview of all the fields in the document, possibly with their values. The JSON document itself ca
Join discussion
Apr 17 · 10 min read · Source: Ways to Handle Schema Evolution Safely in Production Systems The first time a seemingly tiny schema change caused an outage in my team, it wasn't because the change was technically hard — it was because we had focused only on the "happy pat...
Join discussion
Apr 13 · 11 min read · Here's a class of bug I wrote in my first LLM app and then again, on a different team, six months later. I wrote a feature that asked the model to classify a user's message into one of three categories — billing, technical, other — and return it as J...
Join discussion
