The circles next to their names represent gold, silver, and bronze.
The anaerobic battery starts at 15000J and can run down to zero, but is also goes up when, "power change" is negative? means they're making less aerobic effort so 'recovering'?
The first column of numbers is the input scaled to a real number between 0.0 and 1.0
Not sure what the color of the flags mean, if anything.
Not sure what the middle column of 4 numbers are or how/why they change.
Still not sure what "power change" actually is.
I find the need for a "search engine" reduced very considerably with all these "answer this question (NOW!)" options so readily available. They're the modern day "I feel lucky" button.
Mid-70's! Well done.
What degradation in ability should I plan for? Any?
I envisage myself coding for another 45 years (I'm in my 50s now), but I worry about my ability to concentrate on a single task for long spells, think creatively yet realistically enough to find solutions; to learn the latest fads and tools, and maintain my enthusiasm to keep up with the latest fads and tools. Will my hands get too unsteady to type, my eyes too weak to focus; how long will I be able to sit (or stand) up and work in a session. No-one knows I'm a dog, but they will if I have to turn on the camera or go to the office, so, will I necessarily be transitioned to more results-driven work assignments via tasking sites?
(I guess these are the typical prejudices that a hiring team will make when considering an older candidate.)
Prepare me. Share your wisdom. What challenges has aging presented to your ability to code?
Show them fava https://beancount.github.io/fava/. Offer the url; they can comb through it all at their own leisure. "Here let me show you."
Mine likes the pretty graphs. As I enthusiastically explain them, the eyes start flickering elsewhere, attention rapidly dwindles, and trust is effectively reassured for another month, or six.
I think you've lost the point of Markdown: it's readable as raw text.
I was excited that this was an extension of markdown but now I that see it I react with horror: markdown is not a programming language. This looks rather like a programming language.
A time limit identifies knowledge, rather than 'smarts':
An individual who has "mastered the material" can answer quickly irrespective of their smarts: they learnt both the fundamental concepts and the derivatives in preparation for the test, and can commence answering the question immediately from the derivatives.
An individual who has not "mastered the material", but is smart, can start with the fundamentals, work out the derivatives, then commence answering the question: but only given enough time.
So tests which include a time element are, or should be, knowledge tests, and not an intelligence, or 'ability to answer the question', test.
How do you do the arrow keys and navigate the page?
When coding I seem to expend most of my keystrokes just moving around the page. I take it you just setup some short chords for each arrow key, pgup/pgdn, ctrl, alt... etc.
It is hard enough getting around a desktop with just keyboard shortcuts as it is!? I expect I would waste an inordinate amount of time fiddling with my dictionary trying to optimize keystrokes for the OS and apps that I spend the most time in.
