There are definitely wrong ways to develop code. Maybe there are different ways to do things right and the right way depends much on the business... But..
In every object oriented language SOLID is important. In functional languages Single Responsibility, open closed and Dependency Inversion are still important. SOLID principles enable
you for unit testing.
If you really have 1 Millions lines of code, you should organize your code. Microservices or self contained systems are one way, but brings more complexity to your stack. So here are different ways.
There are much code smells (see Martin Fowler Refactoring) easy to detect, easy to remove.
Honestly, there are a lot of wrong ways. But there are good ways. And it's much easier to change from a good way to another good way, then from a bad way to a good one.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There are definitely wrong ways to develop code. Maybe there are different ways to do things right and the right way depends much on the business... But..
In every object oriented language SOLID is important. In functional languages Single Responsibility, open closed and Dependency Inversion are still important. SOLID principles enable
you for unit testing.
If you really have 1 Millions lines of code, you should organize your code. Microservices or self contained systems are one way, but brings more complexity to your stack. So here are different ways.
There are much code smells (see Martin Fowler Refactoring) easy to detect, easy to remove.
Honestly, there are a lot of wrong ways. But there are good ways. And it's much easier to change from a good way to another good way, then from a bad way to a good one.