The focus on quickly bringing a product to the market To compete with and race with other companies to introduce a new product or service it came with a huge mess in the coding world, although the concept of -bringing a product to the market as fast as possible- is profitable From the point of view of the business world, but it makes programming world very messy.

For business, it doesn’t matter how your code looks like, all that matters that

is your product work fine?

is it work without any Failure?

is it meet customer requirements or business needs or whatever stakeholders need?

It’s all about making an executable program in a specific period of time that meets the requirements, it doesn’t matter what behind the scene.

So you maybe thought “if everything works correctly, and the output of the product is what desired, Then where is the problem?”

The problem is that you focus on making everything work before the deadline, but you neglected the core basics of clean code and using the best architecture and design patterns that serves your project, you must focus on both writ clean code and finish your work before the deadline and always remember that

“Just because something works doesn’t mean that it cannot be improved”

So it’s time to stop writing spaghetti code

are you ever stuck with working for someone else code?-maybe the employer was working before you or anyone from your team-

or even open-source code you have just downloaded but you find out that is very hard to modify it and add your features to it, because it’s hard to know the flow of the code, and there are no comments to help you or documentation for this code.

If you ever face such problems, so Its time to learn and stop repeat these mistakes, you may be wondering what is Spaghetti code!

Spaghetti code_ is a pejorative phrase for unstructured and difficult-to-maintain source code._

Spaghetti code_ is a source codes that are tangled up. which, making control within a program very hard to follow._

Spaghetti code is a code that doesn’t follow any rules it just was written as the author wanted to write it, which make other programmers struggle to understand it, or even the author himself.

The advantage of spaghetti code

you don’t tie to any rules, you just coding as you want without Bear the burden of learning new concepts and following it, which will make you finish what you want faster.

The disadvantage of spaghetti code

• Blurry vision.
• lake of using architecture patterns.
• lake of using design patterns.
• It is a complicated mess.
• However programs work, they are difficult to read and maintain.
• they are confusing and are also prone to errors.
• difficult to add more features to the program or integrated it with other systems.
• hard to optimize program code.

In the end, we can say that spaghetti codeis a very very ugly messy code that is working fine.

The cost of writing spaghetti code?

After rushed the product to market and had made a huge mess in the code, as added more and more features, the code **got worse and worse **until simply couldn’t manage it any longer. It was the spaghetti code that brought the product down, as the mess builds, the productivity of the team continues to decrease, approaches zero, as productivity decreases, management does the only thing they can, they **add more staff to the project **in hopes of increasing productivity.

the new staff, and everyone else on the team, are under pressure to increase productivity. So they all make more and more messes, driving the productivity toward zero. Until they realize that the old code will never be helpful for achieving new progress, then they must build a new system that does everything that the old system does. Not only that, they have to keep up with the changes that are continuously being made to the old system. Management won’t replace the old system until the new system can do everything that the old system does.

#experience #clean-code #development #programming #efficiency