What counts as "code" or "programming"?This was an interesting topic between @stevekrouse and @pbiggar in podcast #43 (Unveiling Dark). Some of the contested areas were:* Incidental (accidental) complexity, vs essential "this is what it does" code
* Whether it looks like "code" / is symbolic
* Whether it's the boring / tedius stuff, or the "fun" part of programmingWhat does everyone else think?
Podcast idea: @stevekrouseRob Fitzpatrick, lost over $1 million USD. He has bankrupted 3 businesses. Because he did not know how to do user stories.The same is true for Microsoft, read Microsoft secrets, they had the same problem and used the same solution back in the 1990's.He has a book "The Mom Test". I assume he is happy to do an interview in exchange for a plug of the book.Video of him talking about the problem and solution. He says you should ask questions about current solutions.
Not sure if the topic is right for the pod cast. But feel that the problem he describes and the solution are important to trying to make programming more accessible.
I’m constantly dismayed by developers seeing one way to do things and then it’s seen as the only way things can be. The latest example is you want to do test-driven development of a new system? “cucumber is the only way to go”. Just imagine if they saw morphic and e-toys in squeak, and then learned about cucumber after that.
2 years ago
“Oh, we want to adopt best practices like gitflow”. (Now I feel extremely depressed.) These guys can’t imagine version controlling based on semantic features of the code - it’s all done with diffs of lines in a Unix-style filesystem like we’re in the 1970's. No progress is possible, and we definately haven’t heard of Envy/Developer.