[{"data":1,"prerenderedAt":39},["ShallowReactive",2],{"profile-en":3,"article-decisoes-tecnicas-peso-do-legado-en":27},{"brandName":4,"fullName":5,"headline":6,"manifesto":7,"contactIntro":11,"avatar":12,"manifestoImage":13,"social":14},"Danilo Fernando","Danilo Fernando - Senior Software Engineer","Well-built software, reliable integrations, and architecture designed to last.",[8,9,10],"My journey is guided by the belief that code is just a tool to solve complex business problems. With solid experience in the Java and Spring ecosystems, I focus on systems that work AND are easy to maintain and evolve.","Specialised in robust APIs and critical integrations, I believe technical maturity shows up in balanced decisions that weigh innovation against real business needs.","I chase real impact: Clean Code is not aesthetics, it is an economic necessity for long-term product sustainability.","I'm always open to new professional opportunities, technical exchange, or conversations about architecture and software engineering.","\u002Fimages\u002Fprofile\u002Fdanilo.webp","\u002Fimages\u002Fprofile\u002Fdanilo_manifesto.webp",[15,19,23],{"kind":16,"label":17,"href":18},"email","Email","mailto:danilo.bossanova@hotmail.com",{"kind":20,"label":21,"href":22},"linkedin","LinkedIn","https:\u002F\u002Fwww.linkedin.com\u002Fin\u002Fdanilo-fernando-dev\u002F",{"kind":24,"label":25,"href":26},"github","GitHub","https:\u002F\u002Fgithub.com\u002Fdanilobossanova",{"slug":28,"title":29,"excerpt":30,"category":31,"tags":32,"readTimeMinutes":35,"publishedAt":36,"author":4,"coverImage":37,"body":38},"decisoes-tecnicas-peso-do-legado","Technical decisions and the weight of legacy","Being senior is less about \"how to code\" and more about \"when not to code\".","Career",[33,34],"career","tech-leadership",6,"2024-12-05","https:\u002F\u002Fpicsum.photos\u002Fseed\u002Fcareer\u002F1200\u002F600","## Seniority is context\n\nThe job shifts from *\"solving the right problem\"* to *\"picking which problem\nto solve\"*. That requires little about how to code and a lot about **knowing\nhow to say no**.\n\n### The weight of legacy\n\nLegacy code is the cost you **didn't pay** when the system was born. Every\nshortcut from the past became high-interest debt. The senior's job isn't to\nrewrite everything — it's to pick *which piece* of debt is worth paying off\nthis quarter.\n\n### The map I use\n\n- **High pain + high risk** → surgical refactor with new tests.\n- **High pain + low risk** → replace and move on.\n- **Low pain + high risk** → monitor and document the danger.\n- **Low pain + low risk** → **leave it alone**.",1776457052038]