> So many people stop when it works, without understanding why it works. Most work environments train programmers to act that way. I find this is especially th

> So many people stop when it works, without understanding why it works. Most work environments train programmers to act that way. I find this is especially the case at workplaces that (sort of) follow scrum and agile. In most of these places, junior to mid-level programmers are given a task to work on that already has an hours estimate on it. Managers like to optimize efficiency and programmer time, so that estimate is always tight. Asking why we're doing this task is rarely received well and the tight time estimate means there's barely time to make the change work in the first place, let alone understand why it works. We're literally training our devs not to be top devs.