👋Introduction
About us
We are Leapwise, a team of 20+ individuals dedicated to building products from scratch while prioritizing expertise, integrity, professionalism and authenticity in everything we do. Consequently, while working in technology-intensive industries, we are committed to development by industry guidelines, effective project delivery, knowledge sharing and, last but not least — giving back to the community. For that reason, we decided to reveal a good chunk of our internal coding guidelines to you — our colleagues, clients, or anyone else curious about our development process.
The idea behind this handbook
The handbook originated as a continuation of our internal coding guidelines whose purpose is to unify our way of working by harmonizing languages, frameworks and terminology within the development team. We think that ensuring language uniformity and universal principles to engineering practices is critical for effective communication among team members.
Internally, we have backend and frontend guidelines, as well as employee experience documentation, which we constantly update and refine. These internal documents come in handy when someone new joins the team, but also when we want to remind ourselves of certain practices.
We are very focused on systematic work and knowledge sharing within the team, so we decided to extend this mindset externally to create publically available, free handbooks.
The purpose of the Backend Handbook
Besides sharing our internal development process, we wanted to give out certain practices we have encountered over the years while working on various projects across diverse industries, ranging from telecommunications to cybersecurity and the Internet of Things.
It is a combination of best practices - covering topics such as implied agile, clean code, clean architecture, SOLID Principles for Programming and Software Design, testing principles - and concepts we developed internally at Leapwise.
We hope you find it useful and stick around for new content we'll produce in the future. 🙂
Last updated