Varun Srinivasan
@v
we don't block on code reviews to ship something by default. but there are two important nuances to this: 1. post-facto code reviews, where people can give you feedback on improving something after it ships. this is good for more pendatic, stylistic or perf stuff. 2. requested code reviews, where people working on sensitive code know that they should ask for reviews. this happens often when working on security critical stuff.
6 replies
2 recasts
57 reactions
Fots
@fots
i really like this point, in many companies CR process takes forever and devs ship slower just to write perfect code. but then the question is: how do you deal with technical debt?
1 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
I can't tell if I'm a boomer and this is good for velocity, or if this is an anti-pattern that sacrifices long-term velocity / stability for short-term gains @giu and I review each others' code and we frequently catch things the other misses Especially as you scale the org, how do you prevent bugs from getting into prod?
1 reply
0 recast
1 reaction
Angel
@sayangel
i missed your AMA and meant to ask you this during it. Appreciate the insight! You guys make balancing velocity and quality look easy.
0 reply
0 recast
0 reaction
rocket
@rocket
Wow, lots of trust! Thatβs cool. We just integrated AI code reviews at TipLink, has functioned pretty well as a base line of defense against bugs
0 reply
0 recast
0 reaction
Akston (kolom)
@kolom
where I can send some bugs regarding freezing ui after some actions?
0 reply
0 recast
0 reaction
dmittc π΅
@dmtc
Unfortunately, I'm still in spam, I even replenished my wallet with $35, passed all verification levels. But the mark is still 0. I don't quite understand why Farcaster so persistently throws me into spam
0 reply
0 recast
0 reaction