CodeGym /Courses /C# SELF /The Programmer's Path

The Programmer's Path

C# SELF
Level 7, Lesson 6
Available

1. Career Ladder

Programmers also have gradations depending on their qualification. Once, concepts like "coder," "programmer," and "hacker" were used, but now everyone has switched to English titles from American IT.

There are 6 main levels for a developer:

  • Intern Software Engineer
  • Junior Software Engineer
  • Middle Software Engineer
  • Senior Software Engineer
  • TechLead
  • Principal Software Engineer

Parameters may vary from country to country and even from company to company, but the general idea is roughly as follows:

  • 🌱 Intern Software Engineer — these are interns. They are in the process of learning programming, have no commercial experience, and no experience working on large projects. Usually, they work under the supervision of more experienced colleagues. Their main task at work is to study the codebase and the basics of software development, performing simple coding tasks and participating in testing.
  • 🐣 Junior Software Engineer — these are programmers, but without serious commercial experience or less than a year of experience. They work under the guidance of more experienced developers, implementing parts of projects and participating in code review cycles. This career stage focuses on deepening technical skills and understanding project tasks.
  • 🦾 Middle Software Engineer (or just Software Engineer): have more independence in making technical decisions, responsible for significant parts of the project, start mentoring less experienced colleagues, and actively participate in architecture discussions. Usually have 2–5 years of practical experience.
  • 🧑‍🔬 Senior Software Engineer: responsible for designing and implementing complex systems, providing mentorship and leadership within the team, participating in strategic project planning, and often representing the team in communication with clients and other stakeholders. Typically have 5–10 years of experience.
  • 🧠 TechLead: responsible for the final technical outcome of the project, leads development, solves the most complex tasks, ensures compliance with technical standards, and coordinates the activities of developers.
  • 🏆 Principal Software Engineer: works at the highest technical level, often involved in shaping the company's technical strategy, developing innovative solutions, and establishing technical standards. Acts as the main mentor for technical leads and is a key expert in complex technical issues.

This is interesting. Large companies may have additional roles and sub-roles. For example, in Google, there are such roles:

  • Staff Software Engineer (L6): has significant influence on the technical policy of their department.
  • Senior Staff Software Engineer (L7): works on large-scale and complex projects, defines the strategic direction of technological development in the company.

2. Lego Products

Once upon a time (in 1975), Niklaus Wirth, creator of Pascal language, wrote a book called "Algorithms + Data Structures = Programs." Since then, a lot has changed. Modern software products are not what they were 10 years ago, and definitely not what they were 20 years ago. Talking about 1975 is pointless — it’s been 50 years since then ⏳

Modern programmers no longer write programs manually. Instead, they assemble them from ready-made parts (libraries) and write code that helps these parts interact🧩. Modern software products can consist of dozens or hundreds of programs. Some run on the user's computer or mobile devices, but most run on servers in data centers.

Many of these programs, like web servers or databases, are already written. They just need to be properly configured to work correctly. Although, over time, the configuration process can become so complex that it essentially turns into development. 🤦‍♂️

Programmers constantly fight with themselves. Instead of rewriting similar code in different programs, they write libraries that can be configured (customized) for their needs, and then just include them wherever needed.

Over the past 20 years, programmers have written tons of libraries, frameworks, and open repositories. There are really millions of them. Now, writing all code from scratch is considered bad form. Instead, you should assemble your program from quality, proven solutions — libraries, frameworks, packages, and modules 🧱

But even this approach is becoming outdated. The trend over the last 10 years is moving to the cloud, large data centers that provide everything your programs need. Want a database? We have hundreds to choose from. Need a rare, unique web server? We have those too! Any whim for your money.

3. "I am an engineer" © Elon Musk

img

No more need to write complex and boring stuff yourself. If you need some functionality, there are already ready-made libraries and frameworks for that. Your task: a) know about their existence, b) find the suitable option (there are often several alternatives with different quality and nuances), c) understand how to integrate it into your project 🎓

This makes the work only more interesting. Now you can add new features to your product 10 times faster. 30 years ago, if you needed a web server, you wrote it from scratch. 20 years ago — bought, installed, and configured it. And now — just log into the cloud portal Azure or AWS and turn on the needed service 🌐

By the way, this is one of the reasons why C# language is popular. It’s great not only for writing large solutions but also for "gluing" different components — through .NET, it has integrations with almost anything, whether databases, microservices, REST APIs, message queues, or cloud services.

Consequently, the profession of C#/.NET developer has long transformed into a Fullstack .NET Software Engineer. Modern developers need to understand how databases work (SQL Server, PostgreSQL, MongoDB, etc.) to build interactions properly. They should understand how frontend (HTML, CSS, JavaScript/TypeScript, Blazor) is structured to set up communication with the backend on C#. And, of course, Docker is now a must — it’s industry standard. 🐳

Modern development is very different from what it was 20 years ago. A programmer spends no more than 50% of their time writing code — the rest is spent on reading documentation, learning new technologies, designing, and working in teams during meetings. Solo programmers are now a rare exception.

Comments
TO VIEW ALL COMMENTS OR TO MAKE A COMMENT,
GO TO FULL VERSION