Individual software development

Our agile development teams are specialised in implementing sophisticated IT systems in a complex environment. In close cooperation with the customer, systems are created in short cycles that are powerful, reliable, flexible and secure. The basis for this is well thought-out software architectures and a suitably designed infrastructure.

Agile development processes à la SCRUM require not only a mature build and deployment infrastructure, but also the appropriate “mindset” and the necessary “skills” in the entire development team.

In order to maximise the efficiency and quality of the development teams and to optimise the coordination with our customers, we generally refrain from “outsourcing” or “nearshoring”.

We are convinced that developer hourly rates play only a very subordinate role in the total costs of an individual software development. Much more decisive is how quickly and, above all, how reliably a production-ready solution is actually created. In our experience, this is where the wheat is quickly separated from the chaff.

• For teamwork, we rely on a Git workflow with merge requests and peer reviews.
• The individual developers have long since internalised guidelines such as “SOLID”, “Clean Code” and “Test Driven Development”.
• For Continuous Integration and Deployment we work with GitLab CI and Jenkins respectively. Due to the variety of target environments for our software systems, we are also increasingly using Docker solutions.
• For static code analysis we use tools like SonarQube.

Although our experienced developers usually master a very broad spectrum of programming languages, frameworks and tools, the following main areas of focus have emerged at 4Soft, not least due to many years of experience:

Passende Beiträge aus unserem Blog

Clean Architecture

26.04.2019

Architectural styles such as Clean Architecture by Robert “Uncle Bob” Martin or Hexagonal Architecture by Alistair Cockburn have attracted increasing interest in recent years. They aim at being able to develop and test the technical core of an application independently of frameworks, databases and other infrastructure. In addition to improved testability and maintainability, this approach also allows infrastructure components to be defined at a late stage and easily replaced by others at a later date. The article explains the disadvantages of traditional three-tier architectures and the improvements that can be achieved with Clean Architecture.