Consequences of Badly Planned (or unplanned) Software and Not Writing Clean Code

We all made small personal projects without making any kind of planning or documentation.

But when we get involved in big-scale projects, we need to have a solid plan. This article written by Lyal Avery in 2018, demonstrates the result of an investigation to understand the importance of good planning and documenting every detail of projects, using models and design documentation, using a good architectural structure before starting a new software project.

There are very heavy consequences of unplanned software and the importance of having good, clean coding practices and solid documentation before starting a software project is crucial.

When I spoke to them [software engineers] about the need for documentation and good planning, they didn’t want to understand me or they just didn’t care.

According to research, 20% of software projects fail due to bad code.

Bad Code Study from Stripe

Our work is mainly divided into two parts:

  1. Programming.
  2. Designing.

Many give a lot of importance to programming but few give importance to good planning and making a solid design with solid structures that perhaps lasts months to do without writing any code.

Doing projects with bad design results in having badly done projects, or perhaps being thrown away without even finishing.

Believe me, I have met software engineers who have more experience than me, who had plans for software that in their dreams is worth thousands of dollars and explaining their wonderful ideas on a single sheet of note paper… And when I spoke to them about the need for documentation and good planning, they didn’t want to understand me or they just didn’t care, all they wanted was code and code.

Everything ended without finishing their wonderful ideas because they had never devised a perfectly documented software plan.

If you’re doing serious work, you have to start seriously.

For this reason, it is very important to do good preparation. Badly written and unplanned code can save you an hour of time but maybe it can cause you 20 hours of searching and fixing later when the bugs come out. Have you ever had any good or bad experiences with SDLC? It would be a good idea to share your experience and thoughts. Maybe you can help others with your comments.

– Goktug Erol

About Goktug

Goktug Erol

Goktug Erol is a full-stack software engineer specializing in web and app development who is passionate about creating powerful, user-friendly products that empower people to be successful. With a background in software development, usability engineering, and project management, Goktug Erol has the experience and skillset to bring innovative ideas to life. He has a proven record of delivering efficient, high-quality software solutions that enable individuals and businesses to reach their full potential. Follow his journey on Twitter to see how he's making an impact in the tech industry.


Follow Goktug @ Twitter | Facebook | LinkedIn

comments powered by Disqus

Related Posts

Solving a Common Interview Question: the Two Sum Algorithm in JavaScript

Imagine you’re at a lively party, and everyone is carrying a specific number on their back. The host announces a game – find two people whose numbers add up to the magic number, and you win a prize!

Read more

Remove Duplicates from Arrays and Strings in JavaScript

Removing duplicates is a common problem in programming that can arise in various contexts, such as cleaning up data or ensuring unique entries.

Read more

Remote First: 5 Websites for Remote Job Opportunities

Would you prefer to work in an office, or while sitting at a beach somewhere in Thailand (i.e. remotely)? Okay, maybe there’s no beach in this scenario, but there’s definitely silence, and maybe your cat.

Read more