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 Kadi Kraman, software developer at Expo working on the tools that make React Native development as smooth as possible. Kadi's path started with C++ in a university maths degree, took her through Angular 1, scientific programming for pharmaceutical and defense companies, five and a half years at Formidable, and finally to Expo itself. From the limitations of early React Native to development builds, EAS workflows, fingerprint-based repacks, and the right way to think about over-the-air updates, this is the React Native conversation most web developers never get.
Señors @ Scale host Neciu Dan sits down with Nico Martin — open source ML engineer at Hugging Face working on Transformers.js, and Google Developer Expert in AI and web technology — to go deep on running machine learning models directly in the browser. Nico breaks down architectures vs. weights, quantization, tokenizers, ONNX, WebGPU, and why on-device AI is the right answer for a huge class of problems. He also shares the road from ski instructor and self-taught web developer to landing what he calls his dream job at Hugging Face.
Señors @ Scale host Neciu Dan sits down with Giorgio Polvara, Staff Engineer at Perk (formerly TravelPerk), who joined when the company was 15 people in two flats with a hole knocked through the wall and helped build the frontend foundations that still hold up at unicorn scale. Giorgio covers the multi-year migration from a monolithic frontend to vertical micro-frontends, why their first attempt with single-spa didn't work, how they pulled off a full rebrand behind feature flags without leaking, and the staff engineer mindset of treating every feature as a system improvement.
Señors @ Scale host Neciu Dan sits down with Zack Chapple, CEO and co-founder of Zephyr Cloud, and Nestor, the platform engineer building it, to go deep on module federation, microfrontends, and what it actually takes to go from code to global scale in seconds. They unpack why module federation is Docker for the frontend, how Zephyr composes applications at the edge in 80 milliseconds, and why the real unlock for enterprise teams isn't deployment — it's composition.
📻 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.