Jose Calderon
Lead Software Engineer at JP Morgan Chase
In this episode of Señors @ Scale, host Neciu Dan sits down with Jose Calderon — Lead Software Engineer at JP Morgan Chase, conference speaker, and Java/Spring community leader — to dive deep into refactoring vs rewriting at scale, how to track and justify architecture decisions, and the testing strategies that keep enterprise systems reliable.
Main Takeaways from my conversation with Jose:
🛠 Refactor if you’re in control, rewrite if you’re not.
If your team understands the codebase, has tests, and changes are predictable, refactor. If one line breaks something unrelated or the code is untestable, it’s rewrite time — but keep the scope locked and avoid “bonus” features.
🚧 Stabilize before you touch it.
Before a rewrite, Jose’s teams add telemetry, fix recurring issues, and lock down changes so the new build isn’t chasing a moving target.
💾 Your code is only as good as your decision history.
He uses Architecture Decision Records (ADRs) — stored in source control — to document the why behind each decision, making it easier to evolve or roll back choices later.
📈 Tests are documentation too.
Unit tests should read like an executable spec, explaining what the code does before you even open the class.
🎯 Synthetic testing catches breakage early.
Injecting canary events into critical paths — even in production when allowed — validates integrations before customers feel the pain.
🔥 Chaos engineering builds resilience.
Game-day drills prepare teams to recover fast when production crashes inevitably happen.
👨🏫 Mentorship multiplies impact.
By teaching final-year students how to lead and coach, Jose helps prepare them for the messy realities of enterprise engineering.
🎤 Also in this episode:
- How to pick the right complementary stack with Java
- Turning conference talks into memorable stories (Gaudí, aloe vera, and more)
- Why AI won’t replace devs, but devs using AI will replace those who don’t
- How gaming helps avoid burnout
Episode Length: 1 hour and 6 minutes of pragmatic engineering lessons on managing large-scale code changes
💡 More Recent Takeaways
Señors @ Scale host Neciu Dan sits down with Liran Tal, Director of Developer Advocacy at Snyk and GitHub Star, to unpack NPM malware, maintainer compromise, MCP attacks, toxic flows, and why AI-generated code is statistically insecure without the right guardrails. Liran shares real incidents from the Node and open source ecosystem, how Snyk and tools like NPQ help developers build safer workflows, and why security at scale starts with developers, not firewalls.
Señors @ Scale host Neciu Dan sits down with Luca Mezzalira, Principal Serverless Specialist at AWS and author of *Building Micro-Frontends*, to unpack how he helped scale DAZN’s frontend from 2 developers to 500 engineers across 40 devices. Luca shares the origin of micro-frontends, how to build stable application shells, implement zero global state, use guardrails for bundle budgets, and manage migrations at scale through edge routing and team autonomy.
Señors @ Scale host Neciu Dan sits down with Stefano Magni, Senior Front-End Engineer and Tech Lead at Preply, to unpack what it takes to build and measure a design system for a global learning platform. From managing technical debt and accessibility to driving a culture of public work and data-driven engineering, Stefano shares lessons from 15+ years in frontend development.
Señors @ Scale host Neciu Dan sits down with Bruno Paulino, Tech Lead at N26, to explore what reliability really means in FinTech. From server-driven UIs and CI/CD pipelines to AI-assisted customer support and strict compliance, Bruno shares how N26 balances speed, safety, and developer experience to keep millions of users online.
📻 Never Miss New Takeaways
Get notified when new episodes drop. Join our community of senior developers learning from real scaling stories.
💬 Share These Takeaways
Want More Insights Like This?
Subscribe to Señors @ Scale and never miss conversations with senior engineers sharing their scaling stories.