Hard to Hire, Hard to Learn, Hard to Break: A CTO’s Scala Case
Session Abstract
To business leadership, Scala looks like a high-risk bet: the talent is expensive and the learning curve is a wall. So why willingly sign off on a technology that makes recruiting harder? Because optimizing for cheap headcount is a false economy. This fast-paced session bridges the gap between engineering elegance and CFO mathematics. You will learn how to expose the “shadow payroll” of bloated polyglot teams, and leave armed with the exact financial vocabulary needed to prove that a lean, elite Scala team is the most aggressive risk-mitigation strategy a CTO can deploy.
Session Description
Scala Days is packed with brilliant deep dives into the “how” of the language, but this session zooms out to ask the fundamental “why.”
When engineers pitch Scala to business leadership, the conversation usually hits a wall. To a CTO or CFO, Scala looks like a high-risk bet: the talent is expensive, and the hiring pipeline is slow. The default corporate instinct is to mitigate this by optimizing for “cheap headcount”—often resulting in massive teams writing in verbose, weakly-typed languages.
But that optimization is a false economy. In this fast-paced session, we will bridge the gap between engineering elegance and business reality by examining the true Total Cost of Ownership (TCO) in complex domains. We will expose the “shadow payroll”—the hidden layers of engineering managers, manual QA testers, and incident responders required to babysit bloated polyglot architectures.
By framing Scala’s compiler as an automated compliance officer and its concise syntax as a tool for architectural leverage, attendees will learn how to identify the exact workloads where Scala wins. You will walk away with the financial vocabulary and organizational math required to prove to your stakeholders that a lean, elite Scala team is ultimately far more cost-effective than a sprawling alternative.
