Self-guided architecture workshop

30-day editorial plan

October 19–November 17, 2026 · Suggested dates to review and adapt. Each entry has full copy and a channel-tagged link. Choose your audience's language. Copying or checking an entry does not publish or send anything.

The calendar contains all-day editorial reminders, with no invitees or alerts. Importing it is your action in your calendar app.

1. Oct 19, 2026 · LinkedIn

   A library for testing engineering decisions

   Completed: A library for testing engineering decisions
   Open full copy

   Copy to review and publishA library for testing engineering decisions I put together open tools and materials to turn architecture discussions into experiments: a JSON comparator, .env key checker, queue simulator and TypeScript worker starter. The five-minute route is simple: compare two contracts, generate overload and run the starter tests. Each resource states its limits; the simulation uses no production data. Materials are available in Portuguese, English and Spanish. Which of these decisions comes up most often in your team? Start with the kit and choose one experiment. https://lagrotti.dev/en/recursos/campanhas/kit-engenharia?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d01-kit-enCopy

   View target resource: A library for testing engineering decisions

2. Oct 20, 2026 · WhatsApp

   Did a contract change?

   Completed: Did a contract change?
   Open full copy

   Copy to review and publishDid a contract change? Here is a JSON comparator that shows added, removed and changed fields without treating key order as a change. Try two synthetic examples in your browser. Useful for the next payload review. https://lagrotti.dev/en/recursos/ferramentas/json?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d02-json-enCopy

   View target resource: Did a contract change?

3. Oct 21, 2026 · Developer community

   Open exercise: predict backlog before running

   Completed: Open exercise: predict backlog before running
   Open full copy

   Copy to review and publishOpen exercise: predict backlog before running Sharing an educational queue demo for technical discussion. Challenge: set 20 arrivals/s, two workers and 0% failures. Before advancing ten steps, write down how much work you expect in the queue. Then stop arrivals and estimate drain time. The model attempts one message per worker per second; retries stop after three attempts. It has no backoff, persistence or partitions. The goal is to discuss capacity and recovery, without estimating real broker performance. If you try it, which assumption would you change first: capacity, burst duration or rejection policy? Share your reasoning using synthetic data. https://lagrotti.dev/en/recursos/demos/queue?utm_source=community&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d03-fila-lab-enCopy

   View target resource: Open exercise: predict backlog before running

4. Oct 22, 2026 · LinkedIn

   A queue buys time; capacity pays the bill

   Completed: A queue buys time; capacity pays the bill
   Open full copy

   Copy to review and publishA queue buys time; capacity pays the bill In this model, 20 arrivals per second and two workers leave 18 messages per second outstanding. After ten steps, 180 messages are pending. The queue absorbs the burst without removing the work. With arrivals stopped, two workers need another 90 steps to drain it. If 20 arrivals/s continue, backlog keeps growing. The experiment is ready for you to change the variables. Before choosing a queue, ask: how much delay can the product tolerate, and what is the capacity recovery plan? https://lagrotti.dev/en/recursos/laboratorio/sobrecarga?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d04-backlog-enCopy

   View target resource: A queue buys time; capacity pays the bill

5. Oct 23, 2026 · Newsletter pitch

   Resource suggestion: a TypeScript worker for exploring retries

   Completed: Resource suggestion: a TypeScript worker for exploring retries
   Open full copy

   Copy to review and publishSubject: Resource suggestion: a TypeScript worker for exploring retries Hello, editorial team. I would like to suggest a free resource for an issue about backend engineering or event-driven systems: a runnable TypeScript starter with tests, in-memory deduplication, bounded retries and a dead-letter example. Suggested blurb: “Run a small worker, trigger a failure and follow its retry limit. A starting point for discussing idempotency before adopting a broker.” Requires Node.js 22 or newer and uses the MIT license. The README explains execution; deduplication is process-local and this is not a production-ready solution. If it fits your selection, the link below provides the download and context. Thank you for considering it, Yago Lagrotti Bracco https://lagrotti.dev/en/recursos/templates/worker?utm_source=newsletter&utm_medium=email&utm_campaign=biblioteca-2026-10&utm_content=d05-pitch-worker-enCopy

   View target resource: Resource suggestion: a TypeScript worker for exploring retries

6. Oct 24, 2026 · WhatsApp

   A decision you can revisit

   Completed: A decision you can revisit
   Open full copy

   Copy to review and publishA decision you can revisit An ADR template for context, alternatives, decision and consequences. My favorite part is the review condition: what would need to change for this choice to stop making sense? Download it and fill it in as plain text. https://lagrotti.dev/en/recursos/templates/adr?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d06-adr-enCopy

   View target resource: A decision you can revisit

