S/W Design and Arquitecture

The podcast about Software Craftsmanship in which Robert Martin talks was entertaining, it was recorded in 2009 and it makes sense now a days (2017). It was interesting how it talked about the manifesto and the tools that every programmer should get used to.  Talking about the manifesto, I'm always thinking on the outcomes that could bring every change in any program that is being coded. Thinking that everything can be molded fast is a wrong idea that most people don't get. They want new features and they want them now. Not taking the time to make unit tests and just ship it will doom a project because it will start to diverge and start changing in ways that will make it really difficult to solve if a bug arises or a new feature is asked.  And now, talking about the tools, I at least thought about learning how to use a terminal and a text editor as Sublime Text, Visual Studio, Atom first. The IDE makes it so magical that sometimes a programmer doesn't know what to

In every coding project there are people that will write it and some others will design it but without any question, both of them should know that coding isn't trivial, design errors or coding errors will occur and it is essential to have a risk plan in case that something happens. This allows to have a stablished way of dealing with the problems that will appear as the project grows. Depending on the scope of the coding project, if it will be a program that has some components (an API, a database, users, security, etc.), it is important to design it before beginning to code it. This allows to design it to be scalable, secure, maintainable, and error-prove. If the project is just to write a a program that will resemble a calculator, it is just fine to code it as you go. This means that depending on the complexity of the project, it is necessary to define certain documents to establish the foundations that will allow to create bigger projects (more modules, more people assigned t