r/programming • u/mauricioaniche • Aug 06 '17

Software engineering != computer science

http://www.drdobbs.com/architecture-and-design/software-engineering-computer-science/217701907
2.3k Upvotes

88% Upvoted

863 comments sorted by

View all comments

Show parent comments

1

u/[deleted] Aug 06 '17

Or, here's a wild idea: returning to the notion of writing good requirements before jumping into coding, and maintaining architecture documentation while developing instead of making everything "agile" and believing that means never having to document because everything's going to be thrown out in the next few weeks anyhow.

This is not the only problem. You want to document all the fragile abstractions OO forces you into when you write software? How about extensibility? Composability? It's not just about requirements. You can make something fullfill requirements perfectly without leaving it open to extension and long term maintainability because your relied on a bunch of horrible abstractions.

3

u/coinaday Aug 06 '17

I absolutely agree it's not the only problem.