Skip to content

Commit

Permalink
Introducing Pair-programming.
Browse files Browse the repository at this point in the history
  • Loading branch information
axelabhay committed Nov 17, 2023
1 parent 52b3e10 commit 890d5d1
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion content/docs/how-we-work/coding-principles-standards.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: When working on our projects, we prefer to use libraries. We adhere

# Coding Principles and Standards

When working on our projects, we prefer to use libraries. We adhere to our principle, [proudly invented elsewhere](../../principles/proudly-invented-elsewhere), implying that we value and utilize community libraries. However, the thrill of our work often lies in the unique requirements that call for custom solutions beyond these libraries.
When working on our projects, we prefer to use libraries. We adhere to our principle, [proudly invented elsewhere]({{< relref "../principles/proudly-invented-elsewhere" >}}), implying that we value and utilize community libraries. However, the thrill of our work often lies in the unique requirements that call for custom solutions beyond these libraries.

At Axelerant, we write code not only to solve a specific problem but also to provide a reusable solution that can be used at a community level. We have principles that can guide us to the desired code standards.

Expand Down Expand Up @@ -45,3 +45,7 @@ In our projects, we strictly adhere to the established coding standards. These s
- We stand behind the YAGNI (You Aren’t Gonna Need It) philosophy and avoid “gold plating”.

- When writing code, our code should solve ONLY and EXACTLY the use case that we are trying to support. In many instances, we have a desire to make things MORE FLEXIBLE in the FUTURE but that is code we will have to support without knowing whether any of those use cases will ever come up. Another big reason for wanting to be FLEXIBLE is that refactoring is hard, and it feels easier to have flexibility at the front, but that is why we write automated tests, so refactoring will not be as painful.

## Pair Programming

Pair programming is a software development technique where two developers work together. Sometimes it is proven helpful to debug code collectively by connecting on calls, sometimes [rubber-ducking]({{< relref "../common-areas/debugging/#rubber-ducking" >}}) tactics are clearly achieved through this approach. Pair programming generally helps in improving code quality, including productivity and communication skills.

0 comments on commit 890d5d1

Please sign in to comment.