When a dev leaves a project in the middle, and someone else has to continue their shit, that's the worst fucking thing ever!
3000+ lines of codes in just one class? Fuck!
I don't even know where to put my code, where to put debugger break points, where to... fuck fuck fuck!!! >_<

Isn’t this how software actual evolves, though. Agile? Don’t make me laugh. Applications evolve by devs working on them until they see they’ve added so much technical debt they get scared and jump. Then the next dev comes in and refactors the code, adds a few more features, and the cycle repeats.

I would start by braking that class apart one way or the other.

But the first step would be to make sure what is public and private and then document any external dependency and any class level state.

I have had to do this several times :/

Once you know what it uses and what it presents you can try to map out what is used where without thinking about the inside.

At the best of times you find groups of public functions that are used together.

Then check for each group what internal state it touched and what external resources it uses.

Then you can make sure everything is testable, this will depend on the language.

Then write tests and then get to refactoring.

And the bonus is that once your done you do not only have better code but tests to keep it in line :)

Sames feels bro 😑😑😑

these are rocky numbers !