I think this is a bit reductive & elitist. Not everyone develops complex systems software, where you can actually usefully spend 90% time thinking. And even in those cases, for some not having to memorize structure member names etc leaves more room for architectural thinking.https://twitter.com/hyc_symas/status/931834139753447424 …
-
-
I think you're missing the point. No matter what kind of software you write, you must plan ahead before writing. Focusing on the writing tool is its own distraction.
-
No matter how "smart" the IDE, it won't save you from logic errors or writing bloated, bad code. Only thinking about what you're doing can prevent that. Programmers rush too quickly to start coding before thinking about and fully understanding the task at hand.
- 2 more replies
New conversation -
-
-
Yes totally agree. And writing the code isn’t usually the most interesting part of job. Deciding what code to write and where in the project structure is often much more interesting and challenging...
-
Not to mention that great IDEs *can* help you think about the task.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.