Here's one that shows a longer-term effect:
http://jap.physiology.org/cgi/content/abstract/85/2/695
Essentially, incorporating resistance training in your exercise regime raises your basal metabolic rate.
This is quite well studied, and makes sense.
704 karma · joined February 26, 2008
Here's one that shows a longer-term effect:
http://jap.physiology.org/cgi/content/abstract/85/2/695
Essentially, incorporating resistance training in your exercise regime raises your basal metabolic rate.
This is quite well studied, and makes sense.
E.g., if you store dated snapshots of content, it's much easier on you if you can just store the whole directory, rather than manually maintaining hard links back to previous versions.
Link?
I doubt most such research is considering code, so I'd like to see your sources. I totally agree that English text is easier to read when correctly typeset, but reading code and reading English are very different activities, at least for me. English is mainly read through occasionally overlapping sweeps, with a linear tendency. I read code by jumping around within constraints established by my understanding of structure.
From experience, I know where to look for arguments, for loop bindings, for destructuring; I know how to read a with-* macro, a declaration, a comment block. If those conventions are violated, my code reading slows and errors can creep in.
> What you're saying only applies if your "patterns" consist of forcing > everything into the same length.
No, what I'm saying applies whenever structure can be made visible by aligning tokens to a grid. If that grid is 1em wide, the alignment is easy.
Consider a totally trivial non-indentation example: returning the English-language representation of a mathematical operator using case.
(defun to-english (c)
(case c
(< "less than")
(> "greater than")
(+ plus")
(- "minus")))
Because the operators are all the same width, I can immediately see the syntax error: a break in the column of double-quotes. If those strings were not all aligned to the same grid, the error would not be obvious, and I'd have to rely on syntax highlighting. Syntax highlighting helps in this case, but not always.The effect is even more profound when considering common test code: it's usual to walk a table of data and answers, applying the same test to each, and thanks to monospacing you can ensure that multiple values are grouped in both axes.
You can achieve this for whole-token alignment with careful tab settings, but I'm sure as hell not going to edit code in Microsoft Word. You cannot achieve it within tokens without using monospaced fonts.
Have you ever worked at a low enough level, or with a programming language that uses short tokens, such that you're interacting with a collection of functions like
/_2op
*_2op
+_2op
-_2op
=_2op
>_2op
<_2op
? Having those be the same width helps my brain "unpack" the meaningful content from the "annotation" (the fact that they're all two-operand functions).> I suspect that you might not know what you're talking about, but only because > of your choice of language ("shape of a form", "code is structure and > patterns" - what exactly is that supposed to mean, if anything?)
What part of "make it easier for me" rubbed you the wrong way? I was conveying personal opinion.
Most of my code is written in various Lisps, in which the structure of code is directly manipulated. I'm not sure how to explain the importance of pattern and structure if you don't get it… perhaps some examples of patterns might help you:
public static void main(String[] args)
public void foo()
public void bar()
The structural layout, indentation, and use of established patterns in code fulfills the same role that, say, 12-bar blues does: everyone knows how to work within the framework, so nobody wastes their time trying to figure out how to communicate before they can make something happen. My opinion is that variable-width fonts inhibits my ability to spot the patterns and structure in the code, so I'm forced to read it more carefully to extract the same information.Monospaced fonts make it easier for me to spot that structure and observe those patterns, whether to simplify my scanning of the code, help me spot bugs (e.g., omitted punctuation throws off the shape of a form), or navigate within a file.
I do essentially all of my writing — email, web forms, text editing, console — with monospaced fonts.
I find Pragmata so narrow it hurts to read. :(
To take his point to a higher level: it would be much more destructive (in several senses) to have to rip out HFS+ for legal reasons than it would be to rip out Xcode.
Lots more people depend on a filesystem.
AllegroCache can store persistent maps and sets, so you could use it as a KV store, but that's hardly taking advantage of its power.
Plot the compensation over time, and I'm much better off now, especially considering the other things I've been able to accomplish while not being on a 90-hour week startup deathmarch.
From what I've read, Groovy is monstrously slow. That alone should rule it out.
It's hard to do, though!
It would be foolish to treat it as the only solution.
(I did much the same thing, but that's because I totally ruined my right wrist by working through searing pain. I needed at least three years for my right wrist to recover to the point that I could use it to mouse at all.)
(Disclosure: that's got an affiliate link in it.)
Lots of people get misdiagnosed, have surgery, and end up right back where they started.
The authors explain that most people with persistent strain disorders are suffering from a combination of nerve adhesions, inflammation, and microscopic muscle spasms (tender points or knots) that cause pain, weakness, numbness, and so on. Actual carpal tunnel syndrome is much rarer than commonly thought.
Their primary thesis is that treating a symptom does not help. Cutting your carpal tunnel will only shift the problem elsewhere. Adjusting your position will, at best, move the problem elsewhere. You need to treat the (several) root causes, working your way along the chain until you're nearly pain free.
For example: pregnant women often get the symptoms of carpal tunnel syndrome. Advocating surgery for pregnant women is obviously insane, but it's commonly suggested for us programmers when the ol' "try wearing a wrist brace at night" trick doesn't work. Perhaps hammering away at a keyboard for thousands of hours might have something to do with it, rather than an actual problem with the carpal tunnel?
The authors have a ton of material on the web, so you can read before buying the book:
My personal approach: I use an ergonomic keyboard, of course. I eat better than I used to. I take breaks. I massage my forearms. I lift weights and exercise. I don't take ibuprofen. I don't stretch too much (my arm joints are hypermobile).
Seriously, go read the book.
You don't run a service on one machine; you use redundancy to reduce the chance of catastrophic failure.
To make this work with MacVim on a Mac:
:set editor="/Applications/MacVim.app/Contents/MacOS/Vim -g -f"http://www.itl.nist.gov/div897/sqg/dads/HTML/persistentDataS...
His whole point is that short-term productivity is sometimes more important. No point building a product that'll be easy for you to extend in the future if you don't build it quick enough to have a future.
Version control is not so easy to search, particularly if you're looking for a utility that you think is live in the project.