[{"data":1,"prerenderedAt":36},["ShallowReactive",2],{"rR5k6ogvOcgnuLyIKi1Iw188ZksXL2LawaJFmVeUc1Y":3,"_apollo:default":22},{"talks":4},[5],{"__typename":6,"id":7,"name":8,"abstract":9,"youtubecode":10,"category":11,"createdAt":12,"speakers":13,"event":18},"Talk","cmmdpc7aulzen07tc012v1obh","Why Documentation Won’t Write Itself—and AI Won’t Save You","For the last 15+ years, I’ve joined and consulted software teams that all struggled with the same problem: nobody likes writing documentation, and everybody pays the price for it. New developers spend weeks reverse-engineering codebases, architecture lives in people’s heads, and wikis quietly decay into noise.\n\nWith AI now entering the picture, many hope it will fill the gaps. It won’t.\n\nI’ll show the simple ideas that change everything: how to think about documentation in the right levels, how to keep it close to the code, and how to avoid the decay we all know too well. These are the decisions that have to be made before any tool or process can work.\n\nThe documentation won’t write itself. But there are ways to make it far easier and far more reliable.",null,"Others","2026-03-05T16:50:41.496671+00:00",[14],{"__typename":15,"id":16,"name":17,"speakerPicture":10},"Speaker","cmmdpblcslrfp07uifphn2ti5","Christian Heitzmann",{"__typename":19,"id":20,"date":21},"Event","cmmdots9elegz07tcxai9pwp4","2026-03-27",{"Speaker:cmmdpblcslrfp07uifphn2ti5":23,"Event:cmmdots9elegz07tcxai9pwp4":24,"Talk:cmmdpc7aulzen07tc012v1obh":25,"ROOT_QUERY":31},["null","__typename",15,"id",16,"name",17,"speakerPicture",10],["null","__typename",19,"id",20,"date",21],["null","__typename",6,"id",7,"name",8,"abstract",9,"youtubecode",10,"category",11,"createdAt",12,"speakers",26,"event",29],[27],{"__ref":28},"Speaker:cmmdpblcslrfp07uifphn2ti5",{"__ref":30},"Event:cmmdots9elegz07tcxai9pwp4",["null","__typename",32,"talks({\"first\":1,\"where\":{\"id\":\"cmmdpc7aulzen07tc012v1obh\"}})",33],"Query",[34],{"__ref":35},"Talk:cmmdpc7aulzen07tc012v1obh",1791213694085]