Article by Ayman Alheraki on January 11 2026 10:36 AM
In 1986, I wrote my very first computer program on MSX devices, which operated with the Z80 processor. This processor was first designed in 1976 or slightly earlier by Zilog, as I recall. Since then, I have been following the world of programming, using more than 20 programming languages throughout my journey, whether for learning, teaching, or work. However, I eventually settled mainly on C / C++, and later on JavaScript and Python, based on market demands. Nevertheless, I consider myself primarily a C++ programmer, and I love it deeply.
Even though C++ has been one of the most influential programming languages in the past thirty years or more, I have never claimed that it is the absolute best, nor that all other languages are inferior. Through my long experience, I have come to understand that programming languages are just tools used to meet specific needs, depending on time, place, project requirements, personal expertise, compatibility with the tool, work demands, and available resources for support and development.
If you master certain programming tools, have experience with them, and they fulfill your needs, then they are definitely the best for you—even if there are other tools that can provide solutions faster or more efficiently. The key is familiarity and expertise. This is the logical approach: the language you master, understand, and can creatively use is the best for you, but it is not the absolute best for all solutions.
I have encountered many language enthusiasts who fiercely defend the languages they know, simply because they are familiar with them, without considering whether they are truly the most suitable for solving particular problems. That is why I am addressing new programmers here—to help them avoid getting lost in the vast world of programming. Instead, they should focus on what the market demands when they enter the field, assess their interests and inclinations, and commit to continuous learning without getting caught in endless indecision.
Back in 1998, 27 years ago, someone asked me: "Which language do you recommend I learn—C++ or Delphi?" I replied: "Try both and choose the one you feel most comfortable with."
A few years later, I met him again by chance, and he asked me the same question. I asked: "Haven't you started learning either yet?" He replied: "No, I'm still undecided." I told him: "Go with Delphi; it's much easier for you."
Then, in 2007, I met him again, and he repeated the same question, to which I gave the same answer. By 2011, I saw him once more, but this time, I was the one who asked: "Which language did you choose and work with?" He answered: "I got too busy building my house and didn’t learn either."
I said to him: "I hope you succeed in building your house, and I sincerely hope you don’t hesitate in your choices there—because if you approach it the same way you approached choosing a programming language, you might end up with neither a house nor programming skills!"
Programming is not about blindly favoring one language over another—it is about choosing the right tool for the right task. Do not fall into the trap of endless hesitation, nor let the illusion of a perfect choice hinder your progress. Experiment, decide, learn, and start working. Experience is the key to success—not waiting forever in search of the perfect option.