3 ms·

Yeah, but this will bite you as well when other people do it and you have to fix it. Or I guess you’ll always go look for low hanging fruit and run away from a

Yeah, but this will bite you as well when other people do it and you have to fix it. Or I guess you’ll always go look for low hanging fruit and run away from any responsibility/accountability forever. But even that bites back at some point or another when you run out of luck

throwawaysleep 4y ago
Whether or not I do it, I get bit by others doing it. Whether or not the guy before me leaves a pile of crap behind is not determined by me.
- latexr 4y ago
  > Whether or not I do it, I get bit by others doing it. You could choose to stop the cycle instead of biting the next person down the line just because you were bitten by someone unrelated. > Whether or not the guy before me leaves a pile of crap behind is not determined by me. Maybe not directly, but it does play a part. When no one cares about doing things right, even the ones who did care get fatigued and stop. The way to fix the situation is to be better yourself, thus giving others the chance to be at their best.
  - grugagag 4y ago
    Ive done it a few times. Simplified everything and moved on to other projects only to see the the project be evolved by other into an unorganized pile of crap. I also got laughed at for not using sime pattern or framework du jour
Jcampuzano2 4y ago
I mean this is sort of how things already work, so much so that the trope of "the old devs didn't know shit" and memes about needing to replace everything or crapping on legacy code when starting a new job is talked about daily among devs. I'm not really worried about what other people do because when I have to fix it, I'll be being paid to, and so would the next guy after me. If companies don't feel responsible for treating employees well/not turning their backs on them in the sake of profit then I feel 0 responsibility for anything I leave behind when I'm gone.
- grugagag 4y ago
  That’s fair but seems to me like a chicken and egg problem. Nowadays unless you go build something from scratch it’s all a pile of garbage because no one really cared. The few who did got pushed out or gave up so we as a collective shat where we ate.
- latexr 4y ago
  > If companies don't feel responsible for treating employees well/not turning their backs on them in the sake of profit then I feel 0 responsibility for anything I leave behind when I'm gone. Sounds like the solution is to look for a good company—they do exist—not sabotage the current one.

throwawaysleep 4y ago

Whether or not I do it, I get bit by others doing it. Whether or not the guy before me leaves a pile of crap behind is not determined by me.

latexr 4y ago
> Whether or not I do it, I get bit by others doing it. You could choose to stop the cycle instead of biting the next person down the line just because you were bitten by someone unrelated. > Whether or not the guy before me leaves a pile of crap behind is not determined by me. Maybe not directly, but it does play a part. When no one cares about doing things right, even the ones who did care get fatigued and stop. The way to fix the situation is to be better yourself, thus giving others the chance to be at their best.
- grugagag 4y ago
  Ive done it a few times. Simplified everything and moved on to other projects only to see the the project be evolved by other into an unorganized pile of crap. I also got laughed at for not using sime pattern or framework du jour

Jcampuzano2 4y ago

I mean this is sort of how things already work, so much so that the trope of "the old devs didn't know shit" and memes about needing to replace everything or crapping on legacy code when starting a new job is talked about daily among devs. I'm not really worried about what other people do because when I have to fix it, I'll be being paid to, and so would the next guy after me. If companies don't feel responsible for treating employees well/not turning their backs on them in the sake of profit then I feel 0 responsibility for anything I leave behind when I'm gone.

grugagag 4y ago
That’s fair but seems to me like a chicken and egg problem. Nowadays unless you go build something from scratch it’s all a pile of garbage because no one really cared. The few who did got pushed out or gave up so we as a collective shat where we ate.
latexr 4y ago
> If companies don't feel responsible for treating employees well/not turning their backs on them in the sake of profit then I feel 0 responsibility for anything I leave behind when I'm gone. Sounds like the solution is to look for a good company—they do exist—not sabotage the current one.