35 ms·
I come from an era where the more fully featured your IDE, the less likely you were to truly understand what was going on under the hood. I strongly recommend
by TameAntelope 4y ago
I come from an era where the more fully featured your IDE, the less likely you were to truly understand what was going on under the hood.
I strongly recommend everyone spend their first ~5 years coding in vim or some other basic text editor (preferably through the terminal), before leaning on an IDE to solve their problems for them.
That said, VSCode is now my go-to IDE, and I haven't opened WebStorm in probably ~6 months. It's lighter weight than the IDEA suite of IDEs, and gives me ~80% of the functionality, so it's been a pretty good tradeoff.
- 999900000999 4y agoWould you even do that with C# ? I actually dislike computer science classes which won't let me just use an IDE. No one can memorize the .net 7 API
- heartbreak 4y agoVS Code and Vim have intelligent autocomplete for C#, although Vim requires significantly more configuration to get it working.
- quickthrower2 4y ago.NET Core and beyond yes. For older .NET you really need classic VS or you will probably have a bad time.
- bbkane 4y agoHonestly, I don't think VSCode hides much of what's going on from you. Generally I use it to edit code and then run "go run ." on the side.
- kllrnohj 4y agoThere are languages, like C#, Java, and Kotlin, where the language design basically assumes an IDE is being used. It's just not practical or useful to deal with imports and their structure. Sure you can look them up on javadocs and copy/paste the import path. But at that point why not just use an ide? Why learn a skill you'll basically never use or need?
- TameAntelope 4y agoI wrote Java for multiple years in vim with no extensions installed.
- hit8run 4y agoI don’t think that is smart
- TameAntelope 4y agoI was more productive than I suspect someone with just an IDE would have been, considering the volume of complex non-coding issues I needed to learn about and solve.
- kllrnohj 4y agoHow does spending your time learning about things an IDE would have avoided make you "more productive"? That's a pretty clear cut argument that you were less productive as you were doing things manually a tool would have automated. Thereby spending time being unproductive.
- TameAntelope 4y agoBecause an IDE doesn't always (or even usually) avoid those things, and I don't consider learning time to be unproductive if it means in the future I'm more productive. It's a pretty clear cut argument that using an IDE as a crutch will inevitably bite you in the ass, and if you want the best possible understanding of the language you're using and all of its related tools you ought not use an IDE as it obfuscates those very things you're trying to learn about.