3 ms·
The way it's supposed to work is that acquired teams get lots of support on integration, including readability. This helps your team get integrated into writing
by jefftk 3y ago
The way it's supposed to work is that acquired teams get lots of support on integration, including readability. This helps your team get integrated into writing Google-style code. Not sure why that didn't work out in this case?
(Left Google a year ago)
- badlucklottery 3y agoThis. Someone dropped the ball. There's a form to get your corner of the codebase exempted from readability temporarily. This gives your team a quarter or two to build up readability.
- Espressosaurus 3y agoA quarter or two isn't going to be enough for a drastic realignment of a large codebase. It's a start, but only a start.
- summerlight 3y agoReadability is usually applied in an incremental way. You don't have to fix all the code to make it conformant. If there are concerns about consistency, the style guide actually encourages people to prefer consistency over its own rule.
- badlucklottery 3y agoThe 1-2 quarters is just to "realign" the SWEs, not the codebase. Old code can usually be left as-is unless there some particularly egregious security hole or the like.