Re:Software Engineering ≠ Computer Science (2009)
by chii on Monday August 07, 2017 @05:45AM
(#14946330)
> every situation is novel
this is the point i m contesting - that most situations aren't as novel as the stakeholders think it is. The failure happens because the assumption that it's novel is there!
Re:Software Engineering ≠ Computer Science (2009)
by Illotus on Monday August 07, 2017 @08:41AM
(#14947062)
In general there may not be that much novelty per project, but that isn't the novelty that one needs to worry about in software projects. The relevant novelty is the novelty to the project team. Also lot of the novelty comes not from the technical side, but domain and organization that will be using the software.
Re:Software Engineering ≠ Computer Science (2009)
by mattgreenrocks on Monday August 07, 2017 @03:05PM
(#14950270)
This is a big argument in favor of experienced devs, who have deep technical and domain expertise.
This isn't evident at all. In software, every situation is novel, so there is no room for repeatable processes.
You can build a "bridge library" once and tweak it for each situation, but you never need to develop a rigorous process to build that library again.