Hacker News Reader

Comment by genericlogic | Hacker News Reader

I really enjoyed this article. When I draw an architecture diagram, write documentation, code or really do anything at work I take a moment to try to make it look "nice". I can't explain why I do it, I just know when I look at it I like it more.

I've always been slightly concerned it was possibly not the best use of time, but I have never had anyone tell me not to do it.

What I like about the article is that it articulates, in a practical way, how to make something more beautiful, whereas I go by feel.

Thanks for sharing.

View on HN

I do this, too. Coding is actually a very visual endeavour for me. I can only describe it as "flow". If my code doesn't "flow", I'm not happy with it. I am baffled by my teammates who seem to have no visual awareness of their code. They might forego whitespace between the close of one function and the declaration of the next, or alternate between having one or more parameters per line in a function signature. It sticks out to me like a sore thumb, but they don't seem to care.

>I am baffled by my teammates who seem to have no visual awareness of their code.

I have somewhat avoided this because it can make you look like you're changing things for no good reason (no easily communicable reason, anyway).

I still do it when people have too much going on for a single line though (ternary ops + function calls + string/number formatting, etc which is very common in enterprise-y programs).

Even if you never share anything, just the thought process that goes into the ordering of the blocks and elements on the page force you to think about the larger structure and dependencies. It's incredibly helpful.

When I make network diagrams in Visio I feel the same way. I put my Steve Jobs hat on and obsess over some small detail. Yes, sometimes it is time consuming but it feels some kind of cup for me. I know I have some kind of technical artistic talent, in high school I wanted to be a drafter.

That's what markup is for; it saves you from unproductive embellishment. Obviously, this does not apply for coding.

> Discussions gravitate around this diagram. People randomly walk up and stare at it. Questions are answered by pointing at it. Periodically throughout the day, chairs swivel around to face this centerpiece, their occupants folding their hands behind their heads.

Visualization goals!

Taking the time to clean up a diagram usually means making it 'easier to comprehend.' Every time you use the clean diagram, you've saved time and energy with a reduced cognitive load.

Reply on news.ycombinator.com