41
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Aug 2024
41 points (97.7% liked)
Learn Programming
1616 readers
1 users here now
Posting Etiquette
-
Ask the main part of your question in the title. This should be concise but informative.
-
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
-
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
-
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/
Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
I agree on doing. I don't think I've ever picked up a good coding practice by reading about it and doing it, I'm just not wired like that. Not that I didn't read good coding practices, but most of them I dismissed as overkill... until later when I realized that while working to reverse engineer and cleanup my old, ugly, code, I had independently "invented" a lot of those practices that I had originally dismissed.
That's the test right there imo, you can't really know how bad your code is until you've been away from it long enough to no longer have memory of your intentions on your side. "Wtf is this variable for again? When I figure it out I'll rename it to be more descriptive". "Oooh, this function is doing more than it's name implies? Tf was I thinking?"