I like to work with responsibility of my actions. the more congruent I am with what I'll do and what I say I'll do the happier and relaxed I can feel in my day to day.

I perform the best when I can have a voice in my project, where I can contribute to project at a product level not just engineering level.

What do I value in my work?

Over the years I've learnt to value the following aspects in my work and my team, I've struggled with things like organization, commitment, responsibility, and proactivity. these are some thoughts that help me perform and mitigate these struggles in my life and work.

Team communication

team communication is the most important aspect in a project, to achieve this I strategize around the following aspects

1. Transparency - communicate in open channels where all participants can read the same information.

2. Proactive comms - take advantage of async communication tools like slack, I don't wait until meetings or voice calls to sort out important topics.

3. Don't ask to ask: just ask questions Don't ask to ask, just ask (dontasktoask.com)

4. Document around team decisions and agreements to remind ourselves and to welcome new contributors.

5. Have well defined and directed meetings - meetings when used too much can be a time sink. Having well defined points and directed meetings is key to maximize everyone's time. and leave enough room to do the work.

6. Leave with action items

7. Always keep things professional.

Team health

I value having my team happy and energized to the work, to achieve this I strategize around the following aspects.

1. Listen to the team - listen for their opinions and value their thoughts and find ways to take action.

2. Have friendly conversations with the team, make them feel like they can be themselves in the project.

3. Respect everyones opinion

4. Everyone is accountable to their actions

5. There is no blame just responsibility.

6. Honest feedback - honest and consistent feedback is important to push teams to be better or even just congratulate and recognize the work can be worth massive amounts of good motivation. I like to use radical candor

   1. Care Personally: Show that you genuinely care about your team members as individuals. This means being empathetic and supportive, and taking an interest in their personal well-being and professional growth.

   2. Challenge Directly: Provide honest, straightforward feedback without sugarcoating or avoiding difficult conversations. This involves addressing issues directly and clearly, even if it’s uncomfortable.

   3. Have empathy

7. Mentor and always be open to help

Documentation

Project documentation is very important, to achieve this I strategize around the following aspects:

1. Document team agreements

2. Document complex technical aspects

3. Make usage of contracts

4. Document very important information everyone should know (vacations, useful links, roles, platforms, etc.)

5. Document action items

Technical work

I value technical work and to achieve this I strategize around the following

1. Think about solutions before executing any code implementations.

2. Have round tables around possible solutions to get to a consensus.

3. Ask for feedback to other teammates or teams around a solution that I'm thinking about implementing.

4. Allocate time to do code reviews

5. Allocate time (if needed) to have pair programming sessions with struggling teammates.

6. Set policies or guides for different technical processes (code reviews, deployment processes, unit testing, etc.)

7. Allocate time for solving technical debt, or any QoL improvement.