▲ 544 ▼ Code Quality (lemmy.ml) submitted 6 months ago by herseycokguzelolacak@lemmy.ml to c/programmerhumor@lemmy.ml 22 comments fedilink hide all child comments
[+] idriss@lemmy.ml 3 points 6 months ago (4 children) [deleted] permalink fedilink source parent hideshow 4 child comments replies: [–] eldavi@lemmy.ml 6 points 6 months ago (3 children) the quality of the code is dependent on the quality of the pay. lol permalink fedilink source parent hideshow 3 child comments replies: [–] Cityshrimp@lemmy.world 6 points 6 months ago (2 children) And as others have noted, how much time you are actually given. PMs and managers don’t know or care about code quality, they just want something to work NOW permalink fedilink source parent hideshow 2 child comments replies: [–] Kjell@lemmy.world 5 points 6 months ago And there is never time to maintain the code, because each project only want to add more feature/s which makes the spaghetti code even worse. In my group we had a golden opportunity to fix all old mistakes but no, we (decided by PO and group manager) needed to spend all time on proof of concepts that will go to production at earliest in 5 years. Now that opportunity is gone and we are crunching in order to meet the deadlines instead. Still with bad code quality of course. permalink fedilink source parent [–] eldavi@lemmy.ml 1 point 6 months ago My newest one is as impulsive as I am so the digressions he tasks me with have stalled out long term development plans, yet he's oblivious enough of the situation to seriously ask why progress is taking so long every year during reviews. permalink fedilink source parent
[–] eldavi@lemmy.ml 6 points 6 months ago (3 children) the quality of the code is dependent on the quality of the pay. lol permalink fedilink source parent hideshow 3 child comments replies: [–] Cityshrimp@lemmy.world 6 points 6 months ago (2 children) And as others have noted, how much time you are actually given. PMs and managers don’t know or care about code quality, they just want something to work NOW permalink fedilink source parent hideshow 2 child comments replies: [–] Kjell@lemmy.world 5 points 6 months ago And there is never time to maintain the code, because each project only want to add more feature/s which makes the spaghetti code even worse. In my group we had a golden opportunity to fix all old mistakes but no, we (decided by PO and group manager) needed to spend all time on proof of concepts that will go to production at earliest in 5 years. Now that opportunity is gone and we are crunching in order to meet the deadlines instead. Still with bad code quality of course. permalink fedilink source parent [–] eldavi@lemmy.ml 1 point 6 months ago My newest one is as impulsive as I am so the digressions he tasks me with have stalled out long term development plans, yet he's oblivious enough of the situation to seriously ask why progress is taking so long every year during reviews. permalink fedilink source parent
[–] Cityshrimp@lemmy.world 6 points 6 months ago (2 children) And as others have noted, how much time you are actually given. PMs and managers don’t know or care about code quality, they just want something to work NOW permalink fedilink source parent hideshow 2 child comments replies: [–] Kjell@lemmy.world 5 points 6 months ago And there is never time to maintain the code, because each project only want to add more feature/s which makes the spaghetti code even worse. In my group we had a golden opportunity to fix all old mistakes but no, we (decided by PO and group manager) needed to spend all time on proof of concepts that will go to production at earliest in 5 years. Now that opportunity is gone and we are crunching in order to meet the deadlines instead. Still with bad code quality of course. permalink fedilink source parent [–] eldavi@lemmy.ml 1 point 6 months ago My newest one is as impulsive as I am so the digressions he tasks me with have stalled out long term development plans, yet he's oblivious enough of the situation to seriously ask why progress is taking so long every year during reviews. permalink fedilink source parent
[–] Kjell@lemmy.world 5 points 6 months ago And there is never time to maintain the code, because each project only want to add more feature/s which makes the spaghetti code even worse. In my group we had a golden opportunity to fix all old mistakes but no, we (decided by PO and group manager) needed to spend all time on proof of concepts that will go to production at earliest in 5 years. Now that opportunity is gone and we are crunching in order to meet the deadlines instead. Still with bad code quality of course. permalink fedilink source parent
[–] eldavi@lemmy.ml 1 point 6 months ago My newest one is as impulsive as I am so the digressions he tasks me with have stalled out long term development plans, yet he's oblivious enough of the situation to seriously ask why progress is taking so long every year during reviews. permalink fedilink source parent
