Welcome back to TopSecretProject.
I have been revisiting one of my favourite explorations of software architecture: The Big Ball of Mud.
The key take away for me is the following message about developing features first:
You need to deliver quality software on time, and under budget.
Therefore focus first on features and functionality, then focus on architecture and performance.
2 comments ↓
Definitely. In fact, sometimes following such principles and focusing on simplicity can end with very elegant pieces of code which ‘do the job’, rather than the grander preconceptions which a mind can build up with preconcceptions of design and architecture.
thats a slippery slope though – if you build to a feature spec, you might loose sight of scalability.
I’d actually propose you focus on structural base functinoality, but leave features for later, then build a base architecture that is abstract and truly object oriented.
and presto, you’re on your way to great software.
except, doing things this way require investments in frameworks that aren’t immediately visible by business owners, and thus rarely get funded. and so we go back to the old convoluted way of building software feature-by-feature, until it’s a BIG BALL OF MUD.
…sigh…
Leave a Comment