I would like to share with you the story how I became a software tester and why I chose this profession. I will present the position, responsibilities and advantages and disadvantages of this profession.
This is the last article related to the set of SOLID project principles. The DIP principle is the most useful of all in terms of its relevance to the creation of strong classes and good architecture of the whole system.
In my previous article, I described the recruitment process at Evertop. Today I will continue the topic, focusing on one important stage of recruitment, which I also mentioned previously, the last but not least – the onboarding process.
The principle relates to two main aspects of object-oriented programming. First of all, it highlights the importance of correlation between the classes with the same parent. Secondly, it helps to understand correctly the essence of object-oriented programming and virtual mechanisms, which support the process.
Have you ever seen a class method in your project, the core of which would be one line only: throw new NotImplementedException()? Is this the right solution? Could such a code cause an issue?
For the past two months we have been trainees at Evertop, and we want to share our thoughts and experiences that we have encountered so far, starting from the very beginning – the recruitment stage.
That is the second article from the series about SOLID principles. This time I should give you more details about the Open-Closed Principle. The element of software should be locked for modification but open to extension. Uncle Bob himself used to say: “Good architecture reduces the amount of modified code to the absolute minimum. Ideally to zero”.
SOLID principles are regarded as one the best practices in programming. We hear about them all the time. Unfortunately, it seems to me that these rules are often misunderstood. I’ll try to present them in the series of five articles, one article for each rule.
I’m sure that for many of us looking for a new job is quite stressful. And it isn’t strange at all but let’s think why it is so? As Dan Brown said in one of his bestseller books „we all fear what we do not understand.”
I have seen once such a meme: “If debugging serves to remove errors from the code, programming certainly involves inserting bugs into the code.” There is some truth in it. Modern IT systems implement a lot of very complex processes, it is very easy to make a mistake.
The world is changing faster than ever before, and especially IT world. As software developers and engineers we should „sharpen our saw” not only to be better and better but also to be on a roll with new technologies, frameworks and libraries. The same as athletes who keep in shape and train harder to get better, faster and stronger (yup, I like Daft Punk), we should train ourselves.