-32

submitted 3 months ago by codeinabox@programming.dev to c/programming@programming.dev

14 comments fedilink hide all child comments

About 10 years ago, I realized all the best programmers I had worked with had something in common: they were fast. By that I mean that they moved quickly: we’d discuss a problem and an hour or two later they’d already have a patch ready or a prototype to show off.

It took me a while, but eventually I realized: they weren’t fast because they were great programmers, they were great programmers because they were fast.

you are viewing a single comment's thread
view the rest of the comments

[-] bizdelnick@lemmy.ml 2 points 3 months ago

In my country, they say that you need to be fast when catching fleas. They also say, I can type 2000 characters per minute, but the result is a total bullshit.

I can be very fast when working on the project that I know very good. An I can be very slow when I need to understand how the code works, to learn some new API, new tools etc. If I always were fast, I'd make a lot of stupid mistakes and had to fix them wasting much more time than I spent for initial investigation.

this post was submitted on 01 Jun 2026

-32 points (16.7% liked)

Programming

28304 readers

439 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

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 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev