Meta tags:
description=To be on the hook is to be the one who answers when something breaks. Every team carries a picture... Tagged with agenticsystems, softwareengineering, leadership.;
keywords=agenticsystems, softwareengineering, leadership, software, coding, development, engineering, inclusive, community;

Headings (most frequently used words):

the, left, of, loop, 20, part, series, who, on, hook, dev, community, top, comments, more, from, simon, schrottner,

Text of the page (most frequently used words):
the (156), left (48), loop (48), and (17), that (16), team (16), dev (14), for (10), hook (9), what (9), this (8), was (8), with (7), who (7), share (6), about (6), pipeline (6), spec (6), where (5), end (5), they (5), got (5), accountable (5), not (5), one (5), create (4), #community (4), code (4), softwareengineering (4), agenticsystems (4), more (4), schrottner (4), you (4), still (4), problem (4), fool (4), responsibility (4), never (4), accountability (4), because (4), agent (4), production (4), review (4), before (4), software (3), pheme (3), platformengineering (3), hestia (3), phoenix (3), simon (3), person (3), abuse (3), comments (3), but (3), answer (3), nobody (3), ever (3), tool (3), wrong (3), part (3), don (3), here (3), always (3), just (3), makes (3), now (3), instead (3), mistake (3), gets (3), every (3), way (3), when (3), something (3), account (2), log (2), made (2), built (2), open (2), use (2), conduct (2), organization (2), space (2), keep (2), your (2), from (2), hide (2), comment (2), will (2), post (2), via (2), report (2), let (2), boule (2), gymnasion (2), metron (2), mimesis (2), kybernetes (2), walking (2), over (2), desk (2), dead (2), long (2), live (2), oikonomos (2), astrolabe (2), trireme (2), agora (2), alexandria (2), agreeing (2), genie (2), craftsman (2), parts (2), series (2), remove (2), didn (2), answers (2), honest (2), isn (2), away (2), organizations (2), pretending (2), individual (2), has (2), like (2), name (2), postmortems (2), whatever (2), someone (2), quietly (2), doesn (2), tooling (2), already (2), work (2), fire (2), once (2), can (2), its (2), own (2), same (2), first (2), judgment (2), does (2), automation (2), configured (2), deploy (2), hand (2), catching (2), anything (2), done (2), point (2), nothing (2), any (2), hands (2), question (2), true (2), breaks (2), picture (2), jul (2), copy (2), link (2), search (2), place, coders, stay, date, grow, their, careers, love, 2016, 2026, ruby, rails, powers, other, inclusive, communities, source, forem, terms, privacy, policy, mlh, shop, free, postgres, database, contact, showcase, accounts, advertise, help, education, tracks, videos, challenges, home, discuss, development, manage, career, nov, 2021, joined, pernegg, der, mur, austria, location, follow, further, actions, may, consider, blocking, reporting, confirm, child, well, are, sure, want, become, hidden, visible, permalink, dismiss, preview, submit, templates, quickly, faqs, store, snippets, template, trusted, user, personal, subscribe, top, tools, take, either, changed, automated, change, going, discomfort, goes, rituals, good, moment, stop, complication, philosophically, been, correct, institutionally, act, performance, reviews, look, claim, blamelessness, tend, list, tension, uncomfortable, ignoring, there, very, obvious, non, human, party, room, blame, easy, story, reach, helping, meet, had, takes, none, disappear, relocates, feature, flags, gate, release, roll, back, bad, decision, without, drill, means, caught, fixed, whole, per, happens, hit, org, see, failures, learns, faster, than, repeats, isolation, centralized, useful, comparison, looks, call, repeated, known, process, time, make, calls, constantly, inside, config, thing, bounds, allowed, decide, allow, think, happened, showed, devs, used, build, artifact, themselves, concluded, stopped, being, responsible, deployed, machine, ran, step, anywhere, execution, did, assumption, cheap, incident, moving, earlier, have, real, chance, get, right, ships, session, better, stakeholders, line, implemented, intent, costs, conversation, diff, attached, deadline, breathing, changes, moved, unit, typing, wrote, broke, wasn, reviewed, approved, else, design, discussed, anyone, opened, editor, incidents, disciplinary, letters, them, felt, were, keyboard, assumes, begin, skeptical, engineering, leader, asks, model, implements, agreed, carries, hangs, whether, leadership, originally, published, posted, mastodon, facebook, linkedin, copied, clipboard, pick, gem, boost, save, jump, raised, exploding, head, unicorn, add, reaction, close, powered, algolia, navigation, menu, skip, content,

