Team

Onboarding

When developers are new to a project, they take time to get familiar with the codebase, the requirements, and team dynamics.

This process can be slowed or accelerated by certain factors, like tooling, experience, and leadership.

Onboarding can be frustrating for the new developer and the team. Things can take longer to get going, and the pressure to deliver can stress people out. Some of these feelings are internlized because we want to do a good job. Sometimes they are due to lofty expectations, or unforseen hurdles.

Joining the team

You're the newcomer to an existing team. Maybe they've been together a long time and you're just stepping in, or a new team is forming for a project and you've been selected.

It can take a while to find your place on a team. What is your role, and how does that translate into the daily activities and interactions you will have? What expectations do your teammates have of you, and what are yours of them? How can you quickly become a productive member of the team and feel like you're in the right place?

What kind of team are you joining?

Tracking your time

Tracking your time and submitting hours on time is important for getting paid.

There are additional benefits to accurate time tracking, like making better estimates for your work.

With more clarity around where your time goes, you can see which areas of a project demand more of it.

Record your time as it's spent to maximize accuracy. I use a tool like Toggl to get that done.

Work with your team to clarify the buckets of time you should be tracking against. If everyone puts their time in differently, it's hard to make sense of it at the end.