> Traditionally, coding involves three distinct “time buckets”: > Why am I doing this? Understanding the business problem and value

> What do I need to do? Designing the solution conceptually

> How am I going to do it? Actually writing the code

This is why when people call programmers coders it feels wrong imo