Text of the page (random words):
left of the loop who s on the hook dev community skip to content navigation menu search powered by algolia search log in create account dev community close add reaction like unicorn exploding head raised hands fire jump to comments save boost pick as gem more copy link copy link copied to clipboard share to x share to linkedin share to facebook share to mastodon share post via report abuse simon schrottner posted on jul 10 originally published at schrottner at on jul 10 left of the loop who s on the hook agenticsystems softwareengineering leadership left of the loop 20 part series 1 left of the loop the wrong end of the problem 2 left of the loop a fool with a tool is still a fool 16 more parts 3 left of the loop the end of the craftsman 4 left of the loop the ever agreeing genie 5 left of the loop the alexandria problem 6 left of the loop the agora 7 left of the loop the trireme 8 left of the loop the astrolabe 9 left of the loop the oikonomos 10 left of the loop the po is dead long live the po 11 left of the loop nobody s walking over to a desk 12 left of the loop who s on the hook 13 left of the loop the kybernetes 14 left of the loop the mimesis 15 left of the loop the metron 16 left of the loop the gymnasion 17 left of the loop the boule 18 left of the loop the pheme 19 left of the loop the hestia 20 left of the loop the phoenix to be on the hook is to be the one who answers when something breaks every team carries a picture of where that hook hangs this is about whether the picture was ever true it s the first question any skeptical engineering leader asks about this model the agent implements from a spec the team agreed on something breaks in production who s on the hook the question assumes an answer that was never true to begin with before any of this when a dev wrote the code by hand and it broke in production it wasn t that dev on the hook it was the team the pr got reviewed and approved by someone else the design got discussed before anyone opened an editor production incidents got postmortems not disciplinary letters with one name on them accountability was never individual it just felt that way because one person s hands were on the keyboard nothing about that changes here a part of the work moved to an agent the team is still what s on the hook because the team was always the unit of accountability not the person typing if anything it gets better the team can review the spec with stakeholders before a line of anything gets implemented that s a review of intent done at the point where a mistake costs nothing but a conversation instead of a review of code done at the point where a mistake already has a diff attached to it and a deadline breathing on it catching a wrong assumption in a spec session is cheap catching it in a production incident is not moving the review earlier doesn t remove accountability it makes the team accountable for something they now have a real chance to get right before it ships think about what happened when ci cd automation showed up devs used to build the artifact and deploy it themselves by hand now a pipeline does that nobody concluded the team stopped being responsible for what got deployed just because a machine ran the deploy step the responsibility didn t go anywhere the execution did the pipeline is a useful comparison but not the way it first looks the agent isn t the pipeline the pipeline never made a judgment call it repeated a known process the same way every time the agent does make judgment calls constantly inside whatever space the spec left open the spec is the pipeline config it s the thing that bounds what the automation is allowed to decide on its own the team was always accountable for what they configured the pipeline to do here the team is accountable for what they configured the spec to allow none of this makes the work disappear it relocates it feature flags let the team gate a release and roll back a bad decision without a fire drill a centralized loop means a mistake gets caught and fixed once for the whole organization instead of once per team that happens to hit it an org that can see its own failures learns faster than one where every team quietly repeats the same one in isolation that s tooling helping the team meet the responsibility it already had not tooling that takes the responsibility away here s the honest complication philosophically the team is accountable has always been correct institutionally organizations don t act like it performance reviews look for a name postmortems whatever they claim about blamelessness tend to end with someone quietly on a list ai doesn t create this tension it just makes it uncomfortable to keep ignoring because now there s a very obvious non human party in the room to blame instead and that s an easy story to reach for the honest answer isn t that the team is accountable and the discomfort goes away it s that organizations built rituals pretending accountability was individual and this is a good moment to stop pretending ai is a tool tools don t take on responsibility and they don t remove it either what changed is what got automated what didn t change and never was going to is who answers for it left of the loop 20 part series 1 left of the loop the wrong end of the problem 2 left of the loop a fool with a tool is still a fool 16 more parts 3 left of the loop the end of the craftsman 4 left of the loop the ever agreeing genie 5 left of the loop the alexandria problem 6 left of the loop the agora 7 left of the loop the trireme 8 left of the loop the astrolabe 9 left of the loop the oikonomos 10 left of the loop the po is dead long live the po 11 left of the loop nobody s walking over to a desk 12 left of the loop who s on the hook 13 left of the loop the kybernetes 14 left of the loop the mimesis 15 left of the loop the metron 16 left of the loop the gymnasion 17 left of the loop the boule 18 left of the loop the pheme 19 left of the loop the hestia 20 left of the loop the phoenix top comments 0 subscribe personal trusted user create template templates let you quickly answer faqs or store snippets for re use submit preview dismiss code of conduct report abuse are you sure you want to hide this comment it will become hidden in your post but will still be visible via the comment s permalink hide child comments as well confirm for further actions you may consider blocking this person and or reporting abuse simon schrottner follow location pernegg an der mur austria joined nov 16 2021 more from simon schrottner left of the loop the phoenix agenticsystems platformengineering softwareengineering left of the loop the hestia agenticsystems platformengineering softwareengineering left of the loop the pheme agenticsystems platformengineering softwareengineering dev community a space to discuss and keep up software development and manage your software career home dev challenges dev videos dev education tracks dev help advertise on dev organization accounts dev showcase about contact free postgres database dev shop mlh code of conduct privacy policy terms of use built on forem the open source software that powers dev and other inclusive communities made with love and ruby on rails dev community 2016 2026 we re a place where coders share stay up to date and grow their careers log in create account