You want to get into software engineering. What are the first steps you should take?

In my perspective I'll suggest starting with the basic fundamental programming languages like C and C++ will give you the clear view how the programming works in different paradigms and how the system understands the code you write , after you have the basics and fundamentals clear about the language execution and the programing paradigm then you can start focusing on the domain or interest areas you want to work, Directly jumping on to the latest tech stacks will give you the initial confidence but lack of understanding in underlying architecture will give you problems in future.

The first step is NEVER "Choose a programming language"! The first step is learn to program. Forget about language, language is just syntax. Programming is not about languages or frameworks, it is simply about learning to express your solution to a problem in a syntax-free way. Pseudo-code is not a programming language but is the most important tool you have when discussing problems. This allows you to discuss the issue with everyone, at all levels, from all departments in your company, and all be on the same page.

Begin your software engineering journey by focusing on C#, a powerful and flexible language ideal for a wide range of applications, from web development to game design. C# is heavily used within the .NET framework, making it a strong choice for enterprise-level software. Its syntactical similarity to languages like Java or C++ makes it a great starting point, especially if you’re interested in object-oriented programming and want to develop scalable applications.

Now you can choose a programming language. Data types, loops, conditions, expressions...these are all language-agnostic things you learn when you learn to program (not in any language, programming is agnostic). Now is the time for you to create a simple problem and solution, in pseudo-code, and then use a handful of languages to write the solution. This is where you figure out which language feels more natural to you. People think in different ways, and writing the same solution in one language may seem alien, where writing the same solution in another language just feels right. Choosing an initial language is a personal thing. Don't worry, you'll end up knowing at least 5 by the end of your career.

Learn the fundamentals, have the basic knowledge of what software engineering entails and how to become a software engineer. Some people learn a lot from knowing the a, b, c of a subject. Then go deeper when you've completely understood the fundamentals

Understanding core programming principles is crucial for any aspiring software engineer. These include basic concepts like variables, data types, loops, conditionals, and functions. Additionally, grasping object-oriented programming (OOP) principles such as classes, inheritance, and polymorphism is essential in C#. Mastering these fundamentals helps you build efficient, maintainable, and scalable code, laying a solid foundation for more advanced development.

Learning version control is imperative. Version control take away the fear of deleting code, and keeps your code free from comments that are verbose or when the code is self-explanatory. Never be afraid to delete code, that's one of the reason we use version control systems (VCS), so we can go back to any point in time. This is not about any behavioral framework like Agile, VCS has been around for decades. I remember using VCS for the first time more than 30 years ago. VCS is about protecting your code. VCS is your time machine. With VCS, reflog, blames, etc. you know who did what when, and if you follow good commit message guidelines, you know why they did it.

Learn to use Git, the industry-standard version control system, as early as possible. Git allows you to track changes in your code, revert to previous versions, and collaborate with other developers. Platforms like GitHub or GitLab host repositories where you can share projects and contribute to open-source software. Mastering Git not only helps in managing your own projects but is also a vital skill for working in teams and larger-scale software development.

C# is tightly integrated with the .NET framework, which is crucial for building applications quickly and efficiently. Start by learning ASP.NET if you're interested in web development, or Unity for game development. Frameworks like .NET provide reusable libraries, tools, and best practices, streamlining the development process. Familiarity with a framework enhances your ability to tackle real-world projects and enables you to build more complex and polished applications.

By mastering a framework, individuals gain practical experience, problem-solving skills, and a deeper understanding of industry standards. This knowledge enhances their ability to contribute effectively to software projects, accelerates development timelines, and fosters adaptability in the dynamic field of software engineering.

Forget about frameworks until you master the language you chose as your primary language. Many frameworks are over-engineered, non-componentized, and just beasts. Remember all the framework is doing is using the language you already know. If you only know frameworks, you'll never become a Software Engineer, you will be a Software Developer...there are big differences. Frameworks are useful for rapid application development (RAD), when you need to get something up and running quickly. They take care of a lot of boilerplate code, like having User accounts through registration and logging in, sending emails, logging problems. Remember, a framework is just your lab, you still have to create the formulae.

Building a portfolio is crucial for anyone entering software engineering. It showcases your practical skills, projects, and problem-solving abilities to potential employers. Include a variety of projects that demonstrate your proficiency with different languages, frameworks, and technologies. Explain your role, challenges faced, and solutions implemented for each project. A well-curated portfolio not only highlights your technical capabilities but also provides insight into your work ethic and creativity, making you stand out in the competitive field of software engineering.

Don't build a portfolio of websites, people don't want to see websites unless you want to be a web developer. Create a portfolio of solutions to problems, to show that you understand the fundamental issues. Here's an example of what I mean on the front-end: Build a web component that encapsulates a set of HTML fields, which accept an address, and validates it. In a HTML page, that allows you to just use something like: <address id="billing_address" /> to display all the fields at once, with validation build in. And none of the code is in your main code. Or take a known problem, like the Fetch API doesn't emit events, and wrap that in your own version of the API which does. Create a portfolio of solutions that solves existing problems.

A strong portfolio is essential for showcasing your skills to potential employers or clients. Start by building small, practical projects that demonstrate your knowledge of C# and related technologies. Include projects like web applications, APIs, or desktop apps. Your portfolio should highlight your ability to solve problems, write clean code, and follow best practices. GitHub is an excellent platform to host your projects, as it allows others to view your code and contributions.

Regularly practice coding for problem-solving skills, Showcase projects on GitHub for visibility and collaboration. Stay informed about industry trends and job market needs, Connect with professionals for insights and opportunities.Develop a systematic approach to problem-solving.