Hacker News new | past | comments | ask | show | jobs | submit login

I see a lot of comments mentioning various versions of the following:

- "It's the "jazz music" of software development."

- "...breaks all the "rules" but does so purposefully..."

- "this is irreducibly complex, and cannot be split into multiple files"

- "that smallness-of-file or smallness-of-function is not a target to shoot for"

I am wondering: can't all the above statements be said in defence of any poorly engineered, gargantuan single page code?




But this gargantuan pile of garbage warns that it can not and should not be refactored and it is like the shuttle code (may their souls rest in peace), it is so solid and perfect as is. It is also written in the sacred language of Go. So if these conditions are met, then yes above praises will be and must be sang.


The jazz music analogy implies that it breaks the rules, but do so artfully and intelligently -- that wouldn't necessarily be a valid defense for any old block of poorly engineered code.

Also, poorly engineered code is seldom irreducibily complex.


Code that is “write only” (as is proudly proclaimed in this case) is shit no matter how you spin it.


Can everyone play jazz?

No.


Can everyone claim that their terrible music is jazz music?

Yes.


Apart from a comedy bit, can everyone easily spot the difference?

Yes.


No. Most jazz, including by the jazz greats, just sounds plain terrible. The worst is jam sessions, where everyone steps over each other but it sounds not abysmal at times because they're in the same key.


Only because you asked:

https://youtu.be/cRzDEdY8FL4?t=214


I thought your link was going to be to "H. Jon Benjamin Doesn't Play An Instrument, But Recorded A Jazz Album": https://www.youtube.com/watch?v=ZeMIgcNUpNQ




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: