DEV Community

loading...

Discussion on: Flexible code considered harmful

Collapse
safijari profile image
Jariullah Safi

I like to always start simple when it's a new problem and coalesce similar functionality as time passes. This idea really only works when you're willing to spend time refactoring the same code over and over (which I don't see as a waste of time when done correctly).
That said when an abstraction is obvious I absolutely begin with it.

Collapse
seanmclem profile image
Seanmclem

It's about finding a sweet spot, and not pursuing extremes

Collapse
waveitgoodbye profile image
WaveItGoodBye

I have a co worker that is a big fan of the rule of three. It's a good general rule of thumb to follow and I find it helps summize the same point I think you made here.