It's not just about making changes and closing tickets

[suchona.kani.z]

This is where we talk about quality. Yes, the software has to work - but that alone is not enough. The software not only has to solve the problem, it also has to be well made. Measuring this is not always easy and the meaning of "well made" can vary from project to project.

There are certain fundamentals - complete documentation, extensible and flexible architectures, clean code and consistency, among others. Like all craftsmen and women, developers benefit from their tools. If they don't know a tool but need to learn it because it is the best tool, they will do so. In this way, developers are also responsible for what they create and for avoiding defects.

To deliver well-crafted software, one should use coding best practices. Software design principles and software design patterns are some tools that can be used for this. In addition, there are clean code principles slovenia consumer email list like SOLID, DRY, KISS and many more.


It's about trying to always meet the customer's needs, identifying problems and providing new solutions. In addition to technical solutions, the overall benefit of the software should be considered and one should not be afraid to make new suggestions and bring experiences.

You avoid shortcuts and the “I’ll clean this up later” mindset by maintaining a sustainable pace.

A community of professionals
The software craftsmanship principle is about communication and the community of developers. If you assume that developers are craftsmen, you should accept that this also applies to other people involved. For this reason, other groups of people who have to do with the software developed must also be treated with respect. You are creating software that will later have to be maintained. This maintenance affects other developers in the community. You show respect by, among other things, writing the code in a maintainable, flexible and fully documented way.

This not only helps other developers, but also reduces maintenance costs on the customer side, because maintaining chaotic code means more staff is required for longer periods of time.

In addition, the complexity of technologies continues to increase. Developers should work together to achieve success together - the key point is the exchange of knowledge and experience. This responsibility is not limited to a team, but as part of the software development community you are also responsible to other developers. Contributions to the open source community, activities on platforms such as Stackoverflow or writing articles and comments can be measures to spread knowledge and experience. The motto is: "We teach everyone who is willing to learn."