An ability to switch back and forth to a sort of "graph" view would be tremendously helpful, as most people tend to have a better ability to process visual information rather than a stream of text
Perhaps I lacked the verbosity in my original comment, but this was what I meant to imply: ventilation is part of the design. Unintentional exchange is to be avoided.
Figure it out yourself. You should know your own value in a profit center; it gives you a lot of ability to either negotiate raises or describe your value to others if seeking employment elsewhere. Or alternatively, it gives you data to describe your successes when trying to get someone to fund your next venture.
...but the ideal structure is not supposed to exchange air with the outside particularly because of this. That is why windows and doors have seals on them. I'm no mechanical engineer, but I've worked with enough of them in my career to understand that their goal is usually keeping a structure tightly sealed when ingress/egress paths are closed (of course opening windows/doors is a choice of the occupant, which if your striving to reduce heat loss/gain... you shouldn't do)
HabitRPG is a web and mobile platform for gamifying habits and life goals that launched via Kickstarter a couple years back that is very successful in helping people do what you've done
I am a data junkie as you are, and I have several years of Foursquare data now, but just recently started using Moves. One gripe I've had is that if I stop somewhere for less than a two to three minutes, Moves doesn't register that I was actually at a location, and there's no way to force it to do so. Have you experienced something similar? Beautiful site, by the way.
There are a lot of small, one-off, often very useful utilities that people are now sharing with each other via Github (I'm guilty/a participant in this phenomenon), and many noble users of these utilities want to help, contribute, and send PRs... a non-negligible number of them new to Git.
So, is it more of a PITA to set up a feature branch for a single python script and instruct users in your CONTRIBUTING file to 'make sure they submit PRs to branch XYZ!' or just deal with the odd occasional PR to master? Folks new to Git will probably just send a PR to master anyway (I believe OP addresses the 'new user' issue as well, having to explain Git commands to users in comments on a PR)
That all being said, I still typically follow the workflow shadowmint outlines above.
Seems like they used a Powerpoint-esque framework... it's not really intuitive when you think of it like the average web page, but for giving a presentation it's quite good
I was editing the note about "farts" trying to add a list of foods that cause excessive flatulence (to test markdown support of lists, of course), but after submitting my edit, I was getting 503 errors for a short period of time.
after a few more minutes, things seem fine
edit: it seems that someone was able to remove my hard work and valuable information. Given that this is based on git, is there any way to revert or view previous versions of notes?
the point of a framework is speedy development. less lines of code for results. the tradeoff is often bloat, which one should (ideally) refactor out later. Angular can get overwhelmingly slow if you're not careful with your code, but gosh dang, you sure can whip an app up pretty fast