▲ 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 24 points 6 months ago (6 children) [deleted] permalink fedilink source hideshow 6 child comments replies: [–] vrek@programming.dev 34 points 6 months ago (5 children) The worst programmer I ever met was myself 6 months ago... permalink fedilink source parent hideshow 5 child comments replies: [+] MangoCats@feddit.it 5 points 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago True all that plays a part. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 3 points 6 months ago Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies) load more comments (-2 replies) load more comments (-2 replies) [+] 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 load more comments (-2 replies)
[–] vrek@programming.dev 34 points 6 months ago (5 children) The worst programmer I ever met was myself 6 months ago... permalink fedilink source parent hideshow 5 child comments replies: [+] MangoCats@feddit.it 5 points 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago True all that plays a part. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 3 points 6 months ago Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies) load more comments (-2 replies) load more comments (-2 replies) [+] 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 load more comments (-2 replies)
[+] MangoCats@feddit.it 5 points 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago True all that plays a part. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 3 points 6 months ago Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies) load more comments (-2 replies) load more comments (-2 replies)
[–] vrek@programming.dev 1 point 6 months ago True all that plays a part. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 3 points 6 months ago Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies) load more comments (-2 replies) load more comments (-2 replies)
[+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 3 points 6 months ago Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies) load more comments (-2 replies)
[–] vrek@programming.dev 3 points 6 months ago Yeah, I used to be in the medical device industry. Once shipped, an update typically meant a patient needed additional surgery because of your mistake. That really emphasized the "unless absolutely necessary" part of your statement. permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies) load more comments (-2 replies)
[+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies)
[–] vrek@programming.dev 1 point 6 months ago Oh yeah... I once had a project to change a 0 to a 1 in a file on a machine used to manufacture devices. Basically operator had to align crosshairs over a certain point before starting. At 4 of the systems the operator could just touch the screen at the point and go. At one they had to push x+ or x- or y+ or y- repeatedly to line it up because the configuration had a 0 in the option "Click To Align"... It took 8 months to validate changing that to be 1 permalink fedilink source parent replies: [+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent load more comments (-2 replies)
[+] MangoCats@feddit.it 1 point 6 months ago (1 child) [removed by mod] permalink fedilink source parent hideshow 1 child comment replies: [–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent
[–] vrek@programming.dev 1 point 6 months ago I didn't know the number but I'm not surprised. permalink fedilink source parent
[+] 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
