←back to thread

1087 points smartmic | 1 comments | | HN request time: 0.21s | source
Show context
ChrisArchitect ◴[] No.44303809[source]
might be some good points in here but it's sooo hard to read.
replies(6): >>44303888 #>>44303896 #>>44303966 #>>44304009 #>>44304302 #>>44304591 #
IshKebab ◴[] No.44304302[source]
Since you're being downvoted I just wanted to say I agree. I'm sure it was cathartic to write but it's not a good way to actually communicate.

Also like a lot of programming advice it isn't actually that useful. Advice like "avoid complexity" sounds like it is good advice, but it isn't good advice. Of course you should avoid complexity. Telling people to do that is about as useful as telling people to "be more confident".

We mostly learn to avoid complexity through trial and error - working on complex and simple systems, seeing the pitfalls, specific techniques to avoid complexity, what specific complexity is bad, etc. Because not all complexity is bad. You want simplicity? Better trade in you Zen 4 and buy a Cortex M0. And I hope you aren't running a modern OS on it.

Ok "avoid unnecessary complexity"? Great how exactly do you know what's unnecessary? Years of experience that's how. Nothing you can distill to a gimmicky essay.

replies(2): >>44304906 #>>44307975 #
1. yawaramin ◴[] No.44304906[source]
Yeah that's the point, to communicate the idea that some complexity is unnecessary, and we should beware of it, instead of just accepting wholesale whatever complexity is handed to us, like many in this industry do.