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
In this episode of Señors @ Scale, host Neciu Dan chats with Erik Grijzen — Principal Software Engineer at New Relic — about building one of the first large-scale micro-frontend architectures, the rise of observability, and what technical leadership looks like across dozens of teams.
In this episode of Señors @ Scale, host Neciu Dan chats with Kateryna Porchienova — Senior Engineering Manager at Buffer — about her programming journey, the craft of animation, and why accessibility should be treated as a foundation of good engineering, not an afterthought.
In this episode of Señors @ Scale, host Neciu Dan chats with Adrian Marin — founder of AVO and host of FriendlyRB — about Rails productivity, the magic of Ruby, and how the community continues to evolve through creativity and connection.
In this episode of Señors @ Scale, host Neciu Dan sits down with Andreas Panopoulos — Staff Software Engineer at Hack the Box and co-organizer of Vue.js Athens — to talk about scaling Vue in production, migrating to Nuxt 3, and the human side of engineering.
📻 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.