Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
-
I strongly suggest that you initiate a meeting with devs, manager and PO, adress all this issues and propose course of action that you see fit.
I cannot stress enough how much of importance is for everyone to know the real situation because on the contrary you will burn out. Don't let anyone cover his ass by not telling it to the PO because whoever covers his ass is doing on the expense of the devs.
Also about possible course of action is to checkout new branch from the most forward one and address one component at the time, when done, test it and merge to that most forward branch, presumably dev or master/main.
Extract logic from components either at once or as you solve each component. It will be a mess for some period of time but in the end it will look like an app and not like flying spaghetti monster.
It is tedious work but it's doable. Also make the PO know than this is just a reality check and that this is only way to salvage the app aside starting from scratch!
Good luck! -
@SakuraNinja "on backend" is redundant though.
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
Go big or go home.
I am just sick of the things that's been going on.
Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)
Since the product owner(PO) wants to demo the application he is pushing for bug fixes.
UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.
I am not in a position to switch due to other commitments adds up a lot to frustration
rant