How a Clean Codebase Becomes Unmaintainableby@seeni
1,499 reads
1,499 reads

How a Clean Codebase Becomes Unmaintainable

by Seeni3mAugust 30th, 2022
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

Too Long; Didn't Read

Code should always have a pattern/style. We always strive towards it. But leave it out for a year without a big feature, it might become unrecognisable to you. This is my learned experience from working in Small-Mid Scale Software Companies. As you go into handling many projects, you start to loose control of the packages or libraries that are being used in the organisation. Eventually, your project will be combination of N different coding styles with 2N unit-testing styles. There is no escape from it as you move away from the codebase.

Companies Mentioned

Mention Thumbnail
Mention Thumbnail
featured image - How a Clean Codebase Becomes Unmaintainable
Seeni HackerNoon profile picture
Seeni

Seeni

@seeni

Figuring out the world just like you.

About @seeni
LEARN MORE ABOUT @SEENI'S
EXPERTISE AND PLACE ON THE INTERNET.
L O A D I N G
. . . comments & more!

About Author

Seeni HackerNoon profile picture
Seeni@seeni
Figuring out the world just like you.

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite