61–66 of 66 posts
Don't go on rushing to change existing codebase, spaghetti code is not what company's customers/clients are concerned. They are concerned about the end results.
Starting good code practice will make legacy codebase dwarf at some point.
I would do the job you are paid to do, fix github issues to the best of your ability. Leave the codebase in a better place then you found it. Include small refactors with your code, talk to the other devs frequently and find their pain points in the codebase and take stories which relate to those.
Its 100% not worth it getting depressed feelings for a codebase. I once worked at a startup with a codebase so poor that its hard to explain. The first month I was in a panic because I had 0 clue how to work with it. After a year the team slowly got it to an "ok" state. The truth is that the lessons I learned on that job have been the most important of my career.
For Joining online training batches please feel free to call or email us. Name: Minati Email: minati@maxmunus.com Skype id- training_maxmunus Contact No.-+9066638196/91-9738075708 For Joining online training batches please feel free to call or email us. Name: Minati Email: minati@maxmunus.com Skype id- training_maxmunus Contact No.-+9066638196/91-9738075708
I find the Boy Scout Rule to be helpful: > The Boy Scouts have a rule: "Always leave the campground cleaner than you found it." If you find a mess on the ground, you clean it up regardless of who might have made the mess. You intentionally improve the environment for the next group of campers. Actually the original form of that rule, written by Robert Stephenson Smyth Baden-Powell, the father of scouting, was "Try an…
For Joining online training batches please feel free to call or email us. Email : minati@maxmunus.com Contact No.-+91-9066638196/91-9738075708