minus-squaremarkstos@lemmy.worldtoProgrammer Humor@lemmy.ml•do as i say...linkfedilinkEnglisharrow-up49·1 year agoI’ve been at this for 25 years and a restriction on variable name length hasn’t been a problem since then. A good senior dev shouldn’t just be older, they should have continued to learn and evolve. I do remember texting abbreviations because we texted on a number pad with no autocomplete. Everyone I know was happy to switch to better keyboards and autocomplete as soon as they were available. linkfedilink
minus-squaremarkstos@lemmy.worldtoProgrammer Humor@lemmy.ml•do as i say...linkfedilinkEnglisharrow-up17arrow-down2·1 year agoUgh. linkfedilink
minus-squaremarkstos@lemmy.worldtoProgrammer Humor@lemmy.ml•do as i say...linkfedilinkEnglisharrow-up34·1 year agoSolution: Code Style Guidelines doc that the team agrees on. A checkbox in the PR template that affirms that code is compliant with the guidelines. This way it’s not personal, it’s a rule that everyone should follow as a shared standard. linkfedilink
I’ve been at this for 25 years and a restriction on variable name length hasn’t been a problem since then.
A good senior dev shouldn’t just be older, they should have continued to learn and evolve.
I do remember texting abbreviations because we texted on a number pad with no autocomplete.
Everyone I know was happy to switch to better keyboards and autocomplete as soon as they were available.