Meta tags:
description=As part of my work on #eng-strategy-book, I’ve been editing a bunch of stuff. This morning I wanted to work on two editing problems. First, I wanted to ensure I was referencing strategies evenly across chapters (and not relying too heavily on any given strategy). Second, I wanted to make sure I was making references to other chapters in a consistent, standardized way. Both of these are collecting Markdown links from files, grouping those links by either file or url, and then outputting the grouped content in a useful way. I decided to experiment with writing a one-shot prompt to write the script for me rather than writing it myself. The prompt and output (from ChatGPT 4.5) are available in this gist.;

Headings (most frequently used words):

script, for, consistent, linking, within, book,

Text of the page (most frequently used words):
the (20), and (10), #script (8), for (7), strategy (7), book (7), this (7), but (6), writing (5), are (5), strategies (5), links (5), was (5), output (5), engineering (4), than (4), chapters (4), content (4), rss (3), newsletter (3), will (3), management (3), also (3), from (3), you (3), get (3), that (3), bit (3), had (3), less (3), hand (3), one (3), references (3), editing (3), grouped (3), either (3), way (3), prompt (3), wanted (3), consistent (3), about (2), tags (2), larson (2), stuff (2), written (2), leadership (2), make (2), rather (2), eng (2), heavy (2), popular (2), staff (2), engineer (2), here (2), frequently (2), too (2), heavily (2), stories (2), other (2), two (2), can (2), which (2), first (2), have (2), minutes (2), write (2), with (2), example (2), scripts (2), posts (2), sure (2), been (2), chatgpt (2), these (2), work (2), linking (2), within (2), irrational (2), exuberance (2), 2026, digital, gardening, exuberant, sketches, haven, yet, hopefully, someday, 2022, platforms, change, cool, uris, don, plagarism, idea, theft, online, readme, contribution, reliability, programs, related, revised, rules, assumptions, generated, suppressed, demand, middle, roles, trap, roadmap, decisions, dates, recent, how, create, software, quality, org, seniority, mix, model, moving, orchestration, role, good, fad, building, internal, agents, like, updates, weekly, emails, follow, feed, subscribe, wrote, crafting, executive, primer, elegant, puzzle, books, looking, reach, out, ways, help, folks, natural, referenced, existing, more, unwritten, over, course, drafting, makes, feel, lopsided, when, read, has, helped, address, imbalance, something, didn, wish, ended, leaning, early, mentioned, later, stripe, sorbet, only, three, because, last, finished, quite, helpful, solving, intended, problem, imbalanced, see, initially, uber, migration, documented, altogether, super, simple, could, thirty, allowed, ten, back, actually, remaining, twenty, now, call, standard, mode, worked, correctly, ugly, tweaked, slightly, adjusted, regular, expression, capture, preceding, resulted, although, did, would, faster, just, ask, fix, itself, very, minor, tweaks, both, collecting, markdown, files, grouping, those, file, url, then, outputting, useful, decided, experiment, shot, myself, available, gist, part, bunch, morning, problems, ensure, referencing, evenly, across, not, relying, any, given, second, making, standardized, llm, published, april, 2025,

Text of the page (random words):
script for consistent linking within book irrational exuberance irrational exuberance popular tags newsletter rss about script for consistent linking within book published on april 6 2025 writing 42 llm prompt 1 as part of my work on eng strategy book i ve been editing a bunch of stuff this morning i wanted to work on two editing problems first i wanted to ensure i was referencing strategies evenly across chapters and not relying too heavily on any given strategy second i wanted to make sure i was making references to other chapters in a consistent standardized way both of these are collecting markdown links from files grouping those links by either file or url and then outputting the grouped content in a useful way i decided to experiment with writing a one shot prompt to write the script for me rather than writing it myself the prompt and output from chatgpt 4 5 are available in this gist that worked correctly the output was a bit ugly so i tweaked the output slightly by hand and also adjusted the regular expression to capture less preceding content which resulted in this script although i did it by hand i m sure it would have been faster to just ask chatgpt to fix the script itself but either way these are very minor tweaks now i can call the script in either standard or grouped mode example of scripts links py content posts strategy book md output example of scripts links py content posts strategy book md grouped output altogether this is a super simple script that i could have written in thirty minutes or so but this allowed me to write it in less than ten minutes and get back to actually editing with the remaining twenty it s also quite helpful for solving the intended problem of imbalanced references to strategies here you can see i initially had 17 references to the uber migration strategy which was one of the first strategies i documented for the book on the other hand the strategy for stripe s sorbet only had three links because it was one of the last two chapters i finished writing it s natural that i referenced existing strategies more frequently than unwritten strategies over the course of drafting chapters but it makes the book feel a bit lopsided when read and this script has helped me address the imbalance this is something i didn t do in staff engineer but wish i had as i ended up leaning a bit too heavily on early stories and mentioned later stories less frequently hi folks i m will larson if you re looking to reach out to me here are ways i help books i wrote an elegant puzzle staff engineer the engineering executive s primer and crafting engineering strategy newsletter if you d like to get get updates subscribe for weekly emails or follow my rss feed popular building internal agents good engineering management is a fad moving from an orchestration heavy to leadership heavy management role eng org seniority mix model how to create software quality recent roadmap decisions rather than dates middle management roles are also a trap generated and suppressed demand make no assumptions revised rules of engineering leadership related readme contribution on reliability programs plagarism idea theft and writing online platforms change but cool uris don t stuff i haven t written yet but hopefully will someday 2022 digital gardening at exuberant sketches will larson 2026 tags newsletter rss about

Images from subpage: "lethain.com/middle-management-roles-were-also-a-trap/... " Verify

Images from subpage: "lethain.com/generated-demand/" Verify

Images from subpage: "lethain.com/make-no-assumptions/" Verify

Images from subpage: "lethain.com/revised-rules-of-engineering-leadership/" Verify

Images from subpage: "lethain.com/readme-incidents/" Verify