610
Code Quality (thelemmy.club)
submitted 5 months ago by to c/programmerhumor@lemmy.ml
30 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 5 months ago (4 children)

Progressing is cool, but having 10 yoe and still outputing spaghetti is bad. I am just saying if you care enough about what you are doing you are top 10% already

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 6 points 5 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
    •
  • [–] 6 points 5 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
    •
  • [–] 5 points 5 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
  • [–] 1 point 5 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