HTTP provides some authentication schemes like: Basic, Bearer, Digest, HOBA, Mutual, Negotiate, OAuth, etc. As described in the RFC.

Reading this book has been an interesting experience. This book can give you some light to many different topics in a software developer’s life. John Z. Sonmez tells his story. You can learn very interesting lessons. I recommend not only read the book, but also discover his story the years after writing it.

Be motivated or not be? That is the question. Had you ever thought about what stimulus in your life triggers your motivation?

Thease are some examples of the dotnet dependency injection engine setup, in some different kind of projects.

I like the long road metaphor. During my journey, I like to reach my apprenticeship goals, it’s the way I feel I progress. But, I have got full-time work, a family and a life to attend.

This book has the responses to many questions I asked myself during the last year of exploring DDD. My team and I had te opportunity to discuss and apply many of the concepts and patterns and dynamics of this book in our recent projects. Definitely, give it a try is a recommended experience.

When I was at the university, I learned that software development principles can be classified at different levels, depending on the impact that they affect the structure of a software project. This means that they have a different use, different abstraction level, and different difficulty. So, if you want to learn this discipline in deep, you can know where to start, according to this hierarchy.

Why this book?

During the last years, I had been in Software Craftsmanship conferences in Pamplona, Madrid and Barcelona, and some editions of the Socrates Canaries (Software Crafters and Testers Conference). I have participated in some editions of the Global Day of Coderetreat, and some Coding Dojos of the local Gran Canaria local community of developers.

When you develop you are only sitting in a chair, in front of your screen, writing lines. Once and again the same commands and numbers.

This is what a person that is watching you from outside see. Probably thinks that programming is based in to learn commands and write them. That you probably are listening to music while programming to fight the tedious work of writing thousands of times the same lines every day. Maybe many people think that software development it’s a purely mathematical, methodic and antisocial work. Every day is the same, same screen, same operations, and the same game rules.

But actually, you are just watching the code, you are thinking. Thinking in your next step to sculpt a new feature or just to improve. Improve the legibility, the performance, the team or just you. You are immersed in the “gold rush”, you are looking for the perfect code. The most optimal solution, the easiest to implement, the less expensive or the one that brings more value.