this post was submitted on 05 Apr 2026
106 points (98.2% liked)

Programming

26402 readers
220 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
UlrikHD@programming.dev
bugsmith@programming.dev
Spyro@programming.dev
106
If you thought the speed of writing code was your problem - you have bigger problems (debuggingleadership.com)
submitted 2 days ago by codeinabox@programming.dev to c/programming@programming.dev
9 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.bestiver.se/post/1030154

Comments

you are viewing a single comment's thread
view the rest of the comments
[โ€“] MousePotatoDoesStuff@lemmy.world 3 points 1 day ago (1 children)

That's part why I don't use VIM for software development, even though I love the motions.

It's a perfect solution... for the wrong problem.

(Other reasons are:

  • I like the features that help me handle the code and catch mistakes before running it

-I paid for the entire RAM and I'm going to use the entire RAM )

[โ€“] FizzyOrange@programming.dev 2 points 6 hours ago

Vim's solution to fast editing also isn't very compelling since multiple cursor editing was invented. You can get 90% of the editing speed by learning 1% of the shortcuts. And the UX is slightly nicer since you get immediate feedback.