Skip to content
Shevinu's Digest
Back to archive

Shevinu's Digest — Friday, October 16, 2026

·5 items

Resilience and AI‑augmented tooling are shaping today’s backend craft.

🛠️ Systems Design & Reliability

  • When Software Meets Hardware

    martin_fowler·

    When software meets hardware, the core engineering principles stay the same, but the sensible defaults shift. Kuldeep Singh walks through modernizing a massive IoT fleet of battery‑powered sensors, showing how familiar patterns—like modularity, testing, and observability—still apply, yet must be tuned for low‑power, intermittent connectivity environments. The article chronicles a series of experiments, failures, and operational tweaks that replaced naïve assumptions with more realistic defaults, such as aggressive retry back‑off and edge‑side validation. For a backend architect, the piece offers concrete takeaways on adapting design thinking to hardware‑constrained contexts while preserving the rigor of software engineering.

  • How to Design for Failures

    bytebytego·

    Even the best‑written code can be undone by a power outage, a disk failure, or a network glitch. This guide adopts an "assume everything breaks" mindset and walks developers through a toolbox for building fault‑tolerant systems. It distinguishes between avoiding faults—through defensive coding and validation—and tolerating them via redundancy, graceful degradation, and retry strategies. Readers learn how to scope failures, limit blast radius, and design recovery pathways that keep services running while errors are being resolved. The article also covers metrics for measuring recovery time and reliability, giving engineers a practical framework to turn inevitable failures into manageable events.

  • RPKI now protects 70% of internet routes

    hacker_news·

    Resource Public Key Infrastructure (RPKI) has reached a new milestone: over 70 % of advertised internet routes now carry a valid Route Origin Authorization. The piece explains how RPKI works—network operators publish signed records that bind IP prefixes to the autonomous systems allowed to announce them—thereby reducing accidental or malicious hijacks. It highlights the jump from 54 % validity in September 2025 to 70 % in September 2026, a 30 % year‑over‑year gain, and breaks down the remaining gaps, such as ROAs that are too permissive or missing more‑specific routes. For backend engineers managing external dependencies or designing network‑aware services, the article underscores why RPKI adoption matters for a more secure and predictable internet.

🤖 AI Engineering & Tooling

  • The Pulse: new trend of building “internal vibe-coding apps” at tech companies

    pragmatic_engineer·

    At Ramp, a four‑person team built “Glass,” an internal “vibe‑coding” platform that lets engineers stitch together connectors to internal services and then prototype full‑stack apps in minutes. The article showcases a custom CRM built by a marketer, featuring 50 + fields and live filters, all assembled without writing a line of traditional code. Stripe’s counterpart, “Harbor,” is described as an AI‑assisted prototyping tool that similarly abstracts away boilerplate, letting teams focus on domain logic. For developers, the write‑up illustrates how internal developer portals can accelerate experimentation, reduce context‑switching, and democratize tooling across product groups.

📌 From the blogs you follow

  • Introducing B-TAP: Because Your AI Infrastructure Hasn’t Attributed Its Fair Share

    ken_walger·

    Observability systems watch the supervisors, and other systems watch the observability systems. We’re pleased to introduce the Bureau of Token Attribution and Provenance , or B-TAP , the first bureau of The Vernholt Secretariat and the one some of you will insist on calling the Token IRS no matter how many times we correct you. Our mandate is voluntary but sweeping: to harmonize the reporting of token costs across every model, agent, retrieval pipeline, and suspiciously autonomous llama, everywhere, forever. Context Tax is assessed when information must be carried through active model context. Every instruction, retrieved document, conversation turn, agent output, and piece of supporting material occupies finite context and incurs processing cost.

9 source error(s) this run — see the run's GitHub Actions log for detail.