Introduction

We are a small team of developers, which means every team member can bring something to the table and make a difference in the software we build and in the daily workings of our clients.

Having standards and following best practices for any programming language is essential for any development team. This keeps consistency across all the systems. Usually the readme.md file in any system private or open source is always your friend, most of the info related to the system is documented in there.

Expectations from Senior Developers

  • A senior developer understands and is aligned with the Propay Company Culture.
  • Seriousness firstly means "responsibility". Responsibility for your decisions, solutions, code, and communication with the team.
  • A senior developer is able to carry a message to Garcia: They can take the initiative when carrying out a difficult assignment.
  • A senior developer has experience; because they are able to learn from their mistakes.
  • A senior developer helps their team get better every day. E.g. by energizing his/her colleagues on group calls, setting an example of awesome code that awes the rest of the team, inspiring colleagues with his/her results/help, etc. etc.
  • A senior developer finds and fixes the root causes of the problem and not just the symptoms.
  • A senior developer can self-reliantly deliver working software.
  • A senior developer understands that their job is to provide solutions to problems, not to write code.
  • A senior developer knows their tools: IDE, OS/terminal, debugging, static analyzers, formatters, test frameworks, CI, CD, etc.
  • A senior developer knows how to choose the right tool and framework.
  • A senior developer actively employs the Boyscout principle and helps update this documentation ("always leave the campground cleaner than you found it")
  • Most importantly, a senior developer reminds us all, or reminds a given individual developer, when we do not live up to what’s written on this page, written in the Propay documentation, taught in the developer sessions, or considered a best practice among senior developers. A senior developer is thus a "guarantor" that we continually optimize our team spirit, fun, productivity, learning, results, impact on the world, and programming practices.

Short articles to read

Now, please read the following articles:

Edit this page on GitHub
Table of Contents