3 ms·
1. an ide/language with really good static analysis 2. aggressively minimize codebase complexity done. when my code doesn't work the first time, and i'm writin
by dustingetz 15y ago
1. an ide/language with really good static analysis
2. aggressively minimize codebase complexity
done. when my code doesn't work the first time, and i'm writing in a static-typed language, it's usually due to high accidental complexity in my code or code i interface, requiring me to keep too much context in my head, causing logical problems and problem states to be non-obvious.
stupid errors like writing an if statement wrong, is sophomoric. "most common errors" really means avoiding mutable state & leaky abstractions[1]. i do think the OP gets this, it just doesn't come across too clearly.
[1] nostrademons of HN, "how to become an expert swegr" http://news.ycombinator.com/item?id=185153 http://news.ycombinator.com/item?id=185153
- joe_the_user 15y agoI'd say the devil is in the "aggressively minimize codebase complexity" detail If you can give reproducible instructions about how to do that, I'd say to hear them.
- dustingetz 15y agoagreed, but that's the point: "use 1==foo and keep methods small" is totally missing the point. I'm not sure I can state it more clearly than "understand accidental complexity, aggressively reduce it".