From Chaos to Clarity: Leveraging RFCs in High-Performance Environments

Rate this content
Bookmark

In high-performance environments, the pace is relentless. While it's easy to make quick technical decisions in smaller developer teams, the dynamics shift drastically when dealing with a team of 100 developers. Making significant technical decisions, especially those concerning architecture, without impacting other teams becomes nearly impossible.

In this talk, I'll share my experience of structuring an RFCs process at QuintoAndar. We'll delve deep into RFCs, uncovering why they're an indispensable tool for companies aiming to maintain technical excellence, even with a sizable workforce. We'll explore how RFCs facilitate high-level technical decision-making, providing a clear roadmap for changes and empowering everyone to navigate risks with precision.

This talk has been presented at TechLead Conference 2024, check out the latest edition of this Tech Conference.

FAQ

Mateus Palino is a senior software engineer and tech leader at Quintana Roo.

Quintana Roo is the largest housing platform in Latin America, present in over 50 Brazilian cities and starting to expand internationally.

Quintana Roo has more than 5,000 employees, including 1,000 people in product and technology.

The Amazing RFCs initiative at Quintana Roo aims to improve the quality of architectural decisions, reduce design time, and facilitate knowledge sharing and cross-tribe collaboration.

The three main areas of focus are empowering focal points in each tribe, having managers capable of training and guiding, and creating tools, guides, and processes for architecture.

RFCs Advisors assist others with writing RFCs, create a community for idea exchange, and provide expert advice during the RFC process.

The design review process involves selecting invitees based on domain knowledge and interest, scheduling ad hoc design review meetings, and ensuring synchronous participation of key stakeholders.

Training initiatives include Introduction to Problem Analysis and Solution Architecture Overview, covering topics from fundamental architectural principles to advanced techniques.

The outcomes included increased technical capability in architectural decision-making, more RFCs being written, and higher quality solutions deployed.

RFCs are important at Quintana Roo for making efficient architectural decisions, sharing knowledge, and improving the quality of solutions delivered.

Mateus Paulino
Mateus Paulino
10 min
15 Jun, 2024

Comments

Sign in or register to post your comment.

Video Summary and Transcription

Mateus Palino from Quintana Roo presents From Chaos to Clarity, Leveraging RFCs in High-Performance Environments. Quintana Roo aims to improve delivery quality and reduce design time through RFCs. They have created a group called RFCs Advisors and focused on empowering focal points, training managers, and creating tools, guides, and processes. By implementing tailored training initiatives and optimizing design review meetings, they have increased the number and quality of RFCs, resulting in better solutions deployed.

1. Introduction

Short description:

Mateus Palino from Quintana Roo presents From Chaos to Clarity, Leveraging RFCs in High-Performance Environments. Quintana Roo, the largest housing platform in Latin America, aims to improve the delivery quality and reduce design time through RFCs. They have focused on empowering focal points, training managers, and creating tools, guides, and processes. One important action was creating a group called RFCs Advisors, who assist others and exchange ideas.

Hi, everyone. Mateus Palino here. I'm from Brazil. I'm also a senior software engineer and tech leader at Quintana Roo. And I'm here to present this talk, From Chaos to Clarity, Leveraging RFCs in High-Performance Environments.

So first of all, I'd like to give you some context about Quintana Roo and why RFCs are so important there. So Quintana Roo is the largest housing platform in Latin America. It's already present in over 50 Brazilian cities and has started making its first moves into the international market. Currently, it has more than 5,000 employees, including 1,000 people in product and technology. So therefore, our architecture decision-making process needs to be very, very efficient.

And that's why we have created an initiative called Amazing RFCs. What we hope to achieve end of the initiative. We'd love to see visibly improved quality of our deliveries, reduced time spent on design, RFCs as a way of sharing knowledge, cross-describe and try collaboration.

