Live data from Hacker News

Benefits of Not Using an IDE

alexander-hansen.dev

81–90 of 389 posts

Re: Benefits of Not Using an IDE

#81
post #27

I consider not needing to remember library and api details a benefit. I'd rather dedicate my brain cycles to something else. As for syntax, I don't recall ever struggling to remember syntax of languages I frequently code in. Also the point about IDEs auto generating toHashCode, toString, etc. If your class needs these methods, whether they were auto generated or not seems besides the point. The point the IDE is "comp…

Do you memorize all those IO/XML/JSON/Hadoop (HDFS/MR/Core/...)/AWS/Azure/... APIs by heart?

Re: Benefits of Not Using an IDE

#82
post #27

I consider not needing to remember library and api details a benefit. I'd rather dedicate my brain cycles to something else. As for syntax, I don't recall ever struggling to remember syntax of languages I frequently code in. Also the point about IDEs auto generating toHashCode, toString, etc. If your class needs these methods, whether they were auto generated or not seems besides the point. The point the IDE is "comp…

Do you memorize all those IO/XML/JSON/Hadoop (HDFS/MR/Core/...)/AWS/Azure/... APIs by heart?

The parent explicitly said they do not want to memorize APIs.

Re: Benefits of Not Using an IDE

#83

> When you have to manually find a file to change a subroutine implementation, or to refactor a subroutine, you will have good file names and a good directory structure. The Antipattern of the directory layout of your typical Java Enterprise Project is a Testament to this. (src/main/java/org/company/product/...) To play devil’s advocate, isn’t the goal of a good IDE to abstract away the actual filesystem organization…

I may be talking out of my ass, as I've never used it, but this is my impression of most smalltalk environments, that they just expose objects and functions, not files. For example: https://pharo.org/features.html under "Software as objects"

Re: Benefits of Not Using an IDE

#84
Switching between languages frequently, VS Code is great. Other IDEs are better for specific languages/contexts.

However, I credit my understanding to the time I spent in Notepad++ and times I explored code on the whiteboard while reading docs. Thus, I feel my "internal compiler" would not be anywhere as useful if I had always relied on productivity tools (IDEs).

That said, my input isn't maximized by more efficiently producing the same thing, like a factory, in which case I say IDE all the way.

Re: Benefits of Not Using an IDE

#85

Earlier quoted context omitted.

I'm surprised how many of my colleagues don't use the debugging features of their IDE. Being able to step through code line by line and see all the variables states at any time and evaluate arbitrary expressions given those states seems far superior to print/console based guesstimation. However, somehow my colleagues still do great work!

Depending on which ecosystem you're working with you may be able to get those tools elsewhere. If you're working with client-side JavaScript for example, then you have multiple choices of browsers with excellent debuggers built in.

That’s still not the same as debugging within your IDE. Having to switch from the browser back to your IDE to find the files to make changes is just another context switch that slows you down. Plus, dealing with async loaded files can be a pain in the browser.

Re: Benefits of Not Using an IDE

#86
Always use an IDE for significant software projects. Maybe not for small scripts, or for faffing about on your own learning to code Charles Petzold style. But for professionals working on production code, artificially restricting your productivity by denying yourself the time- and effort-saving features of a good IDE is tantamount to goldbricking.

Re: Benefits of Not Using an IDE

#87

Earlier quoted context omitted.

veering off-topic, that's one of the problems I have with electric bikes - they stop being bicycles and become another kind of vehicle - a faster vehicle that needs longer stopping distances and now has a highe r fatality rate when colliding with a pedestrian. We see this in London cycle lanes. Some cycles are doing a commute, some are trying out for the olympics, some people are doing 25 on a electric scooter and th…

What blows my mind is that in New York, we've decided to deal with this by requiring speed governors on pedal-assist bicycles to limit them to around 20mph... while they're required to share the street with cars that are free to travel at almost any speed.

[deleted]

Re: Benefits of Not Using an IDE

#88

I think the benefits of working with KISS tools - the opposite of 'everything but the kitchen sink' in Emacs parlance - is that it significantly lowers the cognitive load. This may sound odd when comparing a rather bare-bones vi + tools setup with a bells-and-whistles IDE like Visual/Android/whatever Studio but it just ends up working that way for me. I already need to keep enough state in my head for the project I'm…

Absolutely agree. The myriad of overlapping tools were the biggest problem for me when learning javascript.

Re: Benefits of Not Using an IDE

#89
post #4

A good ide is all about auto completion and refactoring tools. The autocompletion means you don’t have to spend as much time memorizing apis, so you can focus more on simplifying your design and minimizing coupling. In something like unreal engine, the intellisense really sets ides apart. The refactoring means you can quickly and easily make large changes to make the code easier to work in. You can just work signific…

I'm surprised how many of my colleagues don't use the debugging features of their IDE. Being able to step through code line by line and see all the variables states at any time and evaluate arbitrary expressions given those states seems far superior to print/console based guesstimation. However, somehow my colleagues still do great work!

Concurrent code is not easy to debug line by line. Logging is a good alternative.

Re: Benefits of Not Using an IDE

#90
When people say "no IDE" what they usually mean is the concept of an IDE turned on its head.

Your command line with vim/emacs and other tools that together arrive at the same feature set as a Integrated Development Environment are still... a development environment.

Not using an IDE doesn't mean you can't have autocomplete, syntax checking, linting, automated rebuilds, and all that other good stuff. It's just not all in one package.

And yes you shouldn't force your choice of (integrated) development environment on others. Different people have different needs: News at 11.

Post reply on HN