4 ms·
> the two probably intersect more often than you think they do One of the reasons I like more terse, concise languages is because it allows me to get the idea
by kbenson 12y ago
> the two probably intersect more often than you think they do
One of the reasons I like more terse, concise languages is because it allows me to get the idea represented quicker, so I spend more time thinking about the problem and solution and less time transcribing the solution.
There is,of course, a downside in legibility, but I believe that's mostly mitigated for people familiar enough with the language.
- jimmaswell 12y agoYou can have the best of both world with an IDE with good autocomplete where you only have to type a few characters and hit tab most of the time, resulting in less time typing and improved legibility.
- marcosdumay 12y ago> resulting in less time typing and improved legibility ...and more time correcting the text that the IDE autocompleted wrongly.
- jimmaswell 12y agoWhat experience are you basing that on? That has never happened to me. It shows you what it's going to put in before it puts it in and gives you a drop-down menu.
- marcosdumay 12y agoWell, that's correcting the choice, only before its applied, what has little impact on how much attention the IDE grabs from you. I've had both before and after application errors, on different IDEs and different codebases (some sets of names change the probability distribution). But Visual Studio seems to be the worst ofender, stealing not only the up and down arrows for navigation, but also open parentesis, space, enter, period, and colon, for application... and I'm sure I forgot some keys.
- mvid 12y agoWhen is typing speed ever really the bottleneck? Code gets read 100x more often than it gets written, and any editor or IDE worth it's salt can auto-complete faster than you can think anyway. #teamReadability
- JackMorgan 12y agoSo why use a wordy language that makes you read twice as many characters to get the same concepts? It would take a few weeks to learn to read the smaller language, but the rest of your career to gain the benefits. Why write down to the skill of the least skilled member?
- mvid 12y agoIf you are looking only to optimize your career and expertise, do whatever you want. If you care about having a codebase that is accessible to all levels of talent, then you should optimize for readable code. The least skilled team member is still a team member. The fresh grad, the intern, the customer support rep with an interest in code, the new hire. Why are you so willing to discount any of these members as not valuable? Just because they don't have an innate skill and interest in code golf? Reading symbols is a near instantaneous exercise. You can tell the difference between "i" and "index" with no extra work. Stopping to think to decipher the meaning of cryptic code is slow. It doesn't hurt to use a full word instead of a single letter variable name, or an explicit function call instead of an alias to some cryptic character. We don't use languages anymore that benefit from have a small file size. Reading will always be more important than writing, until you get down to hardware drivers and kernels.
- marcosdumay 12y ago> If you care about having a codebase that is accessible to all levels of talent, then you should optimize for readable code. "All levels of talent" is such a can of worms. No, not even in a team environment you should have all code accessible to all levels of talent. That's just a recipe failure. Anyway, that isn't really relevant to the argument of how many characters you should use in a variable name.