So to do that, we needed to increase the density of people technically capable of conducting great architecture decisions. And a way to do that is by RFCs. But writing RFCs involved many, many areas. And that's why we have decided to split it in three main areas. The first area that we were going to work was empowering focal points in each tribe. It means having local technical leadership who are subject matter experts and can provide assistance. Those leaders would also directly claim individuals from these tribes. The second area would be managers capable of training and guiding. They will also be responsible for monitoring technical decisions, establishing accountability for good technical decisions within the area itself. And last but not least, tools, guides, and process. Creating guides to assist with different aspects of architecture, creating tools for tracking and improving quality.

So we took many actions to achieve those goals, but I'd like to show you three actions that really made the difference for us. The first one was create a group called RFCs Advisors. People who are responsible for assisting others with RFCs and create a community for them to exchange ideas, as well as bring specific advisors who are experts in system areas. So how did that work? We have the advisors on the top. And the process of writing a RFC would be split into three steps. Step one, initial writing, presentation to the team, and then external review.

2. Actions for Effective RFCs

Short description:

The advisor would also be present along with the person who's writing in those three steps. The second action was changing the schedule and invitees for design review meetings to optimize time. Only key people interested in the subject are mandatory attendees. Tailored training initiatives enhance technical skills for architectural decision making. The outcomes: increased density of people capable of conducting great architectural decisions.

The advisor would also be present along with the person who's writing in those three steps. The second one was open for comments. At least one week in advance so people can prepare and have a week to read the RFC. Then the person who was writing a language with the advisor would present it to the line and then make the adjustments if it was necessary. And last but not least, it would require approval by at least two reviewers and then it was good to ship.

The second action that we took that made a lot of difference was regarding designing review process. We have noticed that our synchronous time are very valuable and tend to produce great results as a first phase through our discussions. But to achieve an optimum use of time for every person, we change the schedule and forum. So changing the invitees to be selected by their domain knowledge and interests. Suppose that we are discussing a new architecture for layout components that will be used heavily across the login page. While we may have several super good candidates for discussion, like front-end engineer that contributed for the login in the past or full stack engineer that modified the login page and integrated with the APIs or the engineering manager that will soon be pushing his team to propose a new architecture for SSO login. We can also have some people that will not have too much to contribute and could potentially use their time better. Like a backend engineer that is currently solving a field challenging or another team doesn't have anything with login. Or a full stack engineer that is currently focusing on integrating several high complexity services for the past few months and isn't aware of the login process. So that's why we have decided that only people interested or key people in the subject of the RCs will be present. Other people are invited to, but it's not mandatory for them. The second thing related to the design review process was scheduling and accurate design reviews instead of a fixed weekly. So we changed our design review meetings from weekly to non-ad hoc schedule, which means the person that are writing the RC will schedule the design review meeting. Together with the advisor, they are responsible for choosing and aligning with the people that will be invited for the discussion. Together with the advisor, they will pre-select the core approvals that will have a required review for their RC to be closed, and their design review will be scheduled at a time that best suits the writer, the advisor and the participants. That way, we can make sure that only the interested people are there, and they will have the time and they will be there to review the RC synchronously.

And another action that we took that I'd like to present here was tailored training initiatives. We have developed trainings that focused on enhancing the technical skills and knowledge necessary for architectural decision making. It covered a wide range of topics from fundamental architectural principles to advanced techniques. For instance, Introduction to Problem Analysis, where we have learned to properly identify an initial, gather requirements, clarify objectives, and define scope, identify potential user roles and stakeholders, identify potential solutions, outline strategies and allocate results, and also test and measure outcomes. Another training that we had was on Solution Architecture Overview, where we learned the concepts behind architecture, and overview on microservice, micro-contents, MVC and other partners, syncing versus asynchronous communication, query or topic, pub-sub, UTLs and API gateways. Those trainings gave us a lot of like a toolbox on writing RCs and finding solutions that could be potentially good. And that helped us to expedite the review as well, because the quality of our RCs increases significantly. So what were the outcomes of those actions? First, we have increased the density of people technically capable of conducting great architectural decisions. That was our main goal.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

