Skip to content

Gabriel's README

Quick Summary

  • I value simplicity and reliability over complexity. Brilliantly executing simple tasks is my target.
  • Always open to new ideas and concepts. There are no dumb questions for me.
  • I like to be corrected asap when I'm wrong. (respecfully)
  • The concept of "Disagree and Commit" is great and I try to follow it on every interaction.

How I Work

Communication Style

  • I like to understand 100% of the expectations before starting a task, so I might ask some "dumb" questions to make sure I'm on the right track.
  • I like to give and receive feedback often. I don't take a defensive posture when receiving feedback.
  • I don't mind having to rebuild something or starting over if the requirements have changed.

Decision Making

  • I do like to interact with the team and gather feedback before making a decision.
  • There is no "right" answer, so I try to understand the trade-offs of each option.
  • I tend to make decisions that will defend the quality of life of the team.

Technical Standards

  • Taking the appropriate amount of planning often pays off in terms of architecture.
  • Code should be readable and maintainable. Performance is also important, but comes last in this list.
  • I like to use widespread, well established tools instead of niche ones.

My Working Principles

  • No dumb questions

Make the effort to set clear expectations and requirements. Ask questions even if they sound obvious.

Correcting me won't hurt my ego.

Discussions should be composed of a team against the problem, not team members against each other. Discussing is to find a solution, not to win.

  • Brilliant basics

Do not overcomplicate things. Many times a simple solution well implemented is much better than a hyped/complex one.

No need for overengineering. Deliver things as abstract as they get, and not more.

What I Value

  • Receiving thoughtful feedback.
  • Humility.
  • Proactive communication.
  • Reporting problems with a solution or two at hand.

How to Work Best with Me

  1. When Disagreeing

  2. Remember we're both working towards the best solution for the team.

  3. Feel comfortable expressing disagreement.

  4. When Facing Challenges

  5. I'll come prepared with potential solutions when raising problems.

  6. Be open to rebuilding or changing direction if requirements evolve.

  7. When Building

  8. Start with clear requirements and expectations. DoD (Definition of Done) is something I value a lot.
  9. Sticking to company-wide standards, and discussing what should be the standards if something doesn't exist yet.
  10. Focus on proven, established tools and approaches.