1,085 karma · joined December 3, 2014
The best photo I can find of it to see the scale:
https://twitter.com/shadow/status/1487051654121807875/photo/...
It is the bridge on the bottom.
"The measurement of V̇O2 max in the laboratory provides a quantitative value of endurance fitness for comparison of individual training effects and between people in endurance training. Maximal oxygen consumption reflects cardiorespiratory fitness and endurance capacity in exercise performance. Elite athletes, such as competitive distance runners, racing cyclists or Olympic cross-country skiers, can achieve V̇O2 max values exceeding 90 mL/(kg·min), while some endurance animals, such as Alaskan huskies, have V̇O2 max values exceeding 200 mL/(kg·min)."
So maybe it is a measurement of "endurance capacity"...
[edited for clarity]
I built a small site for myself to help in learning the 5000 most frequently used French words. It is, and always will be, free and with no account sign up needed.
Check it out, you might find it to be useful:
For non coding related stuff: acoustic guitar and French.
I like the trade that you made of not having persistent accounts. I wrestled with that idea for a portion of my site that features "pre canned" decks. Without looking at the implementation I suspect it could then be a completely client-side solution served as static files.
Nice work.
My actual experience has been exactly the opposite: I've interacted with many members of the community (at multiple Elm conferences, in the Slack, and even twice met members of the community for in-person meetings when they were visiting near my office). All of these interactions have been the entirely opposite of "unfriendly".
Yeah. I'm never going back to an office.
But it is worth mentioning that in any non-trivial project there isn't a single "Choose Boring" or "Choose Exciting" technology decision that is made. Rather there is an entire collection of these types of decisions. And since "Choose Exciting" typically means that the tech is unfamiliar and/or novel, project risk dramatically increases the more "Choose Exciting" choices that are made.
As a tech person, and as a manager of engineers who I want to keep engaged and motivated, I have an affinity towards the "exciting" choices. But as the person responsible for on-schedule, on-budget delivery, I get pulled back towards "boring". It is a careful balancing act.
I understand insurance to largely already work like this: high premiums discourage risky behavior. For example, one might be dissuaded from building a home on a flood plain when one finds out what the flood insurance will cost.
For the last year I have been writing Elixir/Phoenix full-time at work on a greenfield project. We have gone "all in" on LiveView and our using it in a significant portion of our system. I have been very impressed with it so far. When pairing LiveView with Phoenix PubSub, one can achieve Meteor-like 'reactivity' with remarkable ease.