Writing Better Programs: More Than Just “Making It Work” When I first started coding, my mindset was simple: if the program runs, I’m done. But after getting into data structures and algorithm design, I’ve realized that how a program works matters just as much as if it works. That’s where algorithmic design and data structures come in—they help you build programs that are not just correct, but efficient and well-structured. 🔹 Thinking Like a Programmer (Before You Code) One of the biggest changes I’ve made is slowing down before I start typing code. Instead of jumping straight into Java, I try to break the problem down into steps first. This is algorithmic design. For example, I’ll: Figure out what the program needs to do Write out the steps (kind of like pseudocode) Then translate that into actual code Doing this helps me avoid confusion and keeps my program organized from the start. 🔹 Are Some Algorithms and Data Structures Better? Yes—but not in a one-si...
Before writing programs, I had to install Java, which is simple with the right resources. First, I downloaded the Java Development Kit (JDK) from Oracle or OpenJDK . Then I ran the installer, which sets up everything you need, including the compiler and runtime. Most modern installers handle the system path automatically. Finally, I tested it by creating a simple HelloWorld.java program, compiling it with javac HelloWorld.java, and running it with java HelloWorld. For detailed guidance, I found Oracle’s Java tutorials and JavaTpoint very helpful. Learning Java introduced me to object-oriented programming (OOP), a way of designing software around “objects” that model real-world concepts. OOP makes programs easier to maintain, reuse, and expand—skills that are useful whether you’re building small apps or large systems. I explored the four main principles of OOP : Encapsulation : Keeping data and the methods that act on it together in a class, controlling access to internal ...