-
Protected: Why we need modules (aspect three)
There is no excerpt because this is a protected post.
-
Why does the quality of software code suck?
There are many factors that impact negatively software code quality: lack of awarness of complexity Complexity has a major negative impact on software quality. Programmers see and feel this complexity, but are not fully aware that it is growing incredibly fast and where it comes from lack of knowledge Many programmers do not know where…
-
The need for continuous improvement of solution to achieve productivity
During the lifetime of IT project requirements are constantly added. We can think of requirements as dots and connections (for IT people: dots represent the classes or microservices and connections represent the interactions/dependencies): At the beginning of the project there are a few requirements (above), complexity is low. After a few sprints the number of…
-
Protected: One word many meanings – context intro
There is no excerpt because this is a protected post.
-
Protected: What is a model?
There is no excerpt because this is a protected post.
-
Well-designed system starts with domains
Nowadays, many software applications and systems are so complex (huge number of requirements) that without the proper designing very fast are built a ‘big ball of mud’ or ‘distributed monolith’ – systems that is very hard to maintain and extend. Designing is really important. Let’s see why. How to properly design a system? First, you…
-
Negative consequences of large amount of information in IT project
Big knowlegde is required to build a software. We all know that, but in some IT projects amount of knowledge and information required to do even simple tasks is so huge that cause low productivity, low quality and people dissatisfaction. The relation is like that: I think it’s quite obvious. The more knowledge and information…