140
submitted 2 years ago* (last edited 4 days ago) by moon@lemmy.ml to c/programming@programming.dev

calato apoquinados comodato lardeasemos manganeaseis rebroten fletariais deserta

you are viewing a single comment's thread
view the rest of the comments
[-] BeigeAgenda@lemmy.ca 3 points 2 years ago* (last edited 2 years ago)

First of all if you solve problems that means you know enough of the subject to reason out the solution, it may not be perfect but very few solutions are.

I have been working on legacy code and maintaining old c++ code for a decade (200.000 loc) and most of the time I had to spend days debugging and reading code just to understand enough to get a possible solution, and then I still end up writing a solution that breaks in a different corner case that I never could have imagined.

So yes most of the time you feel like you don't know anything, but over time you end up knowing a lot of how that codebase works. And after two years you must have picked up something about what you are working on.

Then you have those programming language genius colleagues, that know all the tips and tricks of a language, I use them to get ideas on solutions, because they always have an opinion on what is the "right" way of doing stuff.

That's just my 2 cents.

this post was submitted on 24 Feb 2024
140 points (95.5% liked)

Programming

25696 readers
53 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