Definitely, a great read, addressing the mammoth in the room > When teaching programming, we should let people make these mistakes, and then show them the tool

Definitely, a great read, addressing the mammoth in the room > When teaching programming, we should let people make these mistakes, and then show them the tools to correct them. This was one of my pain points when I was in college studying CS. It was killing me to have the teacher just dictate that programming lecture without showing what problems it solves and/or how difficult our lives would be if we don’t get it right. I still recall that interfaces lecture where the teacher keep telling us to declare some sort of class with some methods but without implementation!! Any class could then benefit from this! How/Why?! I wasn’t able to get this interface thing until I graduated and worked on a personal C# project with WPF where I designed it with a basic architecture of plugins/addons that got loaded at runtime, those plugins should all have some common functions that can be called by the host app, only and only then, I fully understood interfaces and how/why/when to use them. At that point, I wished I can go back to college, explain this concept to students and get back! I believe the reason why college teachers struggle to explain such concepts in a better way is their lack of experience in the field.