A Guide to React Rendering Behavior
React Advanced Conference 2022React Advanced Conference 2022
25 min
A Guide to React Rendering Behavior
Top Content
This transcription provides a brief guide to React rendering behavior. It explains the process of rendering, comparing new and old elements, and the importance of pure rendering without side effects. It also covers topics such as batching and double rendering, optimizing rendering and using context and Redux in React. Overall, it offers valuable insights for developers looking to understand and optimize React rendering.
Impact: Growing as an Engineer
React Summit 2022React Summit 2022
27 min
Impact: Growing as an Engineer
Top Content
This Talk explores the concepts of impact and growth in software engineering. It emphasizes the importance of finding ways to make the impossible possible and the role of mastery in expanding one's sphere of impact. The Talk also highlights the significance of understanding business problems and fostering a culture of collaboration and innovation. Effective communication, accountability, and decision-making are essential skills for engineers, and setting goals and finding sponsors can help drive career growth. Feedback, goal setting, and stepping outside of comfort zones are crucial for personal development and growth. Taking responsibility for one's own growth and finding opportunities for impact are key themes discussed in the Talk.
Speeding Up Your React App With Less JavaScript
React Summit 2023React Summit 2023
32 min
Speeding Up Your React App With Less JavaScript
Top Content
Watch video: Speeding Up Your React App With Less JavaScript
Mishko, the creator of Angular and AngularJS, discusses the challenges of website performance and JavaScript hydration. He explains the differences between client-side and server-side rendering and introduces Quik as a solution for efficient component hydration. Mishko demonstrates examples of state management and intercommunication using Quik. He highlights the performance benefits of using Quik with React and emphasizes the importance of reducing JavaScript size for better performance. Finally, he mentions the use of QUIC in both MPA and SPA applications for improved startup performance.
On Becoming a Tech Lead
TechLead Conference 2023TechLead Conference 2023
25 min
On Becoming a Tech Lead
Top Content
The role of a Tech Lead involves shaping the roadmap, helping the team be more effective, and working on important projects. Lessons learned include encouraging idea sharing, avoiding taking on all the work, and focusing on delegation. Tech Leads focus on the outcome, involve the team in decision-making, and make plans based on how different pieces will interact. The role of a Tech Lead is to focus on engineering and guide the team in figuring out how the whole system should fit together. Architecting can become problematic when it loses touch with the coding part, resulting in implementation issues.
React Concurrency, Explained
React Summit 2023React Summit 2023
23 min
React Concurrency, Explained
Top Content
Watch video: React Concurrency, Explained
React 18's concurrent rendering, specifically the useTransition hook, optimizes app performance by allowing non-urgent updates to be processed without freezing the UI. However, there are drawbacks such as longer processing time for non-urgent updates and increased CPU usage. The useTransition hook works similarly to throttling or bouncing, making it useful for addressing performance issues caused by multiple small components. Libraries like React Query may require the use of alternative APIs to handle urgent and non-urgent updates effectively.
Emma Bostian: I landed my dream job by sharing my blogs on Twitter
Emma Bostian: I landed my dream job by sharing my blogs on Twitter
Top Content
Featured Article
Emma Bostian
Emma Bostian
Software engineer, lecturer, podcast host, author — is there something Emma Bostian hasn't done? She moved from America to Sweden, started working at Spotify, and took up a few challenges along the way. And now she has some career tips to share.
What led you to software engineering? I was raised in the ecosphere of tech because my dad is a software engineer at IBM, and my mom was a designer there, too. My dad always encouraged me to join STEM and take a look at computer science — however, I was convinced I wanted to be a medical doctor. In my first year of college, I declared a biology major and quickly realized I was not too fond of it. In my second semester, I switched to an actuarial science major where I took Introduction to Computer Science, and the rest is history. In my second year of college, I declared a computer science major and began my journey from there.
What is the most impactful thing you ever did to boost your career?Writing blog posts and documenting my learning journey on Twitter has far been the best career boost. I wrote purely for myself to reference the things I learned over time, and I even utilized my design skills in Figma to create custom graphics depicting difficult concepts like CSS specificity. By sharing my blogs on Twitter and engaging with the people reading them, I was able to grow an audience extremely quickly. I began receiving conference speaking opportunities, podcast requests, and course invitations to teach with LinkedIn Learning and Frontend Masters.
Ultimately, I landed my job at Spotify through Twitter, too, when a friend and follower of mine asked if I would be interested in interviewing. Now I live in Stockholm working my dream job. It still blows my mind how tweeting about my blog led me to some of the most amazing career opportunities.
What would be your three tips for engineers to level up their career? First, be patient. I often see posts on Twitter or LinkedIn about developers who were promoted to a senior position after a year. And while this is wonderful, I think we forget that each company has a different standard for what constitutes a senior developer, and everyone's journey will be different.
Second, don't be afraid to ask questions. If you try your best to solve a problem or answer a question you have, but you can't figure it out after a reasonable amount of time, ask a team member or mentor for help.
And lastly, invest in the right resources for learning. When I started my journey, I didn't know which platforms worked for me to learn. Now, I have a few trusted platforms such as Frontend Masters, Free Code Camp, or Level Up Tutorials that I go to when I need to learn a new skill.
You're currently working as a software engineer at Spotify. What does a typical day of yours look like there?I begin my day answering emails. Then we have a team breakfast and a standup remotely as we're all still remote at Spotify. After that, we might have a web tech sync with the other squads in our business unit. The day usually includes some form of pair or mob programming, depending on the work stream. 
My team always has Fika, a traditional Swedish coffee break, scheduled every afternoon. Every couple of Fridays, we have team games planned to release some stress. 
Also, I tend to have a lot of free time to focus, which is nice but makes for a boring answer to this question!
Do you have some rituals or tools that keep you focused and goal-oriented?I'll admit that I've been struggling with staying motivated in the time of remote work. I've been remote with Spotify since onboarding a year ago, but my team is wonderful, and they help me when I'm down.
Apart from that, I use Todoist to keep track of my tasks, and, naturally, I listen to Spotify while working. But other than that, not really. Maybe I should adopt some new tools to keep me on track!
My current favorite Spotify playlist is Brand New Chill: https://open.spotify.com/playlist/37i9dQZF1DX6uQnoHESB3u?si=380263b3c853442e
I also love Chillout Daily: https://open.spotify.com/playlist/7ozIozDp260fjNOZy1yzRG?si=66d6c839ec9b458a
You wrote a book called De-coding the Technical Interview. What was the impulse to do it?I wanted to give the community a manual of the essentials of computer science knowledge to ace the technical interviews. The book covers data structures like stacks, queues, or linked lists, tackles algorithms, and deals with systems design. You'll also learn about the interview process from start to finish, get tips on how to submit an amazing take-home project, or understand how to problem solve. You'll also gain knowledge on the frontend coding skills needed to excel at a frontend interview.
If you could stress one piece of advice on surviving a technical interview, which would it be?Do not lie your way through an interview. If you don't know the answer to something, just admit it. There's no shame in admitting you don't know the answer to something. There is shame in faking it and pretending like you do know the answer.
What's the single best practice everyone who writes code should follow?Remember that while you are technically writing code for computers, you're also writing it for humans. Your code should be readable and have as little complexity as possible without sacrificing accessibility or performance.
In addition to the book, you co-host the Ladybug Podcast. What inspired you to enter this field, and what are the podcast's main topics?We talk about everything tech and career on the podcast, from Java and GraphQL to how to start a business and cross-cultural communication. The podcast is a way for me and my co-hosts to share our experiences in tech, having taken different paths. And I'm really glad for doing it — it has allowed me to meet so many incredible people, learn many new things, and support my dream of teaching.
What pieces of your work are you most proud of?My technical interview book was a huge feat for me as well as my courses with LinkedIn Learning on building a tech resume. I enjoy creating things that help other people advance their careers, so I'm also proud of my courses with Frontend Masters on design systems and CSS.

Workshops on related topic

React Performance Debugging Masterclass
React Summit 2023React Summit 2023
170 min
React Performance Debugging Masterclass
Top Content
Featured WorkshopFree
Ivan Akulov
Ivan Akulov
Ivan’s first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didn’t know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Here’s how this is going to work. We’ll take a slow app → debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) → pinpoint the bottleneck → and then repeat, several times more. We won’t talk about the solutions (in 90% of the cases, it’s just the ol’ regular useMemo() or memo()). But we’ll talk about everything that comes before – and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work – but want to get better at using the performance tools around React. Also, we’ll be covering interaction performance, not load speed, so you won’t hear a word about Lighthouse 🤐)
Building WebApps That Light Up the Internet with QwikCity
JSNation 2023JSNation 2023
170 min
Building WebApps That Light Up the Internet with QwikCity
Featured WorkshopFree
Miško Hevery
Miško Hevery
Building instant-on web applications at scale have been elusive. Real-world sites need tracking, analytics, and complex user interfaces and interactions. We always start with the best intentions but end up with a less-than-ideal site.
QwikCity is a new meta-framework that allows you to build large-scale applications with constant startup-up performance. We will look at how to build a QwikCity application and what makes it unique. The workshop will show you how to set up a QwikCitp project. How routing works with layout. The demo application will fetch data and present it to the user in an editable form. And finally, how one can use authentication. All of the basic parts for any large-scale applications.
Along the way, we will also look at what makes Qwik unique, and how resumability enables constant startup performance no matter the application complexity.
Next.js 13: Data Fetching Strategies
React Day Berlin 2022React Day Berlin 2022
53 min
Next.js 13: Data Fetching Strategies
Top Content
WorkshopFree
Alice De Mauro
Alice De Mauro
- Introduction- Prerequisites for the workshop- Fetching strategies: fundamentals- Fetching strategies – hands-on: fetch API, cache (static VS dynamic), revalidate, suspense (parallel data fetching)- Test your build and serve it on Vercel- Future: Server components VS Client components- Workshop easter egg (unrelated to the topic, calling out accessibility)- Wrapping up
React Performance Debugging
React Advanced Conference 2023React Advanced Conference 2023
148 min
React Performance Debugging
Workshop
Ivan Akulov
Ivan Akulov
Ivan’s first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didn’t know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Here’s how this is going to work. We’ll take a slow app → debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) → pinpoint the bottleneck → and then repeat, several times more. We won’t talk about the solutions (in 90% of the cases, it’s just the ol’ regular useMemo() or memo()). But we’ll talk about everything that comes before – and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work – but want to get better at using the performance tools around React. Also, we’ll be covering interaction performance, not load speed, so you won’t hear a word about Lighthouse 🤐)
High-performance Next.js
React Summit 2022React Summit 2022
50 min
High-performance Next.js
Workshop
Michele Riva
Michele Riva
Next.js is a compelling framework that makes many tasks effortless by providing many out-of-the-box solutions. But as soon as our app needs to scale, it is essential to maintain high performance without compromising maintenance and server costs. In this workshop, we will see how to analyze Next.js performances, resources usage, how to scale it, and how to make the right decisions while writing the application architecture.
Maximize App Performance by Optimizing Web Fonts
Vue.js London 2023Vue.js London 2023
49 min
Maximize App Performance by Optimizing Web Fonts
WorkshopFree
Lazar Nikolov
Lazar Nikolov
You've just landed on a web page and you try to click a certain element, but just before you do, an ad loads on top of it and you end up clicking that thing instead.
That…that’s a layout shift. Everyone, developers and users alike, know that layout shifts are bad. And the later they happen, the more disruptive they are to users. In this workshop we're going to look into how web fonts cause layout shifts and explore a few strategies of loading web fonts without causing big layout shifts.
Table of Contents:What’s CLS and how it’s calculated?How fonts can cause CLS?Font loading strategies for minimizing CLSRecap and conclusion