Hack Forums
[HF V3ndors] What's One Programming Habit You Wish You Learned Earlier? - Printable Version

+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Coders Lounge (https://hackforums.net/forumdisplay.php?fid=5)
+---- Thread: [HF V3ndors] What's One Programming Habit You Wish You Learned Earlier? (/showthread.php?tid=6329471)



What's One Programming Habit You Wish You Learned Earlier? - Mxstermind - Jul 31, 2026

What's One Programming Habit You Wish You Learned Earlier?


If you could go back and give your younger self one piece of programming advice...

What would it be?

Could be technical.

Could be career-related.

Could be about debugging.

Documentation.

Testing.

Reading code.

Architecture.

I'm always interested in lessons that only come with experience.


RE: What's One Programming Habit You Wish You Learned Earlier? - TooBuck - Aug 1, 2026

Committing myself to learning C. I never learned it in my adolescence. As a working adult, you have less time, and certainly less energy at the end of a day to learn.

I feel like other languages make me lazy. Most of the ones I've learned are object oriented languages. C makes you grind harder, and (in my opinion) grows your knowledge.


RE: What's One Programming Habit You Wish You Learned Earlier? - Mxstermind - Aug 2, 2026

(Aug 1, 2026 09:08 AM)TooBuck Wrote:  Committing myself to learning C. I never learned it in my adolescence. As a working adult, you have less time, and certainly less energy at the end of a day to learn.

I feel like other languages make me lazy. Most of the ones I've learned are object oriented languages. C makes you grind harder, and (in my opinion) grows your knowledge.

Great feedback sir, thank you.


RE: What's One Programming Habit You Wish You Learned Earlier? - BabaNugga - Aug 18, 2026

Writing the thing that already works down before I touch it. Half my bugs were me 'improving' a script I did not understand anymore.


RE: What's One Programming Habit You Wish You Learned Earlier? - Clifftonn - Aug 29, 2026

Check every return value. recv(), malloc(), fork() — they all fail. Silent failures in infrastructure code are nightmares to debug. Second habit: write the test before the fix. If you can't reproduce it, you didn't fix it.


RE: What's One Programming Habit You Wish You Learned Earlier? - code_g33k - Sep 6, 2026

(Aug 1, 2026 09:08 AM)TooBuck Wrote:  Committing myself to learning C. I never learned it in my adolescence. As a working adult, you have less time, and certainly less energy at the end of a day to learn.

I feel like other languages make me lazy. Most of the ones I've learned are object oriented languages. C makes you grind harder, and (in my opinion) grows your knowledge.

I definitely agree. I was 18 again I'd stop video games and talking on the phone a lot to learn C/C++.


RE: What's One Programming Habit You Wish You Learned Earlier? - rodrigayz - Sep 8, 2026

prob web dev in general cuz thats the fastest to market/get money from, i went thru c++ at first which made it very slow for me to make projects and the specific projects i needed it from was some automation project which could of been done with python, more than a decade ago.

but now i dont regret, even though i did in fact learnt to use python, javascript, and so on, AI agents nowaday make me x100 the work output and also the money coming in.


RE: What's One Programming Habit You Wish You Learned Earlier? - Thalion - Sep 9, 2026

I often wish I'd taken the time to become really good at JavaScript and CSS earlier. Now that they're pretty much cornerstones of web development, I'm a little bitter. :^)


RE: What's One Programming Habit You Wish You Learned Earlier? - CapoCorleone - Sep 23, 2026

Probably not skipping the boring stuff: reading the docs and checking return values before assuming it works.

I used to copy a snippet, tweak it until it looked right, then wonder why it exploded under load. Now I read the man page first, test the failure cases, and commit small steps even if the code is ugly. Feels slower at first, but it saves you from the 3am “why did this work on my machine” moment.