257m ( @257m@lemmy.ml ) to Programming@programming.dev · 2 years agoWhat are your programming hot takes?message-squaremessage-square374linkfedilinkarrow-up1222
arrow-up1222message-squareWhat are your programming hot takes? 257m ( @257m@lemmy.ml ) to Programming@programming.dev · 2 years agomessage-square374linkfedilink
minus-square T (they/she) ( @Templa@beehaw.org ) linkfedilinkarrow-up2·2 years 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-square Digital Mark ( @mdhughes@lemmy.ml ) linkfedilinkEnglisharrow-up1·2 years 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-square T (they/she) ( @Templa@beehaw.org ) linkfedilinkarrow-up1·2 years ago…did you ever work with business/product people?
minus-square Digital Mark ( @mdhughes@lemmy.ml ) linkfedilinkEnglisharrow-up1·2 years 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.