CodeGym /Courses /C# SELF /Creating Products: How Modern IT Products Are Born

Creating Products: How Modern IT Products Are Born

C# SELF
Level 8, Lesson 6
Available

1. "People Aren't Born, They Are Grown"

Well, since you're still here, let's continue. "And I will show you how deep the rabbit hole goes" © 🐇

Let me tell you how the product development process happens — we'll go through steps from the highest global level down to the very bottom — writing code. I think you'll discover some interesting things…

Modern IT products are no longer written; they are created. They are assembled from libraries, frameworks, third-party programs and products, or even use remote paid or free internet services 🧩.

A modern product is a whole zoo of technologies, services, solutions, and processes. Some work is done by people, some is automated, and the remaining 90% are handled by cloud services in data centers ☁️. The world is no longer what it used to be.

But the first thing you'll notice is constant changes. You're no longer just writing programs, you're making changes to them.

2. Constant Changes

You come to work and join a team of 20 people who have been working on a product for 5 years. Currently, users have access to its 7th version. Your task will be to make changes to this product. Small ones, so as not to scare off current active users.

And it won't be easy, because the product is already running. It has clients, and they pay 💰. So, nothing can be broken. Making changes to an already working product is several times harder than to a new one. There are special standards, migration protocols, and utilities for this. A joke comes to mind:

Two old friends meet: one became a mechanic, the other a surgeon... Each has their own life, worries, joys... They tell each other everything, and then the topic of salaries comes up. The auto mechanic says: "Well, I get 30K a month and am very happy with that, how about you?". The cardiac surgeon says: "Well, I make about 100K per operation...". The mechanic gets interested: "Strange, why such a big difference? We do basically the same thing — change parts". The surgeon says: "Well, come to the car, start it...". The mechanic starts the car, the surgeon opens the hood and says to the mechanic: "See, the engine is running? Replace it!" 😂

Even if a miracle happens and your team wrote a product from scratch for a whole year and only then released it, do you know what will happen next? If your product becomes successful, the product owner will want to develop it further. Release a new version, add some functionality. Or at least run some experiments. And do you know what will follow? Changes 🙈

3. Product Value

From the perspective of modern development, only the code that is already released and the feature that users are actively using has value. If you've written code, it’s stored somewhere, works, but people don’t use it, then its value is close to zero. That's why all code should get to production as early as possible 🚀

Your code should go through these stages:

  • ✔️ You wrote it and made sure it works.
  • 🔍 Your TeamLead reviewed it and merged it into the main branch in Git.
  • 🧪 Tests during the build showed that you didn't break anything important.
  • 🧩 Integration tests confirmed that the product works as expected.
  • 🛡️ The QA checked this code and approved it for release.
  • 📦 Then you need to build a new version of the product and release it on the server.
  • 🐳 The new version should be packaged into Docker Images and released.
  • 🗄️ You might need to run migration scripts and update databases or other third-party solutions.
  • 📊 Then logs need to be collected on the server to ensure everything works correctly.
  • ⏪ In case of emergency, if something broke, you need to roll back the build, restore the previous database state, and not lose user actions performed while working with an unstable version of the product.

Most companies have now solved these tasks: new processes are in place, specialized people are hired, and security protocols and quality standards are introduced. The bigger the company, the less time passes from writing code to it reaching production and becoming valuable — starting to benefit people.

In most companies, this path takes about two weeks. But some companies release every week or even daily. The exceptional ones — several times a day.

Written code is worthless. Value only comes from code that runs in production.

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