kucing@lemmy.my.id to Programmer Humor@programming.dev · 1 year agoIt's a-melemmy.my.idimagemessage-square30fedilinkarrow-up1703arrow-down113
arrow-up1690arrow-down1imageIt's a-melemmy.my.idkucing@lemmy.my.id to Programmer Humor@programming.dev · 1 year agomessage-square30fedilink
minus-squarekucing@lemmy.my.idOPlinkfedilinkarrow-up7arrow-down5·1 year agoHaving to work with legacy overengineered java services for the past year, yep i keep wondering why it’s not six feet under already.
minus-squareJackbyDev@programming.devlinkfedilinkarrow-up11·1 year agoI assure you working with any legacy over engineered system is a pain.
minus-squareAlexWIWA@lemmy.mllinkfedilinkarrow-up2·1 year agoYup I’m seeing similar issues in python. Twelve layers of subclasses
minus-squarekucing@lemmy.my.idOPlinkfedilinkarrow-up2arrow-down4·edit-21 year agoIkr but some genius made 5 layers of abstraction for a home brew object mapper (no, no tests at all). Also time consuming gradle runs (+buttload of RAM) really adding salt to the wound lmao.
minus-squareJackbyDev@programming.devlinkfedilinkarrow-up1·1 year ago genius Everybody thought they were, didn’t they? That’s always how it goes it seems.
Having to work with legacy overengineered java services for the past year, yep i keep wondering why it’s not six feet under already.
I assure you working with any legacy over engineered system is a pain.
Yup I’m seeing similar issues in python. Twelve layers of subclasses
Ikr but some genius made 5 layers of abstraction for a home brew object mapper (no, no tests at all). Also time consuming gradle runs (+buttload of RAM) really adding salt to the wound lmao.
Everybody thought they were, didn’t they? That’s always how it goes it seems.