257m to Programming@programming.dev · 1 year agoWhat are your programming hot takes?message-squaremessage-square861fedilinkarrow-up1349arrow-down113
arrow-up1336arrow-down1message-squareWhat are your programming hot takes?257m to Programming@programming.dev · 1 year agomessage-square861fedilink
minus-squareT (they/she)@beehaw.orglinkfedilinkarrow-up2·1 year agoUntil you’re oboarded on a codebase that’s heavy on tech debt and that also doesn’t have proper documentation of the data being used.
minus-squareDigital MarklinkfedilinkEnglisharrow-up1·1 year agoTerrible projects are terrible because of the developers, not because of the language. I find dynamic projects easier to refactor and fix, just write some tests and if it’s green bar before and after, you’re fine.
minus-squareT (they/she)@beehaw.orglinkfedilinkarrow-up1·1 year ago…did you ever work with business/product people?
minus-squareDigital MarklinkfedilinkEnglisharrow-up1·1 year agoAll my career. They can’t program, they have no valid opinion about programming, as long as we finish the user stories. Which is several times faster in a nice dynamic language than a bondage language.
Until you’re oboarded on a codebase that’s heavy on tech debt and that also doesn’t have proper documentation of the data being used.
Terrible projects are terrible because of the developers, not because of the language.
I find dynamic projects easier to refactor and fix, just write some tests and if it’s green bar before and after, you’re fine.
…did you ever work with business/product people?
All my career. They can’t program, they have no valid opinion about programming, as long as we finish the user stories. Which is several times faster in a nice dynamic language than a bondage language.