--- title: "Daniel Posing (@danposing) | Hashnode" description: "Most systems work great, until they meet real-world data. I work on everything that happens after that. Read the latest articles by Daniel Posing on Hashnode." url: "https://hashnode.com/@danposing" --- @danposing # Daniel Posing @danposing · Joined May 2026 Most systems work great, until they meet real-world data. I work on everything that happens after that. ### [Surviving Schema Drift in Immutable Search Indices (Unhappy Paths #4)](https://danielposing.hashnode.dev/surviving-schema-drift-in-immutable-search-indices-unhappy-paths-4?utm_source=hashnode&utm_medium=feed) We added a text field. Then data started silently vanishing every day. We often focus on the dramatic technical failures—the server crashes, the migrations, the complex race conditions. But some of th 5 min read · [danielposing.hashnode.dev](https://danielposing.hashnode.dev/surviving-schema-drift-in-immutable-search-indices-unhappy-paths-4?utm_source=hashnode&utm_medium=feed) [Jul 22](https://hashnode.com/posts/surviving-schema-drift-in-immutable-search-indices-unhappy-paths-4/6a6044ce1e42ecb7e062b31a) ### [Tracing Lost Updates in Distributed Search Layers (Unhappy Paths #3)](https://danielposing.hashnode.dev/tracing-lost-updates-in-distributed-search-layers-unhappy-paths-3?utm_source=hashnode&utm_medium=feed) A silent data failure, a textbook Read-Modify-Write race condition, and the cost of concurrent updates without optimistic locking. 5 min read · [danielposing.hashnode.dev](https://danielposing.hashnode.dev/tracing-lost-updates-in-distributed-search-layers-unhappy-paths-3?utm_source=hashnode&utm_medium=feed) [Jul 13](https://hashnode.com/posts/tracing-lost-updates-in-distributed-search-layers-unhappy-paths-3/6a546b2fbcc093c1c667abe8) ### [Orchestrating Reliability through Verification Proxies (Unhappy Paths #2)](https://danielposing.hashnode.dev/orchestrating-reliability-through-verification-proxies-unhappy-paths-2?utm_source=hashnode&utm_medium=feed) How a strict attribute limit turned a routine migration into a P0. Solving Read-Modify-Write race conditions with Python and verification proxies. 6 min read · [danielposing.hashnode.dev](https://danielposing.hashnode.dev/orchestrating-reliability-through-verification-proxies-unhappy-paths-2?utm_source=hashnode&utm_medium=feed) [1](https://hashnode.com/posts/orchestrating-reliability-through-verification-proxies-unhappy-paths-2/6a0a90b93104e2aff00f67cf) [May 18](https://hashnode.com/posts/orchestrating-reliability-through-verification-proxies-unhappy-paths-2/6a0a90b93104e2aff00f67cf) ### [When “Working Encryption” Isn’t Enough (Unhappy Paths #1)](https://danielposing.hashnode.dev/when-working-encryption-isn-t-enough-unhappy-paths-1?utm_source=hashnode&utm_medium=feed) A P0 incident, a broken integrity check, and the tradeoff between security and delivery. 8 min read · [danielposing.hashnode.dev](https://danielposing.hashnode.dev/when-working-encryption-isn-t-enough-unhappy-paths-1?utm_source=hashnode&utm_medium=feed) [May 2](https://hashnode.com/posts/when-working-encryption-isn-t-enough-unhappy-paths-1/69f54853ec32cba9e589e50e)