Live data from Hacker News

Benefits of Not Using an IDE

alexander-hansen.dev

281–290 of 389 posts

Re: Benefits of Not Using an IDE

#281
post #165

Earlier quoted context omitted.

The thing I hate most about IDEs is when they insinuate themselves into a project's development workflow so deeply that you can't make do without them. Do I have to spin up a whole session of the IDE just to run my test suite? Do I have to dig through eleven nested GUI settings dialogues to find out what the command to build the damn project is, just so I can tweak a build parameter? Is there so much boilerplate or X…

> Do I have to spin up a whole session of the IDE just to run my test suite? In the java ecosystem at least, the answer is no. But in highly CI-based situations, the answer is still no, but you DO need the CI system to be up, and the only way to run a test at all is to just commit something and see the CI system run it, e.g. because the tests require a database engine that isn't installed on your development machine.…

If you're not familiar with them, have a look at visual studio SLN files. They are exactly what was described. There is more and more being pushed into the msbuild files instead (a separate format, that is at least theoretically separate from visual studio) but the weird and underdocumented sln file still exists. And msbuild files are absolutely unreadable XML crap anyway, good luck writing one by hand.

Re: Benefits of Not Using an IDE

#282

Earlier quoted context omitted.

I get those exact same warnings in Vim :)

Vanilla vim without any extension ? Otherwise you're just reimplementing your own IDE by hand in your vim config

Obviously extensions.

And it's not "reimplementing" the whole IDE, it's choosing and configuring parts to work just the way you want it to, and it's usually done in a handful of lines.

Re: Benefits of Not Using an IDE

#283

Listen, 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…

“Power drills have batteries or cords and motors that wear down and they’re more expensive and complex and can break more easily and it’s just smarter to bring hand crank tools to the worksite.” - Nobody

Wouldn't another analogy be knowing how to navigate a boat with a sextant and a chronometer versus modern radio and GPS maritime navigational aides? The latter's more efficient, but those with deep knowledge of navigation understand how to use the former if necessary.

Re: Benefits of Not Using an IDE

#284

Earlier quoted context omitted.

In the US, class 3 electric bicycles can assist up to 28 miles per hour, or around 45 km/h. I might be able to ride 28 miles per hour on a regular bicycle, but I can't do it for very long.

Are they regulated like non-electric bikes? In Europe, I believe the main difference is insurance and license, which are required for e-bikes with motor-supported speeds > 25km/h (at least in some countries, not sure how uniform it's handled).

As far as I know there is no jurisdiction in the US where you need either a license or auto insurance for a class 3 electric pedal assist bicycle. I think you generally ride them wherever regular bicycles are ridden.

Re: Benefits of Not Using an IDE

#285
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…

When you start to work with too many languages frequently, using syntax from one while writing another is common and IDEs really help at this point. I too prefer not to remember APIs and methods, but with time, our brain starts maintaining a cache of these. Completions make this faster.

That and error detection are only features I like in IDEs. For everything else, dedicated tools are often better (but not necessarily easier) than integrated ones.

Re: Benefits of Not Using an IDE

#286

Earlier quoted context omitted.

There is a very large difference between a very smart source code editor (e.g. Visual Studio Code) and a complete IDE. I consider the first essential and the second completely useless. For editing or just navigating the source files, the smarter the editor is, the better. On the other hand I have never seen any IDE where the management of projects (e.g. adding/deleting/moving/renaming files and setting compilation/li…

> There is a very large difference between a very smart source code editor (e.g. Visual Studio Code) and a complete IDE. I consider the first essential and the second completely useless. I know VSCode is positioned this way in the market, probably to differentiate it from VS. And I switched to it from a much less “smart” editor (TextMate, which I still adore! No offense meant to TM creator/maintainers!). I’m having a…

I think the difference is that when you start out with VSCode, you tend to do things by editing text and using the CLI, and with time you add plugins and tools that makes it more into an IDE. When starting out with IntelliJ or Pycharm or whatever, you first start by trying to understand the IDE itself to generate your project, and then you start writing code inside the project. A bit like libraries and frameworks. At least that has been my experience.

Re: Benefits of Not Using an IDE

#287

Earlier quoted context omitted.

“Power drills have batteries or cords and motors that wear down and they’re more expensive and complex and can break more easily and it’s just smarter to bring hand crank tools to the worksite.” - Nobody

Wouldn't another analogy be knowing how to navigate a boat with a sextant and a chronometer versus modern radio and GPS maritime navigational aides? The latter's more efficient, but those with deep knowledge of navigation understand how to use the former if necessary.

As someone replied to GP, you should definitely know how to complete tasks with only basic tools and without advanced tools. But it doesn't mean you should only use basic tools or no tools at all. I mean I do know how to calculate without calculator but it doesn't mean I dont use calculator. I use it all the time. Of course deep knowledge almost always means that you have a strong hold on the basics.

Re: Benefits of Not Using an IDE

#288
> simply listing Reasons, The Antipattern of the directory layout of your typical Java Enterprise Project is a Testament to this., contribute to a Project, idiomatic Code in the Language of your Choice.

What's with the wild capitalization?

Re: Benefits of Not Using an IDE

#289
post #167

Earlier quoted context omitted.

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.

Traffic rules basically give drivers a way to deal with other vehicles going different speeds. So a the driver of a scooter going 20 mph and the driver of a car going 40 mph can share the same road, just like a driver of a truck going 40 mph can share the road with the driver of a car going 60 mph.

And yet, that same car can go 80 or 90 or even over 100 mph, which would be illegal on any road. Why?

Re: Benefits of Not Using an IDE

#290

Earlier quoted context omitted.

> The best developers I've found are the ones who know how to work without an IDE, even if their preference is to use one. The best swimmers can stay afloat with pounds and pounds of weight dragging the down; the worst swimmers will drown. Doesn't mean weighing you down makes you a better swimmer.

Ironically, it would make you a better swimmer - it will help you build up strength, stamina, and technique. An excellent choice in analogies.

Harrison Bergeron would never have ascended so high, were he not so greatly weighed down first.
Post reply on HN