How many valid JSON strings exist? Discover the surprising answer in our latest blog post.

New JSON attachments let you log arbitrarily large or nested JSON, beyond any trace limits. Use them for long conversation transcripts, doc collections, embeddings, and more. Learn more: https://lnkd.in/gV6-E_gW

🍦 @fizzwiz/vanilla v0.0.0-dev.1 is out! Lightweight semantics for plain JSON objects — perfect for distributed objects & async workflows. ✨ Includes: OptionStore (type-based options) ObjNavigator (safe nested editing) 🧠 Learn more → https://lnkd.in/enqK3rJv 📦 npm → https://lnkd.in/eqg6EvCy “Keep it plain, keep it structured.”  — `@fizzwiz` ✨`

JSON Pointer is a tiny standard that solves a huge problem: how to reference exactly one value inside any JSON document using a short, stable string like /users/3/email. Read more on: https://lnkd.in/dJPB_MRr

Does MoreLINQ Zip Outperform LINQ Zip? Let's Benchmark Them! A duel between two methods for zipping collections in CSharp! But a challenger approaches: Our very own naive implementation of LINQ Zip! In this video, I'll walk through the BenchmarkDotNet benchmarks for comparing the LINQ zip method and MoreLINQ ZipShortest and ZipLongest methods. We'll even see how my naive implementation does against these! Buckle up and get ready to see how optimized my code is! Spoiler Alert: It's not. More Spoiler Alert: You'll still be surprised. Watch here: https://lnkd.in/gY4nmEbe

The Sourcemeta "Learn JSON Schema" site _finally_ features FULL documentation, examples, best practices, anti-patterns, etc for JSON Schema 2019-09! For context, we only had full documentation for 2020-12, and other dialects only had a basic outline. But that's changing this week! We'll aim to get them ALL properly documented. Better late than never 😅 See https://lnkd.in/d4AcUzSQ

Struggling with slow updates in your Apache Iceberg 🧊 tables? When dimensions change too fast, Iceberg writers can face chilly performance bottlenecks. What if there was another way you could write Iceberg tables with blistering throughput, no compromises? Read our latest engineering blog to learn how your Iceberg tables can leverage techniques that standard OSS might not get even by the v6 spec 😉. 👉 https://lnkd.in/gS5nPPai #ApacheIceberg #ApacheXTable #ApacheHudi #DataLakehouse

Pro tip: Use Nuclei's JSON extractor with jq syntax to effortlessly pull data from JSON responses. Check out this Nuclei cheat sheet, including more information on extractors: https://lnkd.in/gKZwQYES

The other day, I was working with a table containing thousands of records. I paused for a moment, asking myself: 👉 Should I DELETE the records or DROP the table entirely? It’s a small decision that can have a big impact on system performance and memory usage. DELETE removes data but keeps the table structure. It is good when you plan to reuse it. DROP completely removes the table. It frees up space but also erases the structure. Understanding how each command affects storage, indexes, and memory helps us write more efficient, resource-conscious code. Being efficient isn’t just about logic — it’s about making every query count. Here, truncate came to my mind, which I will discuss in the next post 😊

Are you looking for examples of bug bounties? We’ll explain what bug bounties are and show you how they work step-by-step using actual examples. https://lnkd.in/dPYhBCwn

Okay, TS fans... we need to talk. Can we just just agree to stop acting like `exactOptionalPropertyTypes` isn't a thing? Like, even some (most?) of the TS ecosystem's most popular libraries that are "ZOMG SO TYPE-SAFE" just completely break when you turn on the compiler option... which shows the library authors themselves didn't even turn it on. If you're wondering why it's actually a big deal, tell me this: What is the type returned by the `merge` function below? ```typescript type First = { one: string; two?: string | undefined }; type Second = { one?: string | undefined; two: string }; function merge(first: First, second: Second) {   return { ...first, ...second } } ``` Thank goodness Zod finally supports this distinction at the parser level. Now if we can just convince people to care... Matt Pocock, get behind me!