Professional expectations

This is part of the Semicolon&Sons Code Diary - consisting of lessons learned on the job. You're in the workflows category.

Last Updated: 2022-12-01

I was thinking about what specifically makes someone professional in their coding abilities and came up with a list for the benefit of myself and the people I work with - a set of standards to work towards.

Consistency

Doing things in a standardized and consistent manner

What this means in practice

Parsimony

Having nothing more than necessary to reduce cognitive load.

What this means in practice

Conscientious

Essentially double-checking your work and actively searching for errors.

What this means in practice:

Communication

Keeping everyone in the loop and proactively helping team-mates avoid WTF situations and confusion.

What this means in practice:

Growth and Mentoring

Cultivate an attitude of wanting to improve.

What this means in practice:

Introspective tools

Have at your disposal excellent information and tools about how your code and how your program is running, in order to debug it quickly.

What this means in practice:

Teamwork

Activities that enable the team to work more effectively.

What does this mean in practice:

Architecture

Atomize

Good engineering consists of breaking your work down into small, cohesive, "units" that can be re-used across the project, re-used in other projects, easily tested in a REPL or in unit tests, and happen in enough isolation to avoid merge conflicts.

What does this mean in practice:

Other