I smoothly move from requirements analysis to agile development. I like to start from clearly defined requirements, but I also understand that the client often forms an idea about the given product only during development. I always prefer fast feedback with regards to the current MVP.

Before development can begin, everything must first be set up properly at the project level. I'm a proponent of minimalism, most project management can be handled using Clockify and Gitlab. The clearly preferred platform for development and deploy is Linux.

A properly set up development environment is essential. If the CI/CD pipeline does not force the programmer to follow established conventions and meet predefined tests, it is impossible to embark on full-fledged development.

Measure twice, cut once is doubly true in commercial development, as it saves both our time and, above all, our clients' money. Therefore, it is always advisable to think architectural decisions through. I consider it essential to continuously practice refactoring, adhering to clean-code and writing documentation even in the form of commented code.

An important factor influencing the development of the project is the distribution of responsibilities and subparts of the project among the individual developers. I believe that developers should interfere with the code as little as possible during development. At the same time, they should be aware of what the other developers are creating. We regularly go through code-reviews for better code maintenance.

Once the development is in full swing, it is important to set certain milestones and also regular meetups to keep the client in the loop. The client is handed the highest quality product that is sustainable over the long term and it is easy to bring in other developers who will be able to deliver the same quality the client is used to as soon as possible.