3 ms·

The more apt analogies would be: * "chng af" * "tglCB" I will continue my crusade to fight against this and spell things out until my death.

by bmitc 4y ago

gregjor 4y ago
Learning some jargon and specialized skills most people don’t need or care about doesn’t make a person smarter or better, nor does it mean everyone else is ignorant or too dumb. Showing off and complaining about the dumb masses is vanity, not professionalism.
- bmitc 4y ago
  I was just using your examples to comment on the common programmer practice of needlessly shortening words and names of things or, even worse, intentionally quirkily naming something to make a specialized word or domain even more specialized. It's a practice that I do not like, as it arbitrarily creates an additional layer of obfuscation.
  - gregjor 4y ago
    At one time memory constraints made the short names necessary. Not a technical issue anymore. Now we have autocomplete in the shell. But what do you expect from a professional caste who debate endlessly about efficiency and “productivity” supposedly improved a fraction by a keyboard or typeface or color scheme?
    - Espressosaurus 4y ago
      Let me post another article about how I can save 10 seconds by using Emacs for my toaster!
IshKebab 4y ago
Hear hear. I don't think programmers - as a group - get to complain about people not learning programming tools while simultaneously making them so unapproachable (especially Linux things). It's not just the overuse of acronyms. There's also: * Religious devotion to the CLI despite it having terrible discoverability. * Really bad naming. Git is probably the worst offender at this, but the whole of Unix is a naming mess. WTF is `usr`? Is that where user files go? * Generally over-complicated tooling. A good example of this is Node/NPM. So complicated to set up! Contrast it with https://trunkrs.dev/ https://trunkrs.dev/ * Deification of distro packages. No I do not want to spend half of my development time packaging my app for 10 different distros. I guess I'll go with curl | bash then. * Distain for binary app distribution. I'm looking at you glibc.
- bmitc 4y ago
  Thanks for being one of the rarities top understand. Gives me a glimmer of hope. I agree with everything you said.

The more apt analogies would be: * "chng af" * "tglCB" I will continue my crusade to fight against this and spell things out until my death.

by bmitc 4y ago

The more apt analogies would be: * "chng af" * "tglCB" I will continue my crusade to fight against this and spell things out until my death.

gregjor 4y ago

Learning some jargon and specialized skills most people don’t need or care about doesn’t make a person smarter or better, nor does it mean everyone else is ignorant or too dumb. Showing off and complaining about the dumb masses is vanity, not professionalism.

bmitc 4y ago
I was just using your examples to comment on the common programmer practice of needlessly shortening words and names of things or, even worse, intentionally quirkily naming something to make a specialized word or domain even more specialized. It's a practice that I do not like, as it arbitrarily creates an additional layer of obfuscation.
- gregjor 4y ago
  At one time memory constraints made the short names necessary. Not a technical issue anymore. Now we have autocomplete in the shell. But what do you expect from a professional caste who debate endlessly about efficiency and “productivity” supposedly improved a fraction by a keyboard or typeface or color scheme?
  - Espressosaurus 4y ago
    Let me post another article about how I can save 10 seconds by using Emacs for my toaster!

IshKebab 4y ago

Hear hear. I don't think programmers - as a group - get to complain about people not learning programming tools while simultaneously making them so unapproachable (especially Linux things). It's not just the overuse of acronyms. There's also: * Religious devotion to the CLI despite it having terrible discoverability. * Really bad naming. Git is probably the worst offender at this, but the whole of Unix is a naming mess. WTF is `usr`? Is that where user files go? * Generally over-complicated tooling. A good example of this is Node/NPM. So complicated to set up! Contrast it with https://trunkrs.dev/ https://trunkrs.dev/ * Deification of distro packages. No I do not want to spend half of my development time packaging my app for 10 different distros. I guess I'll go with curl | bash then. * Distain for binary app distribution. I'm looking at you glibc.

bmitc 4y ago
Thanks for being one of the rarities top understand. Gives me a glimmer of hope. I agree with everything you said.