{"id":527,"date":"2006-08-12T22:41:24","date_gmt":"2006-08-13T03:41:24","guid":{"rendered":"http:\/\/blogs.law.harvard.edu\/hoanga\/2006\/08\/12\/the-state-of-software-engineering\/"},"modified":"2006-08-12T22:41:24","modified_gmt":"2006-08-13T03:41:24","slug":"the-state-of-software-engineering","status":"publish","type":"post","link":"https:\/\/archive.blogs.harvard.edu\/hoanga\/2006\/08\/12\/the-state-of-software-engineering\/","title":{"rendered":"The state of software engineering"},"content":{"rendered":"<p><a name='a645'><\/a><\/p>\n<p>If you&#8217;re curious on one person&#8217;s viewpoint on software engineering as a<\/p>\n<p>discipline (academic and professional) this is a very nice summary \/ rant<\/p>\n<p>on it.  One minor niggling point is that I think the author could spend <\/p>\n<p>a little time fixing small grammatical mistakes.  Since the mistakes <\/p>\n<p>make a serious criticism like this look a little childish.  But only on the<\/p>\n<p>surface.  Here&#8217;s a choice<\/p>\n<p>snippet:<\/p>\n<p><em><\/p>\n<p>First, let&#8217;s touch on requirements gathering. No where in the book did Pressman<\/p>\n<p>illustrate how most engineers actually get their requirements. He presented<\/p>\n<p>some idealized scenarios, and correctly illustrated the benefits of use cases.<\/p>\n<p>But in the real world, most requirements come from emails and rough wireframes.<\/p>\n<p>Assuming that we can start by writing the specification is folly. What we<\/p>\n<p>should be studying is how to turn a screen shot created in Photoshop in to a<\/p>\n<p>real specification. Engineers need to learn how to annotate a screen shot with<\/p>\n<p>input validation rules. They also need to error messages and edge cases. And<\/p>\n<p>they need to do it with the understanding that their stakeholders don&#8217;t know or<\/p>\n<p>care about such matters unless you bring it up to them first.<\/p>\n<p><\/em><\/p>\n<p><a href=\"http:\/\/grauenwolf.bloggerteam.com\/entry.php?u=grauenwolf&amp;e_id=37125\"><\/p>\n<p>Read it yourself<\/a><\/p>\n<p><\/p>\n<p>Kudos to <a href=\"http:\/\/joel.reddit.com\">Joel&#8217;s Reddit page<\/a> for this one<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you&#8217;re curious on one person&#8217;s viewpoint on software engineering as a discipline (academic and professional) this is a very nice summary \/ rant on it. One minor niggling point is that I think the author could spend a little time fixing small grammatical mistakes. Since the mistakes make a serious criticism like this look [&hellip;]<\/p>\n","protected":false},"author":704,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1212],"tags":[],"class_list":["post-527","post","type-post","status-publish","format-standard","hentry","category-tagme"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/527","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/users\/704"}],"replies":[{"embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/comments?post=527"}],"version-history":[{"count":0,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/posts\/527\/revisions"}],"wp:attachment":[{"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/media?parent=527"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/categories?post=527"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/archive.blogs.harvard.edu\/hoanga\/wp-json\/wp\/v2\/tags?post=527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}