{ "success": true, "comment": "\x3cdiv class=\"comment comment-published odd\"\x3e\n\n  \x3cdiv class=\"clear-block\"\x3e\n      \x3cspan class=\"submitted\"\x3eSun, 2009/03/08 - 4:15pm — \x3ca href=\"/users/ksu257\" title=\"View user profile.\"\x3eKSU257\x3c/a\x3e\x3c/span\x3e\n  \n  \n  \x3cdiv class=\"comment-score-div\"\x3e\n      \x3cspan class=\"comment-score-label\"\x3eScore: \x3c/span\x3e\x3cspan class=\"comment-score\"\x3e-3\x3c/span\x3e\n    \x3c/div\x3e\n\n  \x3cdiv class=\"comment-voting-controls\"\x3e\n    \x3cspan class=\"comment-promote\"\x3e\x3c/span\x3e \x3cspan class=\"comment-bury\"\x3e\x3c/span\x3e\n  \x3c/div\x3e\n\n  \n    \x3ch3\x3eSoftware Engineering (Development)\x3c/h3\x3e\n\n    \x3cdiv class=\"content\"\x3e\n      \x3cq\x3eIn free software world developers make all decisions because they really write code.\x3c/q\x3e\x3cp\x3eThere is an interesting article in the current (03/2009 P.24) \x3ci\x3eCommunications of the ACM\x3c/i\x3e that asks the big question: Is Software Engineering [really] Engineering?\x3c/p\x3e\x3cp\x3eWhether or not it is really engineering, developers need to realize that software development is a lot more than writing the code.  Writing the actual code should be only a small part of software development.  If it is engineering, then analyzing the problem and designing the solution are the important parts of the project.  Writing the code is only implementing the solution.\x3c/p\x3e\x3cp\x3eTo make my point clear: \x3cb\x3edesign is what is important.\x3c/b\x3e  You need to develop a good design \x3cu\x3ebefore\x3c/u\x3e you write the code.\x3c/p\x3e\x3cp\x3eThis mantra of FOSS has come to mean that those that write the code do the system analysis and project design.  Why should it be that way?  Does knowing a programing language automatically make someone good at analysis and design?  I don\'t think so.            \x3c/div\x3e\n  \x3c/div\x3e\n\n  \x3c/div\x3e\n" }