The article mentions fast user feedback and dogfooding as alternative ways to get feedback to code reviews. I think these are two different things, user feedbac

The article mentions fast user feedback and dogfooding as alternative ways to get feedback to code reviews. I think these are two different things, user feedback and dogfooding are great ways to know if you built the right thing or you built an intuitive solution but they have nothing to do with the underlying engineering of the solution. I much prefer (software) design reviews, they make code reviews a sort of a sanity check to see if the design was followed (reasonably), we're testing the right thing, and maybe there were some business rules that weren't followed because they weren't obvious in the design process. This is especially important when you have a lot of engineers in the team/organization. Clicking around in Raycast's jobs page, I get the impression they prefer ICs to work individually and ship things on their own with little to no collaboration, so no code reviews seems to be aligned with their values.