Anti patterns in Software Product Development Evaluating
Universities teach us algorithms and data structures. Sometimes lectures can talk about design patterns or multi-threaded programming. But I didn’t hear about how to correctly evaluate labor costs. Meanwhile, every programmer needs this skill every day. There is always more work than can be done….
CI / CD using Jenkins on Kubernetes
Here are already several articles on our website about jenkins, ci / cd and kubernetes, but in this I don’t want to concentrate on analyzing the capabilities of these technologies, but check their simplest configuration for building the ci / cd pipeline. I hope that…
GitLab Shell Runner. Competitive launch of test services using Docker Compose
This article will be interesting for both testers and developers, but it is aimed more at automations who are faced with the problem of configuring GitLab CI / CD for integration testing in conditions of insufficient infrastructure resources and / or lack of a container…
Specification by Example: Illustrating using examples, Validation & Green Tests
Natural languages play a trick on us. They leave space for interpretation, misunderstanding, and sometimes require knowledge of the subject area and / or specific slang in order to understand what is the point. A slight misunderstanding can lead to deadlines and a large number…
Specification By Example – BDD for Pragmatists
For the product to get a good position in the conditions of the modern IT market, we, developers, need to achieve two goals. Make the right product (exactly what the market wants to buy) and make the product right (without spaghetti code, bugs and other…
Pitfalls of GDPR
The main mistake in the implementation of GDPR is to rely on the strength and resources of only one person. A common practice is to expect independent work on the Rules from a lawyer. In such a situation, if he doesn’t have enough serious position…
Docker: NOT useless advices
In comments to our article “Docker: bad advices” there were many requests to explain why the Dockerfile described in it is so terrible. Summary of the previous story: two developers in a hard deadline made the Dockerfile. In the process, Ops – let’s call him…
Good, bad, evil – testing beginners in a project
Tests are necessary, first of all, in order to convince everyone (including ourselves) that the program behaves as it should in test situations. Secondly, they ensure the performance of the code covered by tests in the future. Writing tests is a useful process, because during…
Cost effective code. Part 2
Graceful Degradation for low value code, tricky YAGNI The business value of the developed application is not evenly distributed throughout the code base. This statement is true for the amount of development effort. Until recent time, IE6 support was an example of a huge waste…
Cost effective code. Part 1
Software development is an area, which is always at risk. In our sphere, when one or several risks occur, the delivery time for the working version may change not by the usual and comfortable 10-20%, but by all 150-300%. And we must admit that this…