Re:Ask HN: Programmers vs. Developers vs. Engineers
by varjag on Wednesday July 28, 2010 @03:34AM
(#1553820)
I would take an opportunity to disagree with your definition of software engineering. It is not easy to write a quick prototype for many, many things out there. Nor there is an accepted engineering practice following which allows us to build arbitrary, robust (in say, civil engineering sense of "robust") products.
Re:Ask HN: Programmers vs. Developers vs. Engineers
by keefe on Wednesday July 28, 2010 @10:42AM
(#1554417)
I'm sure there are some things that are difficult to prototype, but typically you can special case the difficult parts. Regardless, if the prototype is difficult the product will be even harder.
I think there are basically accepted practices. If the software has a UI, use MVC and separate all the UI bits. Test coverage gives a good metric for product quality and everything but the UI should be well covered. Reasonable performance tests should cover multiple users, load etc.
I'm not sure what civil engineer considers robust, but I think this approach basically works.
Ignoring job titles and just talking about skillsets :
programming : taking a specification and coding it up, for example build this b-tree, web-app, whatever.
developing software : typically, this implies more participation in the design process. Developers don't just make software work, they help decide what it does.
software engineering : Writing a quick prototype for anything is easy. Writing a software system that is well tested and stands up under load requires engineering.