This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned on Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series.
Robert C. Martin (AKA Uncle Bob) published his ideas about Clean Architecture back in 2012, in a post on his blog, and lectured about it at a few conferences.
The Clean Architecture leverages well-known and not so well-known concepts, rules, and patterns, explaining how to fit them together, to propose a standardised way of building applications.
Continue reading “Clean Architecture: Standing on the shoulders of giants”
This post is my personal notes of the talk “Clean Code 3: Functions” by Robert C. Martin.
Recently I revisited this conference talk Uncle Bob gave about functions/methods, where he gives us a set of guidelines on how to do them clean. These are the main guidelines I gathered: Continue reading “Clean Code 3: Functions by Robert C. Martin (Uncle Bob)”
“The reasonable expectations of your new CEO”
There is software everywhere! And it must be work! It must not fail! People depend on it!
Continue reading ““Expecting professionalism” by Robert C. Martin”
This post is my personal notes of the talk “The responsibility of knowing” by Robert C. Martin.
The responsibility of knowing
Engineers are creators, inventors, they know how to build things, how things work, what can fail, what will fail, when it will fail. Engineers have the knowledge, and that means they have great power, and “with great power comes great responsibility”.
Continue reading ““The responsibility of knowing” by Robert C. Martin”
This post is my personal notes of the talk “Clean Code I: Arguments” by Robert C. Martin.
Clean Code 1: Arguments
Bad code slows you down. You write it under business pressure, because there is no time, the client needs the feature yesterday, the feature was sold before it was build, maybe even before it was ever thought of by the team, or any other reason. But the real truth is:
There is not excuse to write bad code!
Continue reading “Clean Code I: Arguments by Robert C. Martin (Uncle Bob)”