Some people may think that a good or a bad architecture doesn't affect the behavior of the program the user sees, but that is wrong. Although a good architecture helps the developers, it also reflects the quality of the final program, a good design. And as Steve Jobs said "Some people think design means how it looks. But of course, if you dig deeper, it's really how it works". and this can perfectly fit in this reading.
The author relates various types of software architecture with types of pasta. I like the relation, because code is pretty much like pasta, it can be a mess if you don't care about anything, or it can be something with an interesting shape, but at the end is pasta.
"A good architecture leaves space for maneuverability, extension, and modification". That is one key concept and in my short coding experience I can say that phrase holds the truth. Sometimes I've written code in the rush, just worrying about delivering it without paying attention to possible changes in the future; and that mistake has cost me a lot of time.
For example:
I recently programmed an Android app in which I spent a lot of time replicating code over and over, getting errors where they shouldn't be and driving me very mad. Then, after struggling I realised that what I needed was to implement a Java interface for my problem. Finally, when I did that, everything was more clear and without errors, because that was the correct approach. And what is best, the next time I face a problem like that, I know how to quickly solve it, because now I know the perfect tool for it.
But obviously not everything solves with interfaces, we need to find the correct tool for our problem. That's why these readings are so important, because show you various ways to find the correct tool for your Flying Spaghetti Monster.
No hay comentarios:
Publicar un comentario