Loading…

software engineering

Subscribe to the podcast

Get The Stack Overflow Podcast at your favorite listening service.

One quality every engineering manager should have? Empathy.

Ryan talks with senior engineering manager Caitlin Weaver about how her childhood fascination with computers led to her leading CLEAR’s Cloud Infrastructure Engineering team, her experiences in DevOps, the role of empathy in engineering management, and how the platform engineering landscape is evolving.

“Countries are coming online tomorrow, whole countries”

Ben and Ryan are joined by RJ Tuit, Head of UI Platform and Client Architect at ClickUp, formerly an engineering director at Microsoft. They talk about ClickUp’s vision for a comprehensive productivity platform, the complexities of measuring productivity and UX in software development, how to navigate the hype around AI, and more. Plus: What it was like scaling Microsoft’s cloud services to meet the unprecedented demands of a global workforce in quarantine.

The reverse mullet model of software engineering

Ben and Ryan are joined by software developer and listener Patrick Carlile for a conversation about how the job market for software engineers has changed since the dot-com days, navigating boom-and-bust hiring cycles, and the developers finding work at Walmart and In-N-Out. Plus: “Party in the front, business in the back” isn’t just for haircuts anymore.

Using stretch work assignments to help engineers grow

Stretch work assignments are tasks or projects that are a bit beyond an engineer’s current skill or knowledge level and that allow them to improve and learn new things. When done correctly these assignments serve a dual purpose of providing learning opportunities for your engineers, while at the same time completing a project or task that will help your company.

Requirements volatility is the core problem of software engineering

It's now been more than 50 years since the first IFIP Conference on Software Engineering, and in that time there have been many different software engineering methodologies, processes, and models proposed to help software developers achieve that predictable and cost-effective process. But 50 years later, we still seem to see the same kinds of problems we always have: late delivery, unsatisfactory results, and complete project failures.