<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress.com" -->
<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"
	xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
	xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
	xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
	>
<url><loc>https://pdawg.blog/2026/05/06/the-three-words-every-backend-engineer-should-tattoo-on-their-forearm/</loc><news:news><news:publication><news:name>Pdawg</news:name><news:language>en</news:language></news:publication><news:publication_date>2026-05-06T03:54:21+00:00</news:publication_date><news:title>The Three Words Every Backend Engineer Should Tattoo on Their Forearm</news:title><news:keywords>Computer Science, book summary, software architecture, software design, distributed systems, designing data intensive applications, martin kleppmann, reliability, backend engineering, technical debt, tail latency, percentiles, programming books, scalability, database design, web development, chapter summary, maintainability, ddia, fault tolerance, data engineering, engineering culture, system design, book notes, tech books</news:keywords></news:news></url></urlset>