Ramon's README
Quick Summary
- I'm direct, transparent, and approachable
- I believe in moving fast, starting simple, and learning through iteration
- I expect everyone (including myself) to check their ego at the door
How I Work
Communication Style
- I state my opinions directly and with conviction - not because I believe I'm always right, but because clarity drives better discussions
- I'm quiet when processing information and forming opinions. Don't mistake my silence for disinterest - I'll speak up when I have something to contribute.
- I expect and welcome pushback, provided it comes with substantive reasoning
- I'm almost always available on Slack - don't hesitate to reach out
- I prefer overcommunication about blockers or concerns - tell me early, tell me often
Decision Making
- I believe in making decisions quickly with the information we have
- I'd rather see a simple solution deployed today than a perfect solution next month
- When I disagree, I'll be direct about it and explain my reasoning
- I expect you to challenge my thinking if you see flaws - I have no ego about being wrong
Technical Standards
- I maintain high standards for code quality, architecture, and technical decisions
- I believe in "fail fast, learn fast" - but I expect us not to make the same mistake twice
- Technical debt is okay when strategic; unplanned tech debt is not
- I value pragmatic solutions over perfect ones, but expect clear reasoning behind technical trade-offs
My Working Principles
-
Speed with Purpose
-
Move fast, but know why you're moving in that direction
- Start simple, iterate based on learnings
-
Better to build, learn, and adjust than to overanalyze
-
Quality Through Iteration
-
High standards don't mean perfection from day one
- Each iteration should be better than the last
-
Document learnings from failures - they're valuable assets
-
Transparent Leadership
- I'll share context, concerns, and decisions openly
- You'll always know where you stand with me
- I expect the same transparency from my team
What I Value
- Direct, substantive feedback
- Proactive communication
- Ownership mentality
- Learning from failures
- Simple solutions to complex problems
- Team members who challenge assumptions (including mine)
How to Work Best with Me
-
When Disagreeing
-
Come prepared with specific examples
- Focus on business/technical impact
- Propose alternative solutions
-
Be direct - I appreciate clarity over diplomacy
-
When Facing Challenges
-
Flag issues early
- Come with potential solutions when possible
- Be clear about what you need from me
-
Don't wait for the perfect solution before speaking up
-
When Building
- Have strong opinions about your solutions - you're the expert on your code
- Challenge my ideas if you believe there's a better approach
- Be prepared to explain your thinking
- Own not just the code, but the product and user outcomes
My Commitments to You
- I will be transparent about expectations and feedback
- I will provide context for decisions and priorities
- I will be available when you need support
- I will admit when I'm wrong
- I will help remove blockers
- I will always be open to feedback about my leadership