About a year ago I was very interested in learning as much as possible about the subject and gathered as much information as I could about it. I watched several conference talks and I read several articles from very knowledgeable and experienced people, like Martin Fowler, Fred George, Adrian Cockcroft, or Chris Richardson, in order to learn as much as possible about microservices, and this post is the result of that.
This post talks about:
Continue reading “Microservices architecture: What the gurus say about it”
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)”
Simon Brown talks to us about how, now days, we have many diagramming tools and concepts which some of us like to use, and sometimes are even imposed upon the developers by the corporations managers, who actually have no idea of technicalities and the usefulness or not of those diagrams. However, despite the tools and concepts we have, when we create a diagram of the architecture of a software program we are developing, most of the time it ends up not matching the actual code, we can not see the architecture in the code.
Continue reading “Software Architecture vs. Code – by Simon Brown”
“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)”