How the projects were built and what I learned along the way. Decisions with their reasons, mistakes with their cost.https://portfolio-luciano-carrizo.pages.dev/https://portfolio-luciano-carrizo.pages.dev/en/articles/i-learned-design-by-copying/https://portfolio-luciano-carrizo.pages.dev/en/articles/i-learned-design-by-copying/I designed my portfolio with a different reference for every page, yet they all came out using the same repertoire of gestures: the same full-screen hero, the same sidebar, the same label above the title. The tools that got me out of that pattern—Figma, Canva, structured prompts—arrived only at the end, and I think that is why they worked.Tue, 28 Jul 2026 00:00:00 GMTmockupsjudgmentdesign-systemtoolshttps://portfolio-luciano-carrizo.pages.dev/en/articles/three-roles-not-twelve/https://portfolio-luciano-carrizo.pages.dev/en/articles/three-roles-not-twelve/An orchestrator that writes prompts and verifies what comes back, a research role accountable for its sources, and an implementation role accountable for leaving the repository green. This is the system I now use to delegate work to AI agents, after trying an entire org chart of managers and specialists.Tue, 28 Jul 2026 00:00:00 GMTagentsorchestrationdelegationworkflowhttps://portfolio-luciano-carrizo.pages.dev/en/articles/16-documents-500-commit-fork/https://portfolio-luciano-carrizo.pages.dev/en/articles/16-documents-500-commit-fork/I adopted a 500-commit codebase I did not write and documented its views in the opposite order from the obvious one: first I changed the feature, only then did I write the document.Sun, 26 Jul 2026 00:00:00 GMTdocsrustgitlegacyhttps://portfolio-luciano-carrizo.pages.dev/en/articles/the-ci-i-inherited-was-never-green/https://portfolio-luciano-carrizo.pages.dev/en/articles/the-ci-i-inherited-was-never-green/A fork brings the code, the license, and the history. It also brings broken CI, and nobody tells you until you open the first PR.Sat, 11 Jul 2026 00:00:00 GMTci-cdgithub-actionsrusttauri