7. Oct 25, 2026 · LinkedIn

   Does the response need the result now?

   Completed: Does the response need the result now?
   Open full copy

   Copy to review and publishDoes the response need the result now? That question comes before choosing a broker. If the response needs the result immediately, and traffic and dependencies fit the latency budget, a direct call may be enough. A queue makes sense when acceptance and completion can be separate, bursts exceed sustained capacity and work can be replayed safely. That adds decisions about retention, ordering, idempotency and failure handling. I wrote a short guide with criteria and limitations. Use it to review a choice in your context: which requirement actually needs asynchronous processing? https://lagrotti.dev/en/recursos/guias/filas?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d07-guia-filas-enCopy

   View target resource: Does the response need the result now?

8. Oct 26, 2026 · LinkedIn

   A variable name is also a contract

   Completed: A variable name is also a contract
   Open full copy

   Copy to review and publishA variable name is also a contract A deployment can fail because a required key never reached the environment. To review that contract, I built a tool comparing variable names from an .env.example reference against another configuration. The report highlights missing keys, extras, duplicates and invalid lines without reproducing values. Processing happens in the browser. Use synthetic values for demonstrations: the checker is not a complete dotenv parser and cannot confirm a secret is correct. Which configuration check would you like to make before the next deployment? https://lagrotti.dev/en/recursos/ferramentas/env?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d08-env-enCopy

   View target resource: A variable name is also a contract

9. Oct 27, 2026 · WhatsApp

   What if the message arrives twice?

   Completed: What if the message arrives twice?
   Open full copy

   Copy to review and publishWhat if the message arrives twice? Retries raise a question: does repeating this operation repeat its effect? This short explanation of idempotency separates message identity from the business effect. Bring a synthetic payment or order example to your team discussion. https://lagrotti.dev/en/recursos/glossario/idempotencia?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d09-idempotencia-enCopy

   View target resource: What if the message arrives twice?

10. Oct 28, 2026 · Developer community

    Small lab: test failures before the broker

    Completed: Small lab: test failures before the broker
    Open full copy

    Copy to review and publishSmall lab: test failures before the broker Here is an exercise using the library's TypeScript starter. Download it and run npm install, npm test and npm start on Node.js 22+. Read the deduplication test and retry limit before changing code. Now describe two scenarios: a repeated message within one process and a repeat after restarting the process. An in-memory Set does not solve the second case. Which storage and transaction boundary would you use to connect the business effect to its idempotency key? The starter uses the MIT license and is educational. If you share a solution, include a test and explain the failure assumption; use no real customer data. https://lagrotti.dev/en/recursos/templates/worker?utm_source=community&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d10-worker-lab-enCopy

    View target resource: Small lab: test failures before the broker

11. Oct 29, 2026 · LinkedIn

    A benchmark needs context to be useful

    Completed: A benchmark needs context to be useful
    Open full copy

    Copy to review and publishA benchmark needs context to be useful Comparing JSON.parse/stringify and structuredClone by the lowest time leaves important questions unanswered. Which types must survive? How large was the data? Was the runtime the same? I published an experiment with synthetic JSON data, warm-up, alternating method order and downloadable raw samples. The dataset does not test Date, Map, cycles or transferables. A local measurement does not make one strategy a universal winner. Read the method, run the script in your environment and compare results by size. Which use case would change your choice even at a higher execution time? https://lagrotti.dev/en/recursos/benchmarks/json-clone?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d11-clone-enCopy

    View target resource: A benchmark needs context to be useful

12. Oct 30, 2026 · Newsletter pitch

    For your resource list: a queue you can overload

    Completed: For your resource list: a queue you can overload
    Open full copy

    Copy to review and publishSubject: For your resource list: a queue you can overload Hello, editorial team. I would like to suggest an interactive demo for an issue on reliability: readers adjust arrivals, workers and failures to observe backlog, retries and dead letters. No account is required. Suggested blurb: “Before adding a queue, predict backlog from a ten-second burst and test your estimate in the browser.” The model is educational, with no production data, backoff or persistence. The page states those limits and lets readers repeat the exercise. It may be a practical companion to a capacity discussion. Here is the link for your review. Thank you, Yago Lagrotti Bracco https://lagrotti.dev/en/recursos/demos/queue?utm_source=newsletter&utm_medium=email&utm_campaign=biblioteca-2026-10&utm_content=d12-pitch-filas-enCopy

    View target resource: For your resource list: a queue you can overload

13. Oct 31, 2026 · WhatsApp

    Repeat the measurement on your runtime

    Completed: Repeat the measurement on your runtime
    Open full copy

    Copy to review and publishRepeat the measurement on your runtime Here is a JSON cloning experiment with a script and synthetic data. Run it in your environment and compare medians by size. The useful part is recording method and limits, rather than choosing an API from one number. Instructions are here. https://lagrotti.dev/en/recursos/laboratorio/copias?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d13-reproduzir-enCopy

    View target resource: Repeat the measurement on your runtime

14. Nov 1, 2026 · LinkedIn

    Read the flow before choosing the tool

    Completed: Read the flow before choosing the tool
    Open full copy

    Copy to review and publishRead the flow before choosing the tool Event discussions become more concrete when we draw the stages: where data enters, where it is processed and how it reaches queries. The VMAGeste case study uses that flow as an entry point into its architecture decisions. My suggested reading exercise: identify an asynchronous boundary, write down the assumption it addresses and look for what operations would need to observe. Use the case for context and the library demo to test capacity ideas with synthetic data. What do you look for first in a diagram when trying to understand failure recovery? https://lagrotti.dev/en/projetos/vmageste?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d14-caso-vmageste-enCopy

    View target resource: Read the flow before choosing the tool

15. Nov 2, 2026 · LinkedIn

    One hour to write a defensible decision

    Completed: One hour to write a defensible decision
    Open full copy

    Copy to review and publishOne hour to write a defensible decision I prepared a self-guided workshop around one bounded problem: 20 orders/s arrive, two are processed per second and the burst lasts ten seconds. The task is to model backlog and record a decision in an ADR. The outline splits one hour between context, experiment, alternatives, writing and review. Work alone or in pairs with only a browser and text editor. The material includes exercises, expected outcomes and an answer key for discussion. This is available material, with no registration or scheduled event. Which condition would make you reject work instead of queuing it? https://lagrotti.dev/en/recursos/campanhas/oficina-arquitetura?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d15-oficina-enCopy

    View target resource: One hour to write a defensible decision

16. Nov 3, 2026 · WhatsApp

    Two-minute challenge

    Completed: Two-minute challenge
    Open full copy

    Copy to review and publishTwo-minute challenge 20 arrivals/s, two workers, 0% failures, ten seconds. How much work remains? Predict before opening the demo, then stop arrivals to measure recovery. The exercise separates a temporary burst from a permanent capacity deficit. https://lagrotti.dev/en/recursos/laboratorio/sobrecarga?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d16-pico-enCopy

    View target resource: Two-minute challenge

17. Nov 4, 2026 · Developer community

    ADR review: what evidence would change your decision?

    Completed: ADR review: what evidence would change your decision?
    Open full copy

    Copy to review and publishADR review: what evidence would change your decision? An exercise for an architecture discussion: use the self-guided workshop scenario and write an ADR with context, two alternatives, a decision, consequences and a review condition. Avoid justifying it through tool preference alone. One alternative can retain current capacity and accept delay; another can increase workers or reject arrivals above a limit. Compare recovery time, cost, duplication and user-visible behavior. State the assumptions your experiment did not measure. During review, look for a testable condition that would force reconsideration. The material includes an example answer without treating one architecture as the only solution. Which assumption is missing from your ADR? https://lagrotti.dev/en/recursos/campanhas/oficina-arquitetura?utm_source=community&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d17-adr-review-enCopy

    View target resource: ADR review: what evidence would change your decision?

18. Nov 5, 2026 · LinkedIn

    Does a code boundary need to become a service?

    Completed: Does a code boundary need to become a service?
    Open full copy

    Copy to review and publishDoes a code boundary need to become a service? Separating responsibilities is one decision; separating deployments is another. A boundary can begin inside a modular monolith and later gain independent operations if a concrete need emerges. The guide on modular monoliths and separate services compares autonomy, contracts and operating cost. A new process also adds networking, observability and partial failures. Before splitting, write down the constraint that separation solves and the condition that would justify revisiting it. Which part of your system needs operational autonomy today? https://lagrotti.dev/en/recursos/guias/monolito?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d18-monolito-enCopy

    View target resource: Does a code boundary need to become a service?

19. Nov 6, 2026 · Newsletter pitch

    Study material: a 60-minute architecture workshop

    Completed: Study material: a 60-minute architecture workshop
    Open full copy

    Copy to review and publishSubject: Study material: a 60-minute architecture workshop Hello, editorial team. I would like to suggest material for a study or team activities section: a 60-minute workshop on comparing alternatives and writing an ADR supported by a capacity experiment. Suggested blurb: “One problem, one simulation and one recorded decision. Work alone or in pairs with a browser and text editor.” The guide includes timing, exercises, expected outcomes and an answer key. The scenario is fictional and requires no registration. It is an available proposal and self-guided material, with no claim of a previous presentation or class. The link provides context and downloads for review. Thank you, Yago Lagrotti Bracco https://lagrotti.dev/en/recursos/palestras/arquitetura?utm_source=newsletter&utm_medium=email&utm_campaign=biblioteca-2026-10&utm_content=d19-pitch-oficina-enCopy

    View target resource: Study material: a 60-minute architecture workshop

20. Nov 7, 2026 · WhatsApp

    Quick configuration review

    Completed: Quick configuration review
    Open full copy

    Copy to review and publishQuick configuration review Before testing, create two synthetic .env files: a reference with API_URL and WORKER_TOKEN, and another with API_URL repeated. The checker shows the missing key and duplicate without reproducing values in the report. Here is the tool. https://lagrotti.dev/en/recursos/ferramentas/env?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d20-env-check-enCopy

    View target resource: Quick configuration review

21. Nov 8, 2026 · LinkedIn

    What should you observe beyond queue length?

    Completed: What should you observe beyond queue length?
    Open full copy

    Copy to review and publishWhat should you observe beyond queue length? Two backlogs of the same size can represent very different situations. A queue that drains quickly after a burst calls for one interpretation; an old message that never progresses calls for another. To explore that difference, read the PulseWatch case alongside the queue guide. Use the case as product and operations context without turning simulator numbers into project metrics. In your review, note three signals: oldest message age, completion rate and failure destination. Which signal would help you choose between waiting, scaling and investigating? https://lagrotti.dev/en/projetos/pulsewatch?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d21-caso-pulsewatch-enCopy

    View target resource: What should you observe beyond queue length?

22. Nov 9, 2026 · LinkedIn

    Where does the third failure go?

    Completed: Where does the third failure go?
    Open full copy

    Copy to review and publishWhere does the third failure go? A retry needs a limit and a destination after that limit. In the educational demo, a message failing three times goes to a dead-letter queue. That ends the model's automatic cycle but does not explain how to fix the cause. An operations discussion must say who investigates, how to identify the message and when replay is safe. Moving work from an endless retry loop into an unowned error store is not enough. The glossary explains DLQs and connects the concept to the exercise. If a message reached the dead-letter queue today, would your team know the next step? https://lagrotti.dev/en/recursos/glossario/dead-letter?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d22-retries-enCopy

    View target resource: Where does the third failure go?

23. Nov 10, 2026 · WhatsApp

    Watch a contract change

    Completed: Watch a contract change
    Open full copy

    Copy to review and publishWatch a contract change A short recording shows two versions of an event and the fields that changed. Watch it, then repeat the comparison with synthetic examples. A quick starting point for a contract review discussion. https://lagrotti.dev/en/recursos/videos/json?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d23-json-video-enCopy

    View target resource: Watch a contract change

24. Nov 11, 2026 · Developer community

    Open invitation: reproduce a benchmark with a method

    Completed: Open invitation: reproduce a benchmark with a method
    Open full copy

    Copy to review and publishOpen invitation: reproduce a benchmark with a method I opened a brief for reproducing the JSON cloning experiment on another runtime and comparing results with the same method. The material includes the script, samples and limitations. A useful contribution states runtime version, system, CPU, command and raw samples using synthetic data. Before comparing, check object sizes and each API's semantic guarantees. Differences can motivate hypotheses; they do not prove a universal rule. The brief explains review and credit. There are no confirmed coauthors; any joint publication depends on methodology review and participant permission. If this kind of reproduction interests you, read the scope and propose a contribution. https://lagrotti.dev/en/recursos/colaboracoes/reproduzir-benchmark?utm_source=community&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d24-benchmark-colab-enCopy

    View target resource: Open invitation: reproduce a benchmark with a method

25. Nov 12, 2026 · LinkedIn

    From payload to product context

    Completed: From payload to product context
    Open full copy

    Copy to review and publishFrom payload to product context A diff shows that a field changed. Deciding whether it matters needs context: who produces it, who consumes it and which behavior depends on it. Use the Eurologado case study as a reading exercise. Pick one described flow and write a minimal fictional contract for it. Then add a field and change a value using the library's JSON comparator. This does not reproduce the project's internal contracts. It connects a comparison tool to product questions: can the consumer tolerate the change? Would validation detect an incompatibility? https://lagrotti.dev/en/projetos/eurologado?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d25-caso-eurologado-enCopy

    View target resource: From payload to product context

26. Nov 13, 2026 · Newsletter pitch

    Resource suggestion: engineering tools and exercises

    Completed: Resource suggestion: engineering tools and exercises
    Open full copy

    Copy to review and publishSubject: Resource suggestion: engineering tools and exercises Hello, editorial team. I would like to suggest the open engineering kit for a practical resources selection. It brings together a JSON comparator, .env key checker, queue demo, TypeScript starter and architecture decision exercises in Portuguese, English and Spanish. Suggested blurb: “Compare a contract, trigger overload and take a starter with tests. A library for experimenting with decisions using synthetic data.” The resources explain their limitations and can be explored without registration. I am not presenting audience metrics or adoption results; the link below lets you assess the material directly. If it fits an issue, I can clarify method and scope. Thank you, Yago Lagrotti Bracco https://lagrotti.dev/en/recursos/campanhas/kit-engenharia?utm_source=newsletter&utm_medium=email&utm_campaign=biblioteca-2026-10&utm_content=d26-pitch-kit-enCopy

    View target resource: Resource suggestion: engineering tools and exercises

27. Nov 14, 2026 · WhatsApp

    A 30-minute queue outline

    Completed: A 30-minute queue outline
    Open full copy

    Copy to review and publishA 30-minute queue outline I prepared “Queues without magic”: an outline and material for discussing capacity, retries, idempotency and observability in 30 minutes. Includes exercises and an answer key. Available for invitations or study, with no scheduled event. https://lagrotti.dev/en/recursos/palestras/eventos?utm_source=whatsapp&utm_medium=messaging&utm_campaign=biblioteca-2026-10&utm_content=d27-charla-enCopy

    View target resource: A 30-minute queue outline

28. Nov 15, 2026 · LinkedIn

    Replace “it is better” with an observable condition

    Completed: Replace “it is better” with an observable condition
    Open full copy

    Copy to review and publishReplace “it is better” with an observable condition A useful ADR does not end with the technology choice. It records the constraint, the rejected alternative and the signal that would make the team reconsider. In the workshop's fictional scenario, a condition might be: if backlog does not drain within the product's required time, revisit capacity and admission policy. The number must come from a requirement or experiment, with visible assumptions. The template is available as plain text for adaptation. Take a recent decision: which consequence was accepted consciously, and what evidence would show its cost has grown too high? https://lagrotti.dev/en/recursos/templates/adr?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d28-decisao-enCopy

    View target resource: Replace “it is better” with an observable condition

29. Nov 16, 2026 · Developer community

    Used a resource? Show a verifiable application

    Completed: Used a resource? Show a verifiable application
    Open full copy

    Copy to review and publishUsed a resource? Show a verifiable application The library has an open invitation for anyone who applies a resource in a public demonstration. A useful proposal shows which resource was used, what was adapted and how another person can verify the result. It could be a deduplication test, an ADR with a reproducible experiment or a contract comparison using synthetic data. Include a public link, preferred credit and publication permission. Share no third-party personal data or confidential material. Proposals are reviewed; submission does not guarantee publication. The page explains the process and lets you prepare and review a proposal before sending. Which adaptation would make the resource more useful in your context? https://lagrotti.dev/en/recursos/comunidade/sua-aplicacao?utm_source=community&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d29-comunidade-enCopy

    View target resource: Used a resource? Show a verifiable application

30. Nov 17, 2026 · LinkedIn

    Choose an experiment and record what you learned

    Completed: Choose an experiment and record what you learned
    Open full copy

    Copy to review and publishChoose an experiment and record what you learned If you reached the library through a post, here is a route from reading to practice: compare two synthetic payloads, overload the queue, test the starter and write an ADR with a review condition. You do not need to adopt a new technology to get value from the exercise. The outcome might be confirming that a direct call is enough, finding an untested assumption or explaining failure recovery more clearly. The kit collects the routes and downloads in three languages. Which experiment would you choose for your next engineering discussion? Write your prediction before running it and compare afterward. https://lagrotti.dev/en/recursos/campanhas/kit-engenharia?utm_source=linkedin&utm_medium=social&utm_campaign=biblioteca-2026-10&utm_content=d30-proximo-enCopy

    View target resource: Choose an experiment and record what you learned