Hi Zack,
Stefan Manastirliu
11

I’ve found that a follow-up question of “why do recommend that change?” resolves a lot of the issues with people who have read software theory but aren’t able to apply it in practice.

“Because it should follow the Proxy pattern from the Gang of Four” is not a good reason for changing code because it ignores the product context and the overhead of an extra layer of abstraction. “Wrapping the writing logic in a separate interface would allow us to easily add more export formats” is better. It’s clear about which product needs might merit investing time in a refactor.

Like what you read? Give Zach Millman a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.