# system Published articles for system. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How Marathon Incidents Expose Organizational Fragility and Require Structured Incident Response DevFeed: [How Marathon Incidents Expose Organizational Fragility and Require Structured Incident Response]() Original publisher: [Read original article]() Author: Vanessa Huerta Granda Published: 2026-09-17T09:30:00Z Content type: article Language: en Sources: [InfoQ]() Topics: [incident](), [Incident response]() Tags: [devops](), [incident](), [incident-response](), [infoq](), [limits](), [organizational](), [outages](), [presentation](), [qcon-san-francisco-2026](), [qcon-software-development-conference](), [real-world](), [stream-incidents](), [structured](), [system](), [transcripts]() ### AI overview Vanessa Huerta Granda discusses how prolonged incidents reveal gaps between planned work and work as performed. Drawing on real-world scenarios, the presentation examines organizational fragility, human limits, system interdependencies, and the need for structured, humane, cross-functional incident response. ### Source excerpt Vanessa Huerta Granda explains how marathon incidents expose the gap between work as imagined and work as done. Drawing from real-world scenarios, she shares how complex outages reveal organizational fragility, human limits, and system interdependencies--and why incident response requires structured endurance, humane rotations, and holistic cross-functional coordination. By Vanessa Huerta Granda ## How to Identify Which Raspberry Pi Model You Have DevFeed: [How to Identify Which Raspberry Pi Model You Have]() Original publisher: [Read original article]() Author: Patrick Fromaget Published: 2026-09-17T02:25:39Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Raspberry Pi](), [Operating system](), [cpu](), [Wi-Fi]() Tags: [beginner-s-guides](), [cpu](), [how-to](), [install](), [raspberry-pi](), [specifications](), [system](), [wi-fi]() ### AI overview A practical guide to identifying which Raspberry Pi model you own. It covers physical markings, purchase records, system commands, model comparisons, and a flowchart, with examples including Raspberry Pi 1, Raspberry Pi 2, and Raspberry Pi Zero. ### Source excerpt You bought a Raspberry Pi a few months or years ago and have no idea what model you have. This is a problem because you'll need this information to order accessories or install a new operating system. No worries, I'll give you tips on how to find which one you have easily. Most Raspberry Pi... ## What N, N+1, 2N, and 2(N+1) Mean in a Data Center DevFeed: [What N, N+1, 2N, and 2(N+1) Mean in a Data Center]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-27T13:59:08Z Content type: tutorial Language: en Sources: [Justin Wilson (j2sw)]() Topics: [datacenter](), [data]() Tags: [2n-redundancy](), [capacity](), [colocation](), [components](), [cooling](), [data-center](), [data-center-power](), [equipment](), [internet-architecture](), [maintenance](), [n-plus-1-redundancy](), [network-operations](), [power-distribution](), [system](), [ups]() ### AI overview This article explains what data center redundancy ratings N, N+1, N+2, 2N, and 2(N+1) indicate about component capacity, failures, maintenance, cooling, and alternate paths. ### Source excerpt Have you ever looked at a data center marketing slick and wondered what N, N+1, 2N, and 2(N+1) actually mean? The main thing they tell you is how many components can fail before the system drops below the capacity needed to support the load. When I evaluate a data center, I want to know what ... Read more The post What N, N+1, 2N, and 2(N+1) Mean in a Data Center appeared first on Justin Wilson (j2sw). ## FreeBSD Foundation Intern Sourojeet Adhikari on Bringing ROCm to FreeBSD DevFeed: [FreeBSD Foundation Intern Sourojeet Adhikari on Bringing ROCm to FreeBSD]() Original publisher: [Read original article]() Author: Florine Kamdem Published: 2026-08-24T20:34:20Z Content type: article Language: en Sources: [FreeBSD Foundation]() Topics: [rocm](), [GPU](), [Computing](), [Open Source](), [Programming]() Tags: [blog](), [gpu](), [open-source](), [programming](), [rocm](), [system]() ### AI overview An interview with University of Waterloo student Sourojeet Adhikari about his FreeBSD Foundation internship and work to bring AMD's ROCm GPU computing platform to FreeBSD. It covers his path into open source, systems and GPU programming, and the challenges of the project. ### Source excerpt For University of Waterloo student Sourojeet Adhikari, an early interest in understanding how computers work eventually grew into a summer spent helping bring AMD's ROCm GPU computing platform to FreeBSD. Sourojeet is studying Mathematical Physics and entering the third year of his degree. This summer, he joined the FreeBSD Foundation as an intern, working on [...] The post FreeBSD Foundation Intern Sourojeet Adhikari on Bringing ROCm to FreeBSD first appeared on FreeBSD Foundation. ## Alta labs: AP7-Pro 3.0i and AP6 2.4j Released DevFeed: [Alta labs: AP7-Pro 3.0i and AP6 2.4j Released]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-08T02:41:16Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [releases](), [Release notes]() Tags: [alta](), [alta-labs](), [ap7-pro](), [compatibility](), [devices](), [firmware](), [identity](), [mesh](), [nas](), [network-engineering-resources](), [release](), [release-notes](), [reporting](), [system](), [wireless]() ### AI overview Alta Labs released AP7-Pro version 3.0i and AP6 version 2.4j. The updates improve WPA3 transition-mode compatibility, add NAS-IP-Address to RADIUS frames, address mesh and 802.1x identity reporting issues, and improve AP7-Pro system stability. ### Source excerpt https://forum.alta.inc/c/release-notes/13 The post Alta labs: AP7-Pro 3.0i and AP6 2.4j Released appeared first on Justin Wilson (j2sw). ## Mikrotik quietly adds features to the Winbox package updates DevFeed: [Mikrotik quietly adds features to the Winbox package updates]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-12T14:11:16Z Content type: news Language: en Sources: [Justin Wilson (j2sw)]() Topics: [MikroTik]() Tags: [features](), [mikrotik](), [network-engineering-resources](), [packages](), [rosv7](), [routeros](), [system](), [updates](), [updating]() ### AI overview MikroTik has added new features related to updating system packages in Winbox. The article provides few details and says more information will follow. ### Source excerpt Mikrotik has added some new features to system...packages as far as updating goes. More info to come soon. The post Mikrotik quietly adds features to the Winbox package updates appeared first on Justin Wilson (j2sw). ## Managing an Engineer's Week as a Queueing System DevFeed: [Managing an Engineer's Week as a Queueing System]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-03-15T00:00:00Z Content type: opinion Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [queueing theory](), [scheduling](), [systems](), [Server]() Tags: [email](), [focus](), [minutes](), [notifications](), [productivity](), [queueing-theory](), [scheduling](), [servers](), [slack](), [software-engineering](), [system](), [time-management](), [work]() ### AI overview The article argues that software engineers' schedules behave like queueing systems: near-total utilization increases waiting time, while interruptions evict working context. It recommends maintaining schedule headroom, batching communications, and limiting work in progress. ### Source excerpt An engineer's week behaves like a queueing system: book yourself at 100% utilization and the wait time for anything new goes vertical, exactly as it does for a server. The fixes are the ones we already use in systems: keep headroom, coalesce interrupts instead of taking them one by one, cap work in progress because Little's law applies to you, and stop letting urgent-but-small tasks hold the lock while important work starves. ## Building AI agents that overcome the complexity cliff DevFeed: [Building AI agents that overcome the complexity cliff]() Original publisher: [Read original article]() Author: Ethan Ruhe Published: 2026-03-10T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [AI Agent](), [systems](), [Framework](), [Artificial Intelligence]() Tags: [agents](), [ai](), [building](), [challenges](), [complexity](), [infrastructure](), [system](), [system-design](), [temporal-voices]() ### AI overview This article presents a framework for understanding how AI agent capability grows with execution time and the number of tools and systems an agent can use. It argues that greater capability also increases the likelihood of failures and slows iteration, creating a "complexity cliff" where conventional frameworks may break down and Durable Execution becomes necessary. ### Source excerpt A principled framework for assessing agent capability -- why advanced agents need different infrastructure. ## What It Actually Takes to Build a Data Pipeline System DevFeed: [What It Actually Takes to Build a Data Pipeline System]() Original publisher: [Read original article]() Author: SeattleDataGuy Published: 2026-01-14T17:59:10Z Content type: article Language: en Sources: [SeattleDataGuy's Newsletter]() Topics: [data]() Tags: [building](), [components](), [data](), [data-pipeline](), [pipeline](), [system]() ### AI overview The article breaks down the components, tradeoffs, and practical realities of building your own data pipeline system. ### Source excerpt A breakdown of the components, tradeoffs, and realities of building your own data pipeline system ## Mmap effects in databases DevFeed: [Mmap effects in databases]() Original publisher: [Read original article]() Published: 2025-04-22T00:00:00Z Content type: article Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Database](), [Operating system](), [data](), [systems](), [file](), [memory pool]() Tags: [database](), [file](), [memory](), [mmap](), [operating-systems](), [performance](), [system]() ### AI overview This article explains how databases use operating-system storage and memory mechanisms, including buffered writes, storage blocks, database pages, and memory mapping, and discusses their effects on performance and data resiliency. ### Source excerpt . [mmap Effects in Databases](mmap-effects-in-databases-cover... ## Reduce latency and speed up your Temporal Workflows DevFeed: [Reduce latency and speed up your Temporal Workflows]() Original publisher: [Read original article]() Author: Joshua Smith Published: 2025-02-12T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [Latency](), [reliability](), [systems](), [Cloud](), [Network](), [Server](), [Transactions]() Tags: [cloud](), [durability](), [e-commerce](), [latency](), [measuring](), [optimizing](), [payment](), [problems](), [reduce](), [speed](), [system](), [techniques](), [temporal-concepts](), [workflows]() ### AI overview This tutorial explains how to reduce latency in Temporal workflows used by interactive applications while preserving durability and reliability. It identifies workflow startup, task scheduling, network calls, and activity execution as contributors to response time. ### Source excerpt Latency can be a challenge when responsiveness matters. The good news is, there are ways to make your workflows snappier without sacrificing durability. ## Part 3: Processing Payments - Ethereum Payment DevFeed: [Part 3: Processing Payments - Ethereum Payment]() Original publisher: [Read original article]() Author: Emmanuel Goossaert Published: 2022-11-29T19:18:12Z Content type: tutorial Language: en Sources: [Code Capsule]() Topics: [Ethereum](), [Blockchain](), [web applications](), [API]() Tags: [algorithms-and-programming](), [algorithms-and-programming-blockchain-crypto-ethereum-mongodb-nodejs-payment-system-typescri](), [api](), [blockchain](), [crypto](), [ethereum](), [mongodb](), [nodejs](), [payment](), [processing](), [system](), [typescript](), [web](), [web3]() ### AI overview A tutorial walkthrough of processing and validating payments from a web application on the Ethereum blockchain. It covers server-side prevalidation, submitting purchase transactions, tracking transaction status through polling, and handling successful or failed payments. ### Source excerpt A walkthrough of the steps needed to process and validate payments from a web application on the Ethereum blockchain. The post Part 3: Processing Payments - Ethereum Payment first appeared on Code Capsule. ## Maxim Fateev and Samar Abbas Discuss Temporal on Gremlin's Podcast DevFeed: [Maxim Fateev and Samar Abbas Discuss Temporal on Gremlin's Podcast]() Original publisher: [Read original article]() Author: Shawn Wang Published: 2021-10-07T07:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [Chaos Engineering](), [reliability](), [Open Source](), [Cloud]() Tags: [chaos-engineering](), [community](), [engineering](), [gremlin](), [open-source](), [podcast](), [reliability](), [system](), [time]() ### AI overview Temporal co-founders Maxim Fateev and Samar Abbas discuss Temporal's origins in Cadence at Uber, the decision to create a separate company, open-source adoption, cloud hosting, technical debt, and reliability requirements in an interview on Gremlin's podcast. ### Source excerpt Our co-founders Maxim Fateev and Samar Abbas recently joined Gremlin's podcast Break Things on Purpose for a rare double appearance to talk Temporal. Listen to it here! ## Stochastic Systems, Fokker-Planck and the Heat Equation via Haskell DevFeed: [Stochastic Systems, Fokker-Planck and the Heat Equation via Haskell]() Original publisher: [Read original article]() Author: Dominic Steinitz Published: 2020-04-26T14:20:10Z Content type: tutorial Language: en Sources: [Maths, Stats & Functional Programming]() Topics: [systems](), [Haskell](), [Library](), [C]() Tags: [c](), [example](), [examples](), [haskell](), [library](), [numerical-methods](), [numerics](), [partial-differential-equations](), [source](), [system](), [systems](), [using](), [with]() ### AI overview A short Haskell example models a stochastic system with the Fokker-Planck method, converts it to a partial differential equation, and solves a two-dimensional equation using SUNDIALS through the hmatrix-sundials library. The example is based on C examples included with the SUNDIALS source. ### Source excerpt This is a short example of taking a stochastic system, using Fokker-Planck to convert it to a PDES and using SUNDIALS to solve a 2D partial differential equation in Haskell via the hmatrix-sundials library. The example is taken from the C examples that come with the SUNDIALS source. Here's the full blog. ## NTSB on Uber (Preliminary) DevFeed: [NTSB on Uber (Preliminary)]() Original publisher: [Read original article]() Author: Adam Published: 2018-05-25T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [systems](), [Algorithms, Complexity]() Tags: [report](), [screen](), [self-driving](), [system](), [systems]() ### AI overview A preliminary NTSB report on Uber's self-driving car fatality found that the vehicle detected the need to brake with enough time to stop automatically, but automatic braking had been disabled. The article also raises questions about preserving relevant computer-system data and algorithms. ### Source excerpt [no description provided] ## Some notes about Skytools3 DevFeed: [Some notes about Skytools3]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2011-04-11T09:30:00Z Content type: article Language: en Sources: [Dimitri Fontaine]() Topics: [PostgreSQL](), [configuration](), [Server]() Tags: [documentation](), [packaging](), [production](), [release](), [separate](), [services](), [system]() ### AI overview The article discusses packaging Skytools3, including separating its daemons and subprojects into installable components for PostgreSQL environments. It describes service users, configuration files, startup and shutdown integration, logging defaults, and planned documentation work before a public release. ### Source excerpt I've been working on skytools3 packaging lately. I've been pushing quite a lot of work into it, in order to have exactly what I needed out of the box, after some 3 years of production and experiences with the products. Plural, yes, because even if pgbouncer and plproxy are siblings to the projets (same developers team, separate life cycle and releases), then skytools still includes several sub-projects. Here's what the skytools3 packaging is going to look like: