Aral Balkan

I love that moment when you’ve iterated on a design enough times that you really start to peel away all the decoration you added initially because of the insecurity of not having understood the actual problem you were trying to solve. Design is not so much about solving problems as it is about allowing yourself to understand the true nature of the problem you’re trying to solve. Design fails so often not because we cannot solve a problem but because we’re not solving the problem we think we are.

@aral When I worked as SysAdmin (sometimes SysArchitect) for a major multinational we used to say that the most important step was teaching customers to identify what they needed solved, so they could order the right solution from us.
Identifying the problem well enough is core to all later steps...

@aral How many designers does it take to screw in a lightbulb?


Designers: Does it have to be a light bulb?

@aral Your comment reminds me of a cool quote that I like from Antoine de Saint-Exupéry: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."

@aral is that spoken in context of writing code? I am curious, because it's an experience I had many times when building software.

@kosmotaur More on conceptual design / flow but yes, same for code. (And I don't see a clear cut difference between the two.)

@aral I think coding is an act of expressing concepts, and deeply reflects the abstract design behind it. That's probably why your description in the previous toot felt so familiar to me.

Sign in to participate in the conversation
Aral’s Mastodon

This is my personal Mastodon.