Lesson I learned from coding

I’ve first started programming when I was 15 with QBasic. In the past two decades of coding as a hubby and later as a professional developer while coding in 7 languages, I’ve learned a set of useful skills and life lessons. I’m going to share them here:

  • Learning is the greatest life skill everyone should develop, so first learn how to learn.
  • Planning and Discovery are two skills that are requisites for success. Both can be learned.
  • It’s important to know when to learn the skills while doing, and when to use the skills for learning.
  • Processes that can be optimized should be optimized, and most things can be viewed as processes.
  • Routine tasks that can be automated, should be automated.
  • Most people can’t provide good advice, yet your best source of advice can only be among them.
  • Mindset comes before mastery.
  • Programming is a combination of two skills: Problem-solving and Coding. Development is the combination of two skills: Programming and Delivering results.
  • Frustration isn’t that bad, when success brings greater gratification.
  • Always build to use, and create value. If you can’t create something that brings value to people, then create something that is challenging to make and has learning value for you.
  • There are few universal constants, making change inevitable. One can only adopt or accept deprecation.
  • Failure is part of life. Look at it as a benevolent teacher.
  • Perfection is unattainable, or at least not worth the effort. Do or make something that is worth the effort, and only then start to improve it.
  • Assume nothing, Test everything, and document every little bit of detail.
  • Burnout is real. Don’t overwork, and measure and control work time periods.
  • A problem simplified, is a problem half solved.
  • Names have power. How we define and call things changes how things are perceived.
  • Plan your work as if you’re, and be diligent and hardworking in doing it.
  • Problems don’t go away when you don’t see them anymore. Solve problems at root.
  • Plan and act for re-usablity.
  • There is no shame in using other peoples work, as long as you can take them apart, study and understand them, and if possible improve them.

Leave a Comment