In this BONUS episode, we explore a thought-provoking LinkedIn post by John Crickett that challenges a fundamental misconception in software engineering. John shares insights on why engineers should focus on problem-solving rather than just coding, how to develop business context understanding, and why this shift in perspective is crucial in the age of AI.
Beyond Writing Code: Understanding the True Value of Software Engineering
“A lot of us come to software engineering because we care about building, and missed the goal: solving a problem for a customer.”
John Crickett explains the fundamental disconnect many software engineers experience in their careers. While many enter the field with a passion for building and coding, they often lose sight of the ultimate purpose: solving real problems for customers. This misalignment can lead to creating technically impressive solutions that fail to address actual business needs. John emphasizes that the most valuable engineers are those who can bridge the gap between technical implementation and business value.
In this section, we refer to John’s Coding Challenges and Developing Skills websites.
The Isolation Problem in Engineering Teams
“We have insulated people from seeing and interacting with customers, perhaps because we were afraid they would create a problem with customers.”
