Conversation

Please stop glorifying what's unnecessarily complicated. I've heard countless times people brag about how long it takes people to understand what they work on. In my perfect world, it would be the opposite. You would brag about how quickly people can understand what you wrote.

163

1,327

5,645

Wes

@weskerfoot

Replying to

@sarah_edo

How do you differentiate simple as in minimalism (few parts, no hidden complexity) vs simple as in abstracted (easy to understand but hard to recreate)? I find myself preferring minimalism over heavy abstraction in many cases (but not all).

12:25 AM · Jul 8, 2019Twitter Web Client

Replying to

Good question. What I would say here is: I would never brag that someone can't understand my code. It's true that to different people "simplicity" can mean different things. For personal preference, if something is abstracted I would like a way to reach behind that abstraction.

Replying to

and

A small amount of clever code can also be hard to reason about, so I don't necessarily mean minimalism, either.

Show replies

Replying to

and

Main reason being that minimal things are easier to fix if they're broken. Things that make use of heavy abstractions often end up being hard to understand once you inevitably hit some kind of case that doesn't fit.