| author here. Thanks for your thoughtful comment. > [meta] The title of this article sucks, really, it's a bait, It was not intended. The title just tries to summarize the post. Still, so much to learn about writing! >> Lots of rework happens because of miscommunications with the user. Other times, the user doesn’t fully understand their problem (there’s not much we can do about this) > Agreed. That's where "lean programming" comes into play. If you have the capacity to make the code change as requirements change then I think the issue is pretty much solved. However, not all languages/solutions are equal in that matter. Obviously TDD, Agile techniques help. I have a note on Agile. As I mentioned, I believe Agile or lean programming to be solutions. They don't question anything about the status quo, they just try to cope with it. It's good, it's an improvement. But an incremental one from the perspective of the stack of poker chips. >> If we assume that typing code is the way to program, we will never look for better alternatives.
> Typing code is a medium. The fact is, for an engineers it usually the most convenient way to create a program. Turns out that the medium has an huge effect on our understanding. https://signalvnoise.com/posts/2976-bret-victor-thinks-math-... >> Building software is 90% a human problem
>Agreed, but like everything humans do. The first rule of the tautology club is the first rule of the tautology club. Of course! the idea is to make programming something that humans don't do, or at least, reduce how much human involvement you need. Humans are the weaker link in software development, we should do like with other things that humans don't do anymore, figure out a solution and put our time to do something else. |
WALL·E would disagree, and so would I.