--- product_id: 273602706 title: "Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones)" brand: "marriane bellotti" price: "€ 34.86" currency: EUR in_stock: true reviews_count: 8 url: https://www.desertcart.at/products/273602706-kill-it-with-fire-managing-aging-computer-systems-and-future store_origin: AT region: Austria --- # Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones) **Brand:** marriane bellotti **Price:** € 34.86 **Availability:** ✅ In Stock ## Quick Answers - **What is this?** Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones) by marriane bellotti - **How much does it cost?** € 34.86 with free shipping - **Is it available?** Yes, in stock and ready to ship - **Where can I buy it?** [www.desertcart.at](https://www.desertcart.at/products/273602706-kill-it-with-fire-managing-aging-computer-systems-and-future) ## Best For - marriane bellotti enthusiasts ## Why This Product - Trusted marriane bellotti brand quality - Free international shipping included - Worldwide delivery with tracking - 15-day hassle-free returns ## Description Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones) ## Images ![Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones) - Image 1](https://m.media-amazon.com/images/I/71jHKKH4p9L.jpg) ## Customer Reviews ### ⭐⭐⭐⭐ 4.0 out of 5 stars A refreshing take on age-old issues *by P***L on Reviewed in the United Kingdom on 3 July 2024* A good read with relevant case studies. Food for thought for any systems developer or architect. ### ⭐⭐⭐⭐ 4.0 out of 5 stars Rewriting the code is almost never the right answer. *by P***T on Reviewed in the United Kingdom on 6 December 2021* About a third of the book is about management and doing repair/rewrite inside large organisations, but nearly half of it is directly relevant to maintaining long-lived science and voluntary data management projects:Consider iteration in place as the default approach.Beware of artificial consistency as proposed to "improve" technical value.Don't assume that what you can't see is simple to replace: there may be years of effort hiding considerable complexity which appears simple on the surface.Previous modernization efforts may have left behind serious scar tissue which you need to consider.Many people try to fix things which are not, in fact, broken. Don't optimise beyond diminishing returns.Modernization needs momentum to finish the job: don't take on risks without also producing compelling value.Decisions made to avoid rewriting the new code later are usually bad decisions.The only thing worse than attempting to fix the wrong thing is leaving the fix attempt unfinished.Site reliability expressed as uptime percentages is rarely the real issue.Speed of recovery after failure is always more important than you think.A perfect record of no failures can always be broken, but resilience is an accomplishment that lasts.Know when to run a systemic Code Yellow hackathon and when not to.Always discover why previous modernisations failed first.Spend a lot of time problem setting before you start to think about problem solving.Working through a major modernisation is all about managing scope.Code is much easier to write than it is to read. Modernisaton means a lot of code reading.Human beings are absolutely terrible at estimating probabilities and risk. We always under-estimate the amount of work in a rewrite and over-estimate the likelihood of success.Success does not come all at once. What are the progressive success criteria during the reengineering?Use Diagnosis, Policy, Actions where there is little consensus about what success looks like.Use bullet journalling to maintain your own morale during a re-engineering project.When a failure is user input, fail gracefully with helpful message.When a failure is due to a programming or specification bug, fail hard and fast.Build simple, performant systems before you start on the bells and whistles.Prioritise simple code running fast early, so that you can iterate fast.An existing system is not a reliable specification for the proposed new system. Important behaviour will be implicit, not documented. ### ⭐⭐⭐ 3.0 out of 5 stars Abstract ideas *by O***R on Reviewed in the United Kingdom on 6 August 2023* I think there’s a lot of wisdom behind these ideas but as a manager and tech lead of small team in a small company (< 50) I found these ideas too abstract. ## Frequently Bought Together - Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones) - Staff Engineer: Leadership beyond the management track - The Software Engineer's Guidebook: Navigating senior, tech lead, and staff engineer positions at tech companies and startups --- ## Why Shop on Desertcart? - 🛒 **Trusted by 1.3+ Million Shoppers** — Serving international shoppers since 2016 - 🌍 **Shop Globally** — Access 737+ million products across 21 categories - 💰 **No Hidden Fees** — All customs, duties, and taxes included in the price - 🔄 **15-Day Free Returns** — Hassle-free returns (30 days for PRO members) - 🔒 **Secure Payments** — Trusted payment options with buyer protection - ⭐ **TrustPilot Rated 4.5/5** — Based on 8,000+ happy customer reviews **Shop now:** [https://www.desertcart.at/products/273602706-kill-it-with-fire-managing-aging-computer-systems-and-future](https://www.desertcart.at/products/273602706-kill-it-with-fire-managing-aging-computer-systems-and-future) --- *Product available on Desertcart Austria* *Store origin: AT* *Last updated: 2026-06-03*