Principles
Atomiv has an engineering-oriented approach to software. Our belief is that a lot of software development can be systematized, and that we want to achieve organizational success without too much reliance on having to hire A-players. Thus, it is designed to work well both on teams with lots of seniors but also with juniors.
Atomiv is founded upon the following three principles.
- Quality principle
- Speed principle
- Standardization principle
Quality principle
Quality software is a prerequisite for producing software which works well, with minimal defects and with low maintenance costs, and overall providing a good customer experience. When projects don’t start with a quality architecture and accumulate technical debt over time, it reaches a point when there are too many bugs, the software is unusable, new features cause system breakdown, developers lose productivity and overall leading to customer dissatisfaction. It is essential that projects are started with a solid quality architectural foundation - this is exactly the core focus of Atomiv, to help you develop modular, flexible, extensible and maintainable software.
Speed principle
However, even though we recognize the importance the importance of quality, we are also familiar with the time pressures faced in software projects - to deliver early, to deliver fast, whereby in reality, in the short-term, development speed becomes more important than quality, even though quality is essential for long-term development speed. This is a major barrier for organizations looking to setup quality system architecture. This is where Atomiv comes in - it provides a template for the solution architecture as well as components to reduce development time.
Standardization principle
Last, but not least we come to standardization - the principle to standardize project structure so that we can systemically achieve quality and speed across our software projects. This also increases re-use and provides organizations with higher flexibility to organize development teams and incorporate new members, and avoids to the “re-invent the wheel” syndrome. It also makes project success a part of the organization, rather than relying on a few “talented” “A-player” individuals. Atomiv did not invent anything new, it simply took existing best practices and provided a standardized templated solution.
