5 ms·

For reference, this was a course project done in my class at Stanford (CS 242: Programming Languages) last fall, not a peer-reviewed publication. Overall a grea

For reference, this was a course project done in my class at Stanford (CS 242: Programming Languages) last fall, not a peer-reviewed publication. Overall a great project. The title is a bit general, but the goal was to identify what resources people found most useful when learning Rust and why. My favorite bit: > Participant behavior indicates that they found the in-line Rust Enhanced compiler errors that showed upon saving to be quite useful. Participants were not told about this feature, and only discovered it, on average, 1058 seconds (17 minutes, 38 seconds) into the task. However, after finding the Rust Enhanced compiler error feature, participants began saving every 30.6 seconds, on average, with an average of 24.8 total saves per person.

cuddlecake 8y ago
And here I am, Saving after every change, regardless of the language.
- bhaak 8y ago
  If you save after every change why don't you use an auto save feature?
  - cuddlecake 8y ago
    Touché. Will check if VSCode has such a feature.
  - dmacedo 8y ago
    I do the same as parent comment. I had previously automated it; from simple timers, to every X seconds of inactivity; and in my experience with it, the automation took away time when some editor/compiler stops your flow (errors out/fatally because you haven't completed your current typing), or more importantly, that setup started either colliding with the key press save muscle memory (leading to some frustration when the editor just paused slightly for analysis twice) or slowly removing that muscle memory when working with other editors/setup that didn't have the feature enabled. I've since turned back (ages ago) and prefer this mental trigger to save and check for compilation/analysis at a pause in the flow. I really feel that works best, I'm sure the automatic save will work for others...
jackconnor 8y ago
I do Angular and I 100% agree, as I keep all compiler error outputs on for every save, and you find/squash a trillion bugs before they can turn into anything bad.

cuddlecake 8y ago

And here I am, Saving after every change, regardless of the language.

bhaak 8y ago
If you save after every change why don't you use an auto save feature?
- cuddlecake 8y ago
  Touché. Will check if VSCode has such a feature.
- dmacedo 8y ago
  I do the same as parent comment. I had previously automated it; from simple timers, to every X seconds of inactivity; and in my experience with it, the automation took away time when some editor/compiler stops your flow (errors out/fatally because you haven't completed your current typing), or more importantly, that setup started either colliding with the key press save muscle memory (leading to some frustration when the editor just paused slightly for analysis twice) or slowly removing that muscle memory when working with other editors/setup that didn't have the feature enabled. I've since turned back (ages ago) and prefer this mental trigger to save and check for compilation/analysis at a pause in the flow. I really feel that works best, I'm sure the automatic save will work for others...

jackconnor 8y ago

I do Angular and I 100% agree, as I keep all compiler error outputs on for every save, and you find/squash a trillion bugs before they can turn into anything bad.