Deep dives into tools,
techniques & the web.
Practical guides covering developer tools, health metrics, SEO, converters and more — written to be actually useful.
✦ AI-powered — understands natural language
Word Boundaries and Lookarounds: Precise Find & Replace
Zero-Width Characters Are Used to Watermark Leaked Documents and Bypass Spam Filters — Here's the Full Invisible Unicode Taxonomy
Zero-width spaces and zero-width non-joiners are used to watermark confidential documents — each recipient gets a unique binary pattern embedded invisibly, allowing leaks to be traced back to the specific recipient. Here's the full taxonomy of invisible Unicode characters (U+200B zero-width space, U+00A0 non-breaking space, directional controls), why Python's str.strip() doesn't remove non-breaking spaces, and how invisible characters are used to bypass content filters by breaking exact-match pattern recognition.
Why Kidney Stone Patients Should Not Restrict Calcium — Stone Formation Chemistry, Urine Concentration, and the 2-Litre Target
Approximately 50% of kidney stone patients have a recurrence within 5 years — and inadequate hydration is the single most modifiable risk factor, because concentrated urine allows crystals to nucleate before being flushed out. Here's the stone formation chemistry for each type (calcium oxalate, uric acid, struvite, cystine), why restricting dietary calcium actually increases oxalate stone risk, why 2 litres of urine output requires approximately 3 litres of fluid intake, and why lemon juice increases urinary citrate as a validated dietary intervention.
Two Strings Can Both Be Valid ISO 8601 and Still Be Unparseable by Each Other's Parsers — And the Y2038 Problem Isn't Solved Yet
ISO 8601 permits basic format (no hyphens: 20240315T143000), week dates, and comma as decimal separator — all valid by the standard, all rejected by most "ISO 8601 parsers" that actually implement the stricter RFC 3339 profile. Here's the Y2038 problem's remaining affected systems (32-bit embedded firmware, MySQL TIMESTAMP type), why PostgreSQL's "TIMESTAMP WITH TIME ZONE" doesn't store the timezone, and the precision mismatch that causes events within the same millisecond to appear simultaneous in the UI but distinguishable in the database.
Hierarchical vs Flat URL Structure, Taxonomy Collisions, and Multilingual Slug Design — The Slug Decisions That Last Forever
Slug architecture for content series, taxonomies, and multilingual sites involves permanent commitments — a slug embedded in inbound links can never be silently changed. Here's the hierarchical vs flat URL structure trade-off (hierarchy embeds category in URL, making recategorisation cost real), how category/tag slug collisions form when the same term appears in both taxonomies, author slug edge cases at scale (departures, pen names, duplicates), and why path-prefix multilingual URL structure beats subdomains for authority consolidation.
Microsoft Lost hotmail.co.uk and DHS Lost a Federal Domain — What WHOIS Reveals About Domain Expiry Risk and How Squatters Catch Dropped Domains
Microsoft lost hotmail.co.uk in 2003, the UK Parliament's mobile site was squatted in 2011, and the US Department of Homeland Security briefly lost a domain in 2023 — not from hacking, but from failed renewal monitoring. Here's the EPP domain status code sequence from expiry to pendingDelete, how drop-catching services time registrations to the second, what WHOIS still reveals after GDPR contact redaction (expiry dates, nameservers, DNSSEC status), and why registrar reminder emails go to departed employees' inboxes.
The Database That Runs Every Clock in Every App Almost Went Away in 2011 — The IANA Timezone Database Story
The IANA Time Zone Database — the source of timezone rules for Linux, macOS, Python, Java, and essentially every software platform — was briefly taken offline in 2011 due to a copyright lawsuit, creating a crisis for global software infrastructure. Here's how Samoa skipped an entire calendar day in December 2011, why Egypt and Morocco changed their DST rules with days of notice, the correct UTC-first database storage pattern, and why "UTC+1" is the wrong way to store a timezone.
CSS text-overflow: ellipsis Doesn't Remove Text — The Four Truncation Layers and MySQL's Silent Data Loss Bug
CSS text-overflow: ellipsis hides text from view but leaves it in the DOM — search engines index it, screen readers may announce it, and Find in Page finds it. That's correct for display truncation but completely wrong for data-level truncation. Here's the four truncation layers (CSS, JavaScript, API, database) and when each is correct, MySQL's silent truncation that discards characters without error in default mode, and why meta description truncation should use word boundaries rather than character counts.
The Obesity Paradox: Why the BMI Mortality Curve Is U-Shaped
Some large studies find the lowest mortality in the "overweight" BMI band. The explanation is mostly confounding and reverse causation — here's how to read those findings.
Why GCLID and UTM Parameters Fight Over Attribution in GA4 — and Why "Google" vs "google" Permanently Splits Your Analytics
GCLID (Google Ads click ID) and UTM parameters both try to solve attribution but using different mechanisms — and when both appear in the same URL, GA4 may prefer the GCLID-based auto-tagging over manual UTM values, making cross-platform reporting inconsistent. Here's why UTM capitalisation ("google" vs "Google") permanently fragments your analytics into separate traffic sources, why UTM parameters on internal links overwrite the original traffic source, and why UTM-tagged URLs need canonical tags to avoid duplicate content indexing.
UTC Is 37 Seconds Behind Atomic Time — Why Leap Seconds Exist, Why They Crash Software, and What Replaces Them After 2035
UTC and International Atomic Time (TAI) diverge by 37 seconds because Earth's rotation is slowing — atomic clocks keep perfect SI seconds, but solar noon would drift without periodic leap seconds inserted into UTC. Here's why the June 2012 leap second caused Reddit, Mozilla, and LinkedIn to go offline (a Linux kernel hrtimer bug), why GPS time is 18 seconds ahead of UTC, and why MiFID II's microsecond timestamp requirements create audit trail ambiguities around leap second boundaries.
Reversing Text Is Harder Than It Looks — Unicode Bidirectional Algorithm, Grapheme Clusters, and the Trojan Source Attack
Reversing Arabic text character-by-character produces nonsensical output — Arabic is stored in logical reading order and reversed by a rendering engine, so reversing code points produces different words backward, not mirrored text. Here's how Unicode's bidirectional algorithm assigns direction to each character, why emoji sequences need grapheme cluster reversal rather than code-point reversal, and how the Trojan Source vulnerability exploited RLO (Right-to-Left Override) control characters to hide malicious code in source file reviews.
Why Git Diff Shows the Same Change Differently Than Other Tools — Myers Algorithm, Patience Diff, and Semantic Diffing
The Myers diff algorithm (used by git diff) finds the minimum edit sequence with fewest edit groups — not just minimum edits — because multiple minimum-edit solutions exist and some are far more readable than others. Here's why patience diff wins for code by anchoring on unique lines first, how AST-based semantic diffing represents a renamed variable as one change instead of N lines, and why diff3 merge conflict markers (showing the common ancestor alongside both conflicting versions) make conflicts easier to resolve.
