Programming basics. It’s something we all need to learn but so few take the time to really put all their effort into. I was recently talking to my friend who also runs a tech blog and he couldn’t agree more.
He is a hardcore java coder and teaches people java programming basics (that’s a link to his great guide on getting started in Java) as well as the biggest principles of Object-Oriented Programming. What he told me is to never rely on sheer talent but rather to rely on the fundamentals.
I did a post last week on fundamental programming tools and it is really important that you read that too.
What Are Programming Basics & Why Do They Matter?
The fundamentals of object orient programming come down tho these things right here:
- Resource management
- Data & logical structure
- Efficiency & Techniques
This may be confusing at first but let me shortly just break each down after you watch the video my friend made encapsulating java basics into 500 words beautifully:
This is one of the biggest things people screw up. People always mishandle objects and forget to release resources. In the case of Java this causes the java garbage collector to kick in and lag the hell out of your programs.
As a beginner it’s your duty to really understand that you must only create objects when you have to and always release objects when they’re no longer used.
Data & Logical Structure
When you build a program to achieve a certain task you are tasked with creating a system for moving data in a logical fashion. It is this very structure that is so hard to change further down the line as your program approaches completion.
Yes, it may get the job done, but is it an efficient program? Does it do its job fast and with as little resources as possible?
If the answer is yes then good job! But often the answer is no and when a beginner has to go back and alter the logical and data structures of a program it’s a big “UH-OHHH” because they normally just threw the program together without much forethought to later iterations that may have been needed.
Efficiency & Techniques
The final point is efficiency and the techniques used by the coder.
If you have bad habits of using one method when in reality another should have been used that is bad technique.
Also, if you structure your programs one way when they could run faster another way that is bad efficiency.
These two work in tandem to ensure that your program runs fast and uses as little resources as possible.
I’ll have future articles on these 3 points and go even deeper into them so for any of you, my readers, can learn what it takes to really grasp the fundamentals of programming. Until next time!