# Generation Z Developers, second edition: a build brief *18 October 2026, written by newsroom.writer for the agent that makes the book. Status: a brief; nothing in it is written. The article is [Generation Z Developers, again](https://newsroom.sgit.ai/articles/generation-z-developers-again.html). Facts checked on 18 October 2026.* ## The ask A second edition of Dinis's 2018 book *Generation Z Developers*: the manual he would hand to people starting out, for getting into development and getting a job, now that everyone who can brief an agent is a developer. It is the first book to make this way, before the graphs books and a new Hacking Portugal. Keep the title and date the edition October 2026; frame it with Wardley's explorers, villagers and town planners, and explain Wardley maps; finish the outlines from the newsroom's articles; say what changed; lots of figures and infographics; his handwritten notes; publish early on Leanpub and LinkedIn, then on Amazon KDP, possibly launched in Portugal around Web Summit (Lisbon, 9 to 12 November 2026). ## The source - Leanpub: [leanpub.com/generation-z](https://leanpub.com/generation-z), "Key concepts and ideas for the next generation of developers", 60% complete, 136 pages, 30,695 words, last updated 2018-10-08, 465 readers. - Repository: [DinisCruz/Book_Generation_Z_Developer](https://github.com/DinisCruz/Book_Generation_Z_Developer), a Hugo site with the content under `content/`, last commit 1 March 2024. The repository's licence file is Apache 2.0; the book's own chapter says Creative Commons, and the printed early release (September 2018) carries the CC BY mark on its cover. Treat the book's text as CC BY and confirm with Dinis; the repository's licence file should be corrected or explained. - 138 Markdown files, 90 of them outlines ("Topics to cover and ideas"). By part: introduction 4 files, no outlines; MVP for Gen Z dev 23, 11 outlines; technologies 17, 10; life patterns 27, 21; concepts 27, 26; security 8, 8; your CV 9, 8; misc 8, 5. - The change log names contributors to earlier versions; credit them in the new edition, with their permission. - Amazon: linked from the repository's README; not read for this brief. ## The edition 1. **Keep the title,** with a subtitle that carries the change, for example *second edition: how to get into development, and get a job, with agents*. Dinis's question was Generation Z or Generation AI; the article argues for Generation Z. Confirm with him. 2. **Map every chapter and outline** to newsroom articles, the way [books from articles](https://newsroom.sgit.ai/articles/books-from-articles.html) proposes: one row per chapter, the articles that answer it, and the gap. First readings: future self → bringing my past work back; publish, publish, publish → your own newsroom; graphs → the graphs books, search as navigation; pioneers, settlers and town planners → software vendors as villagers, explorer coding; open source → the fork next door; GitHub and your CV → act as the job you want; ML and AI → hired for the workflow. 3. **A "then and now" box** in each chapter that changed: what the 2018 text said, what is true in 2026, checked against sources. 4. **A new part on working with agents:** explorer coding, your own newsroom, the man behind the curtain, hired for the workflow, act as the job you want. 5. **Dinis's handwritten notes,** scanned, as figures or an appendix. 6. **Fix the spelling,** keep the voice. ## The workflow - **A new repository for the edition** (name to agree with Dinis; it is not created by this brief), where the agentic workflow is mapped as it runs: briefs, debriefs, the review findings, the interview transcripts, the chapter map and the builds. - **Roles, one folder each,** after graphs.sgit.ai's team (librarian, researcher, writer, editor, developer, QA, publisher): at least a reviewer, an editor and a publisher. Reuse the shelf, reading pages and book-as-graph tooling from graphs.sgit.ai rather than rebuilding them. - **Step 1, a thorough review of the 2018 text:** spelling, facts that dated, broken links, and a verdict per chapter (keep, rewrite, cut, merge). One record per chapter, the way this site's reviews work. - **Step 2, the editor interviews Dinis.** The method of *ten hard questions for RiskMandate*: the agent acts as the book's editor, asks one question at a time, challenges each answer, and keeps going until the narrative is coherent. Interviews are by voice memo or in a session; transcripts kept verbatim in the repository. Opening questions for the first interview: 1. Who exactly is the reader you hand this to, and what do they do differently the week after reading it? 2. The 2018 cover says "question everything". What should a reader question about AI that the 2026 conversation does not? 3. Where does a new developer start: as an explorer, a villager or a town planner? Can they choose? 4. You say young Europeans are fed fear about AI. Fear of what, from whom, and what is the honest answer to it? 5. Which 2018 chapter are you most proud of, and which would you cut? 6. "Everyone is a developer" can sound like a slogan. What can't someone who only briefs agents do, that a 2018 developer could? 7. What is the first workflow the reader should run, end to end, on day one? - **Step 3, the chapter map and drafts:** from the review, the interviews and the newsroom articles. Figures and infographics for every chapter. - **Step 4, quick iterations in public:** versions on Leanpub, posts on LinkedIn, feedback taken into the next version. ## Publishing Follow the plan in books from articles: a 6×9 PDF from the same tooling the graphs books used, Amazon KDP (Dinis has published there before, so review should take up to 72 hours rather than up to 6 days), author copies at print cost, and a printer in Lisbon as the fallback. ## Questions for Dinis - The subtitle, and whether "Generation Z" stays. - Portuguese edition, English edition, or both? - The name of the new repository, and whose account it lives in. - The printed copy with handwritten notes: found, or read again and commented?