Skip to main content
4 answers
3
Updated 349 views

How did you choose your programming software and did you stick with it throughout your career?

Would love to know the best programming software out there


3

4 answers


0
Updated
Share a link to this answer
Share a link to this answer

Jeff’s Answer

Hi Kevin,

Great question! And, the answer is that there is no best language. The important thing is to learn the basics and keep learning and evolving.

When I began my career, back in the stone age, all we had was functional languages like Fortran! As my career progressed, the industry evolved into object oriented languages.

I spent much of my career programming in assembly language, developing BIOS code but I've also used C, C++, JAVA, Javascript, Python, R, ADA, SQL, Access, PL/1, PL/S, Basic and I'm sure I'm forgetting a few!

If you understand the basics, you can adjust, adapt and learn new languages easily! I was hired as an IBM programmer to write PL/1 and PL/S code even though I had never seen them. They figured that, since I programmed in 20 different languages in college, the 21st and 22nd would be easy!

Good luck!
0
0
Updated
Share a link to this answer
Share a link to this answer

Sandeep’s Answer

The choice of programming language is often misunderstood. It’s not about finding the best one, but the right tool for the job. The idea of sticking with a single programming language throughout an entire career is outdated and actively harmful to your growth.

My own career, like that of many senior engineers, has required me to master multiple languages, chosen based on the problem domain. For instance, early in my career, I likely used Java or C++ for building robust, high-performance back-end systems, which were standard for enterprise architecture at the time. Later, as I moved into Data Science and DevOps, I shifted to Python for its excellent libraries and quick development capabilities in Machine Learning, and I specialized in SQL for data manipulation. This continuous need to adapt highlights that the language itself is secondary to the underlying engineering principles. Things like algorithms, clean code architecture, and debugging skills remain constant regardless of the language.

The "best" programming language isn't one specific tool; it's the one that delivers the most value for the current project. Today, the most valuable languages are those that dominate specific, high-demand fields: Python for AI/ML and Data Science, JavaScript/TypeScript for modern web development (full-stack), Go/Rust for high-performance systems and infrastructure, and SQL for all data-centric work. To future-proof your career, don't commit to one; instead, commit to being polyglot, mastering one language for high-level logic (like Python) and another for low-level performance (like C++ or Go). Your value as a programmer comes from knowing which language to select and why, based on performance requirements, community support, and the existing technology stack.
0
0
Updated
Share a link to this answer
Share a link to this answer

Ted’s Answer

Engineers often switch between different IDEs and programming languages during their careers. Once you master one, learning another becomes easier, especially with new AI pair programming tools.

If you're deciding what to learn first, identify the type of programming you're interested in, like web development, machine learning, or data engineering. Then, find out which languages and tools are most popular in that field.

Concentrate on turning a problem statement into a complete solution. Also, learn good programming practices and methodologies, as these apply to any language. Reading about Clean Code can be very helpful.
0
0
Updated
Share a link to this answer
Share a link to this answer

Manuel’s Answer

Hi, Kevin.

Honestly, only a few times I have been able to choose a programming language or IDE, most of the times it was imposed by the project requirements, previous developments, etc. I have programmed in Basic, Delphi, C, C++, Java, Javascript, PHP, some DB 4GL, Go, and mostly Python lately.

My advice would be not to stick to any particula language, IDE or programming libraries or frameworks. Things evolve and you may discover new tools over time. I think it is better to stick to good practices, design patterns and architectural paradigms than to any particular set of tools.

Good luck,
Manuel
0