this post was submitted on 23 Jan 2026
548 points (91.5% liked)

Programmer Humor

29741 readers
997 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
(page 3) 40 comments
sorted by: hot top controversial new old
[–] jkercher@programming.dev 2 points 2 weeks ago* (last edited 2 weeks ago)

I feel like this has more to do with what field you work in and what language/paradigm you use. Especially if you're working within some bullshit walled garden, you may not have a choice. I'm a terminal jockey myself, but I mostly program in C, so my code is procedural and to the point. Maybe I might want some fancy smart refactoring feature if I worked in a language where half the code is boilerplate or glue.

If I have the choice though, I don't see any advantage to an IDE. It's like the combination of many tools rolled into a single, bloated UI with about 60% of their original functionality. And I guess it lets you build "projects" and choose which files will be built. That part never made sense to me. I don't need a program for that! Just delete it dog. It's in the repo!

IDE:

  • Text editor
  • Source control
  • Debugger
  • Compiler
  • Terminal
  • File explorer

I'm my opinion, these programs are just better as separate programs.

(Rant) One thing that grinds my gears... Some IDEs will leave you with the dumbest possible directory structure imaginable. Like actively hostile toward us terminal jockeys. Remember, we are repeatedly typing these things out like cavemen. For example, c/c++ developers who put their headers in a separate, but identical directory structure. Oh and let's do full taxonomy and go 10 directories deep. And what the hell, capitalize random letters and throw in some with spaces into the directory names for good measure. These things don't have to matter to IDE people, but it is something to be mindful of.

[–] Johanno@feddit.org 1 points 3 weeks ago (3 children)

You can code in a text editor. It is cumbersome and annoying, but possibly.

You should however use a good ide if you want to be productive

[–] cows_are_underrated@feddit.org 2 points 3 weeks ago (1 children)

i think it really depends on what you want to do, what languages you use and what text editor/ide you use. From my experience its usually not really worth it to get used to an IDE for bash. They all sucked. So instead I just have my emacs and my shell and I can start coding.

[–] Johanno@feddit.org 1 points 3 weeks ago

Yeah bash is sth that doesn't require an ide, but I usually have intellij already open so it helps me with bash too.

[–] raspberriesareyummy@lemmy.world 0 points 3 weeks ago (1 children)

You clearly haven't done much backend or middleware development.

[–] Johanno@feddit.org 1 points 3 weeks ago (1 children)

It depends.

You don't want to write Java or kotlin in a text editor and gather the terminal commands for compiling and stuff when you could use an ide for that.

However there is not much difference writing C in an editor and compile it with make than using an ide. But in both cases I would prefer an ide.

The only reason why I would not use one is when there are incompatibilities or other special setups that make using an ide more work than an editor

[–] raspberriesareyummy@lemmy.world 1 points 3 weeks ago

"it depends" is something I can agree on.

load more comments (1 replies)
[–] TORFdot0@lemmy.world 1 points 3 weeks ago (1 children)

Since coding isn’t my day job. I use slickedit as a nice fully featured text editor. Or notepad++ in a pinch.

Personally haven’t used a full IDE since netbeans 15 years ago in my university days

load more comments (1 replies)
[–] TheV2@programming.dev 1 points 3 weeks ago* (last edited 3 weeks ago)

Once again it seems like I don't even have an IQ ¯\(ツ)

load more comments
view more: ‹ prev next ›