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…
Why do doctors memorize medicines and their effects? Because it's faster to retrieve from memory than from documentation, even automatically presented documentation. It removes a context switch. The "brain cycles" are only run while doing the memorization, not while actually doing the work. > I don't recall ever struggling to remember syntax of languages I frequently code in. Because you've memorized it.
Benefits of Not Using an IDE
121–130 of 389 posts
Re: Benefits of Not Using an IDE
#122The author seems to use IDE for one purpose only: to auto-generate boilerplate code. But this is far from the only benefits of IDEs! I rarely use IDEs for code generation, I don't even like autocomplete. For this stuff I use code snippets; I develop collections of those for any language I use. You don't need an IDE for it; any good text editor has such features. For me really important features of a good IDE are: - N…
Re: Benefits of Not Using an IDE
#123Listen, long story short: just say no to nonsense like this. Given the choice of a) tooling, or b) no tooling, you’re not being smart, cool or clever by choosing b. Obviously, what tools you pick are important and heavy IDEs like IntelliJ are a trade off between speed and functionality, and yeah, more nimble tools do exist, and it’s definitely worth trying different development tools to see what makes you most produc…
It's not being lazy. There is no need for me to use an Integrated Development Environment. Many of the most highly productive people use Separated Development Environments. The integration is most times not necessary. I have never had an IDE provide a feature that I needed and couldn't quickly create or obtain. People let you install your tools in your monolithic IDE package. Why are you so insistent on degrading peo…
Re: Benefits of Not Using an IDE
#124Re: Benefits of Not Using an IDE
#125Re: Benefits of Not Using an IDE
#126Not having an IDE doesn't make me remember things. In my case it just means I use a very limited subset of the features, because I'm not being reminded of the things I don't remember and I don't get to see newer language features unless I happen to read a blog post or see something here on HN. I tend to fall back to implementing things with primitives and fail to use built-in functionality.
For the longest time I was a proponent of limited tooling. In many cases its good to know what you're automating or simplifying because I often found myself in situations where I may have environments I need to do things where I didn't have my tooling to lean on. In the past, this was possible without too much pressure on cognitive load. In modern code bases with all sorts of libraries and layers of abstraction ontop…
I don't know that I view that as a positive. A lot of software development is about managing complexity. IDEs allow developers to be sloppier.
In the same way that faster CPUs have resulted in less optimized software over the years, IDEs have resulted in more complex software.
Re: Benefits of Not Using an IDE
#127No thanks I can't live without Intellij Ultimate + ideavim, I just can't...
I get 90% of the features with LSP. Faster performance. Magit. Extreme configurability. It's easier to write a quick function in elisp and have it at my fingertips at anytime. (ie. M-x my/do-repetitive-thing)
Re: Benefits of Not Using an IDE
#128A 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…
Refactoring is where it's at for me. The ability to rename functions and variables across not just a local file, but all references in the code base is huge. Relatedly, the ability to find all usages of a symbol and navigate between them is indispensable for me at this point.
Re: Benefits of Not Using an IDE
#129Sometimes people need to prove that they are a rare breed of pure developer. Their superior discipline and tastemaking in the development toolchain far surpasses the masses of regular developers who are dependent on old slow crutches to get any meaningful work done. Meanwhile there are real 10x developers out there that while they care about the tools stay out of the weeds of them. This line of blog post reminds me o…
Real men don't need IDEs, nor filthy GUI tools for kids. Shit was the defacto culture at the two Linux only shops I've worked at
Re: Benefits of Not Using an IDE
#130I 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…
Why do doctors memorize medicines and their effects? Because it's faster to retrieve from memory than from documentation, even automatically presented documentation. It removes a context switch. The "brain cycles" are only run while doing the memorization, not while actually doing the work. > I don't recall ever struggling to remember syntax of languages I frequently code in. Because you've memorized it.