4 ms·
Curious if the author has read anything by Watts Humphrey? He spent his entire career at SEI arguing this point and attempting to develop the tools and process
by zenogais 11y ago
Curious if the author has read anything by Watts Humphrey? He spent his entire career at SEI arguing this point and attempting to develop the tools and processes to bear it out. This article reads like a repetition of his arguments from A Disicipline for Software Engineering (1995).
- nickpsecurity 11y agoI learned in a discussion with "kragen" that "software engineering" sort of took on a life of its own that turned into a nightmare of management-focused stuff harmful to programming. Most programmers, especially mainstream crowd, have an aversion to the term from the permanent association. I started saying CompSci and focusing on prior techniques rather than "engineering" due to that permanent scarring. As in my other comment, I just focus on specific techniques and processes that help programmers do their job with evidence they work. It's my suggestion to you. I'm going to try to dig up and read that paper out of curiosity as I know many useful things came out of software engineering research. Most won't, though, the second they see "SEI" or "software engineering." So, might be best for us to just drop that and focus on improvements to "programming" or "development" with specific techniques.
- struppi 11y agoOriginal author here (sorry, was in bed when it came to the front page ;) ) I did not read that paper (book?), but will add it to my "To Read" pile. Thank you ;)