Design goes beyond just coding. The author argues that the current focus on whether designers should code limits the broader conversation about design’s role in the future, especially with the rise of AI and new tools. They question whether designers are becoming more like engineers and what that means for job titles and expectations. The core issue is understanding how design is defined across different contexts, as the term can mean various things depending on the industry and the individual’s approach. The author emphasizes the importance of clearly defining problems before jumping into solutions. Many design projects falter because stakeholders don’t agree on what the problem is. By articulating the problem and aligning with stakeholders early on, designers can avoid compromises that dilute the solution. This process involves questioning assumptions and understanding the context, which can be just as critical as the design execution itself. When it comes to creating solutions, the author separates the process into two stages: conceptual and execution. In the conceptual stage, designers explore different ideas and forms without committing to a final design. For example, in an issue tracking tool, they might consider how to represent projects versus issues. Once a direction is chosen, it moves into the execution stage, where the concept is built and tested. This hands-on phase can lead to new insights, prompting a return to the problem or concept if necessary. Ultimately, the author advocates for a balanced approach where the conceptual thinking doesn’t get overshadowed by the technical execution.