hi is it normal to have 900 lines of code in just 1 out of 51 java classes

Depends on what those lines do?
I had a file that contains around 2000 lines, then I ended up dividing it into smaller files. My file was responsible to fetch data from API, I started with a small API and it was a random side project, when I decided to make it live longer I divided my file into smaller ones each responsible for one thing, for example one for fetching user info, auth token ..etc. another for fetching notes and so on

@gitpush pretty much what im doing right now. i keep adding new shit and the code gets more and more verbose and complicated to understand. should i first refactor the code and then add new shit or should i add all the shit needed and then refactor at the end when im done adding all shit and shit like that

@SukMikeHok If you have time, you better stop, divide your code, refactor what needs refactoring then add new stuff, or else refactoring will be a waste of time and useless

@gitpush thsts the thing my 6th semester starts 19th february this year and i MUST AT ALL COST finish this shit before my fuckin college because my time will be extremely fuckin limited...

@SukMikeHok Then write as much comments as possible so that when you refactor you have a clue what is going on, don't ignore I went that way few years ago and ended up regretting it lol

No. Split responsibilities

@iKameo shut

@gitpush well actualy I've noticed that messy codes slows me down exponentialy. Writing properly separated components gives a nice boost in productivity and it does NOT require any more time to do it right.

I'm not pushing. Just saying. A turtoise won the race after all, and race was all 'bout speed

@netikras I second this for sure. Never knocked my head against the wall when working with properly written code

@gitpush 😣😣😣😫😫😫😫😫 i am going through a nightmare rn...