Sunday, June 7, 2015

Why how and not why?

Software development in 2015 requires that you rapidly learn vast numbers of technologies enough to sew them all together.The most frustrating part of trying to learn all this stuff is that most documentation is focused on how to do something but not why you are doing it. Rarely is context given of why what is being explained needs to be done, only how it is done.Very frustrating. If you are writing software documentation please start every page, every paragraph, every example, every solution, with why before how.