How do you plan a code change?
I talk with a senior dev on my team about a new change, make that change, but in the PR comments there are some differences between what was expected vs what got implemented. What is the best way to mitigate this disconnect? Do you verify an implementation with people on your team before writing code?
Some things can't be evaluated until they're done. Applying for grants is the
canonical example: in order to get money for your proposal, you more or less have to
implement the proposal first. Similarly, senior devs expect junior devs to
spin their wheels writing software that will likely have to be re-written.
It's also more cost-efficient than the alternative of discuss-as-you-go
hand-holding since a junior dev's time is relatively worthless.