canpolat@programming.dev to Programming@programming.devEnglish · 1 year agoTyping is not a programming bottleneckblog.ploeh.dkexternal-linkmessage-square27fedilinkarrow-up183arrow-down115
arrow-up168arrow-down1external-linkTyping is not a programming bottleneckblog.ploeh.dkcanpolat@programming.dev to Programming@programming.devEnglish · 1 year agomessage-square27fedilink
minus-squareonlinepersona@programming.devlinkfedilinkEnglisharrow-up7arrow-down2·1 year agoI agree, typing is not a bottleneck, repeating yourself is. All that boilerplate code in the example, shouldn’t have to be written. It’s wasted time.
minus-squarephilm@programming.devlinkfedilinkarrow-up3arrow-down2·1 year agoThe curse of OOP (java style…). I mean why do you need to write getter and setter methods. I have wondered at the beginning of university 10 years ago, and am still wondering why you would need something like that…
minus-squaremanapropos@lemmy.basedcount.comlinkfedilinkarrow-up1·1 year agoI write Java for a living and the places I’ve worked have used Lombok to cut down on the boilerplate code
minus-squarephilm@programming.devlinkfedilinkarrow-up1·1 year agoMy condolences, haha (I’m honestly not a big Java lover ^^).
minus-squaremanapropos@lemmy.basedcount.comlinkfedilinkarrow-up1·1 year agoIt’s not so bad. I’m just a lowly webdev and my work with Java is mostly just basic CRUD operations
I agree, typing is not a bottleneck, repeating yourself is. All that boilerplate code in the example, shouldn’t have to be written. It’s wasted time.
The curse of OOP (java style…).
I mean why do you need to write getter and setter methods. I have wondered at the beginning of university 10 years ago, and am still wondering why you would need something like that…
I write Java for a living and the places I’ve worked have used Lombok to cut down on the boilerplate code
My condolences, haha (I’m honestly not a big Java lover ^^).
It’s not so bad. I’m just a lowly webdev and my work with Java is mostly just basic CRUD operations