Backend Handbook
Leapwise
  • 👋Introduction
  • Software Design Principles & Clean Code
    • Atomicity
    • Modularity
    • Hierarchy
    • Loose coupling
    • Asynchronous programming
  • Development Practices
    • JavaDocs
    • Technical Debt
    • Testing Guidelines
      • The Importance of Test Automation
      • The Testing Pyramid
        • Unit Tests
        • Integration Tests
        • End-to-End Tests
      • Mutation Testing
      • Contract Tests
        • REST Controller Contract testing
        • OpenAPI Contract testing
      • Testing Frameworks
        • JUnit 5
        • Testcontainers
        • Mockito
      • Writing Clean Tests - Best Practices
    • Common library
    • Generic CRUD
    • Update Facade
  • Development Tools & Environment
    • Monitoring
    • Performance tuning
    • Multi-tenancy & Configuration Management
    • Git practices
    • CI/CD
    • Maven
  • Project Management
    • Jira
    • Confluence documentation
    • SCRUM
    • Our ways of working
  • LIFE AT LEAPWISE
    • Introduction
    • Who are we?
    • What do we do?
    • Our values
    • Hiring process
      • Hiring: A Mid Frontend Developer's Point of View
    • Benefits we offer
    • Onboarding process
      • Onboarding: A Senior Digital Marketing Specialist's perspective
    • Mentorship program
    • Career development
      • Trainings & certificates we offer
      • Career development: A Senior Software Developer's Insight
    • Community building
    • Juniorship
    • First-hand info from our first team member
    • Join our team
Powered by GitBook
LogoLogo

Company

  • About
  • Culture
  • Services

Insights

  • Leapwise Newsletter
  • Blog

© Leapwise

On this page

Was this helpful?

  1. Development Practices

Common library

Common library serves us two key purposes. Firstly, it's our go-to helper for making coding faster and more efficient. Secondly, it encourages us to produce more reusable code and promotes generalization in our development process. In other words, it's like our trusty assistant, helping us work smarter and encouraging best practices that lead to better, more maintainable code.

Let's begin by exploring its efficiency-enhancing attributes. It's like having a toolbox full of useful tools that we can use repeatedly in different projects. It saves us time by avoiding the need to write the same code from scratch every time we start a new project. Instead, we can just grab what we need from the library and use it right away. It makes our coding life easier and faster!

This library is tested over and over again in different projects, so we know it works well. Sometimes, the code in the library might not do exactly what we need. But that's okay! We can add our own features to it. This makes the library even better for future projects because it has more tools to work with. Overall, using common libraries saves time, makes our work easier, and helps us build better software.

PreviousWriting Clean Tests - Best PracticesNextGeneric CRUD

Was this helpful?

Page cover image