Programming

23042 readers

287 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 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

How exactly does one get better at programming? (lemmy.world)

submitted 4 days ago by chrischryse@lemmy.world to c/programming@programming.dev

77 comments fedilink hide all child comments

So I’m an on/off noobie but have been focusing on actually sticking with programming what I’ve been working on is Python but this question is for programming in general. For me it’s hard but I want to see how I can get better

Like are these good ways to get good:

Follow tutorials, then work on ways of adding your own twists or changes? Or trying to code it in something else?

Work on assignments from a resource you’re using like in my case Python Crash Course and attempt to redo the assignments without looking back?

Experiment with multiple libraries and library methods or built in methods?

Please share any other ways especially ones that helped you

Also when would be good to start a new language after learning one

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

[–] mr_satan@lemmy.zip 4 points 4 days ago

I'd say it takes a certain curiosity to make all of this work. Like the other day I read up on SQL indexes and how they work under the hood. I didn't need to, I know what they do and what I needed them to do. But there was this itch when I realized that I don't know how they do it.

And there are many such things depending on the specialty. I'm in web dev and often the work I do is very detached from actual communication protocols and such. I see devs that don't even know how cookies work in an MVC app. And while it's not necessary, it helps a lot to have basic understanding of what happens when you call an API, how exactly HTTP differs from HTTPS, even what happens at TLS and TCP layer of things.

I consider myself a generalist and it's this curiosity that makes me adequate in many different subspecialties. I'm not the best at things, but I can get shit done myself when I need to.