42
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
42 points (97.7% liked)
Learn Programming
1625 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
The already given advice is good: use linters, read.
However, just to say something different: Write a lot of code and do complex stuff. The reason you write code that "just works" is most probably because that's all you've needed.
Good code is good for a reason: it's maintainable. If you never write code that needs to be maintained, you're going to go uphill. If you write complex code you'll NEED to write maintainable code. After refactoring the same kind of code multiple times, you'll see why it is a bad pattern, and you'll learn good code because you need it.
Avoid "simple" languages like python or JavaScript. They let you patch old code too easily to work with new code, creating a mess of legacy code that you'll be afraid to touch. Rust, C++, Ada, java and many others are much less forgiving on bad code, specially due to their type system and compilers.