Adam Warski
1 min readDec 13, 2017

--

So worse is better after all? :)

On a more serious note, I think there are two different ways of understanding generalization: generalization as flexibility and generalization as abstraction. While I agree that over-flexibility and over-configurability is something to avoid (YAGNI), proper abstraction is something always to look out for: it doesn’t need to mean increased flexibility; rather, focusing on more general concepts (probably already implemented elsewhere), which needs to be applied to parameters corresponsing to the problem we are solving. Of course, „proper” is the key word here, which makes the whole thing difficult :)

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

Adam Warski
Adam Warski

Written by Adam Warski

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

Responses (1)

What are your thoughts?