Working With A Bad Codebase

How do you deal with a terrible codebase? - Reddit

Incremental change/Boyscout refactor. With every pull request, try to leave the campground cleaner than you entered it. Do some low impact ...

What are some ways to deal with a terrible code base at your job?

I agree with others here that there's not a lot to be done with the huge existing code base because it's been so tested.

Ask HN: Codebase at my work is a complete mess, what should I do?

Any single coder is almost always going to produce code that looks messy to anyone else. You can say you're not going to work on code like that, ...

Working With A Bad Codebase - Nduli's World

I've worked with codebases that have made me frustrated. Some of the features I've seen include: Fixing such a codebase needs a lot of thought put into it.

Should I quit my job if I am taking over a bad code base with not-so ...

My advice would be to just try to stick with it. If you run from a job every time you encounter crap code you're going to be running from every job under the ...

How to tell your client how bad their codebase is?

Without time and discipline to refactor the design to adapt to the new requirements, most developers will look for the quickest way to make it work. This is the ...

What to do when you inherit an unmaintainable codebase? [duplicate]

Without them, it will simply be impossible to do anything with it. The senior developer is working on trying to at least comment all his code ...

Rage Against the Codebase: Programmers and Negativity - Medium

Going into the future, they begin to accept that bad code is simply a reality of software, and it's their job to make it better. Since there's ...

What I Learned by Switching to a Poorly-Structured Codebase

Well-written code becomes more important when you're writing it for an organization. If you work on a project and later leave the organization ...

What's the worst codebase you've ever worked in? - DEV Community

Oh, I've definitely come across some messy codebases! The worst one I worked on was filled with spaghetti code—no documentation, inconsistent ...

Ask HN: Have you ever inherited a codebase nobody on the team ...

My number 1 red flag of working with a developer, unless they are very early in their career, is hearing them describe a codebase as awful. Most ...

Work effectively on a large codebase | by Zhaojun Zhang - Medium

Expose yourself to high quality code and avoid reading bad code. Any codebase may contain many bad code that you shouldn't follow. For me, I ...

First Job Tips: Overcoming the Anxiety of a Large Codebase

Throwing yourself in the deep end can sometimes be terrible advice, but there's a grain of truth in it. Perhaps wading into the water is a ...

Developers Are Leaving Jobs to Escape Bad Codebase - DZone

Our Findings · 82% believe that lack of proper development practices affects their job satisfaction. · 62% consider code quality as an important ...

Bad Codebases Shoo Developers Away | HackerNoon

Unlike salary and remote work opportunities, understanding the state of the codebase and software development practices can be challenging.

Is it normal to struggle so much on a bad codebase or is it just me?

if you plan to stay there long time then the problem of legacy code can be handled, you should set up as many meetings as possible with the ...

How Good Developers Repair Bad Codebases | by Milos Zivkovic

Don't let your codebase slip away. Set up rules. Start with static code analysis. Progress with mandatory behavior and UI tests, on each build.

How to Address Your Coworker's Bad Code (Part 1) - DaedTech

Build a case with evidence for the principle that you want to cover, and then also find specific, problematic instances in the codebase to ...

[A- The Impact Of A Bad Codebase] The Duty of the Developer As A ...

When a Developper produces bad code, it impacts three different types of actors: himself, his development team and his company, respectively ...

You ever quit because the codebase is so bad? - Blind

Mine told me the code wasn't important, "it just have to work", I was finding bugs left and right from the previous developer, and I'm sure ...