Imagine you’ve been tasked to implement a crucial new feature in the product you’re working on. That’s the opportunity you’ve been waiting for - ev...
For further actions, you may consider blocking this person and/or reporting abuse
Another reason to write an RFC is you know there is a teammate that knows a lot about the part of the codebase you are about to work on, and you could use that knowledge -> RFC is then a good way to have an organized communication about it, they can see your plan, enrich it with their knowledge, and you know you are not missing anything out!
Agreed, RFC is a great way to have a structured discussion about a feature/topic.
I guess the biggest trickery is in defining our needs properly from the get-go, then it gets much easier to figure out whether the RFC is worthwhile. :)
Hah yes, that's always the case, figuring out what you actually want or need! :) Any tips from your experience you'd share?
This is a good one - I never heard of RFC before!
Glad you liked it and learned something new. RFCs are a really helpful tool for planning bigger features.
Nice guide to RFCs, love that you included tools at the end!
Thanks a lot and glad you found it useful!
glad it helped! :)
Great learnings, thanks!
Thank you for reading and hope you found it useful!
nice article!
Thanks Kevin!
Enjoyed this piece! Also, loved the diagram :)
Thanks Petar! Yeah, it's a bit simplified so just a heuristic but I thought it might be a good starting point :)
Nice!! I learned a lot here. Thanks for writing up!
Thanks! I hope you find it as useful as we do :)
Nice post. learned a lot from this!
RFCs >> dealing with 20 comments on the PR
Great post!! We also follow a similar RFC process at Flipt.
QQ: Do you make all your RFCs public at Wasp?
We actually make a lot of them public - it's super helpful when sharing RFCs with the community (e.g. ours is on Discord: discord.gg/rzdnErX), we get plenty of good ideas, and it also helps validate the direction faster.
The only reason why not all of them are public is that by default, they are private in Notion, so if it's a smaller RFC, it might already get merged before we open it up. But there is absolutely no reason not to have it all public!
Btw Flipt looks amazing, and I love that it is open-source, might be a great fit to go with Wasp :)
I thought RFCs must be a white paper with boring long text :D
haha :D Yellow is also fine! :)
Amazing. I'll definitely use this one in the future
Thanks a lot Tin! Really glad you found this valuable :)
Please stop perpetuating the myth of the 10x developer. This problematic idea promotes burnout and worsens imposter syndrome, while encouraging managers to push their people to work harder for less pay and fewer benefits.
The 10x developer myth is objectively harmful.
Hey Mike, I appreciate the comment! But did you read the article, especially the Summary? My main point is actually that being a 10x developer doesn't mean coding more or faster, but rather taking more time to plan and collaborate with your colleagues.
Another thing is whether we should stop using the term "10x developer" altogether, is that what you had in mind? I personally don't think it will go away, and that it's not necessarily inherently wrong, but I believe we should all work together on improving its meaning. That could actually be a really interesting topic to cover.
Thanks again for giving it a look!
I agree. The 10x developer is one that is more like "Sharpen the axe and spend 10% of the time to chop down the tree." You get more done if you are planning and execute the right thing, than not planning and execute many wrong things first. Or you may still execute the wrong thing, but you are likely to at least be 10x closer to the right thing that much sooner.
Thanks Victor, that is what I had in mind!
Just like all other terms which cause harm by creating toxic fictions, the use of this term should indeed be discontinued.
There are a variety of terms which cause harm but are nonetheless unlikely to perish from our collective vocabulary, but this does not excuse their continued willful use.
Thanks for the clarification, I see your point now. I agree there is that "myth" of a 10x engineer, when it is in reality just a person doing their job well, which is what we should all strive for by default. I don't think other professions use this term, e.g. "10x teacher" or "10x lawyer".
Interesting concept, thanks for sharing Wasp's example!
Thanks Ivan!
Great 👍. Gifs and cover pic nice. And will trigger nice idea 💡