Hacker News Reader

What about the importance of handling high-level architecture and design before writing code? This can be done in design docs, discussion on tickets, slack discussions or in person with a whiteboard. I think it's more productive to handle these discussions and reviews before writing any code.

What do other people think?

View on HN

I would agree. I think if you're talking about high-level design in a code review then either:

A) You've revealed a need to get more alignment on design, and should probably be explicit that the discussion has this purpose.

B) You're doing a code review of a spike so that you can get alignment about the design lessons the spike teaches...and should be explicit that the discussion has this purpose.

Reply on news.ycombinator.com