Getting rate limited by GitHub, gonna add caching here as well. Temporary workaround is to sign in manually and return to example page: https://0github.com/handler/sign-in
we are ex-Stripe engineers building Lumen Payments. Takes care of webhooks and a lot of boilerplate code so you can implement billing + entitlements really easily.
Wouldn’t you? If I switch context and interrupt my flow to answer a question I’m losing at least 20 mins to regaining focus, why shouldn’t that be reflected in billing?
Knowledge work is knowledge work, no point belittling colleagues in a different profession.
Thats how MSPs operate too. At least the good ones. Billing increments are sometimes as low as 6 minutes, or as high as 30. 15 minutes is average in my experience.
> how do they check whether the contestant is conscious?
already answered but they'll apply pressure on your hand (or similar) and you need to apply pressure back
> How does the contestant know what his limits are before passing out?
When you hold breath for a long time your body will have muscle contractions. The time that needs to pass for each contraction to happen varies from person to person but it is quite consistent for each person. So free divers can know that they are good up to X contractions which will take after X minutes in certain conditions. The fun part is you can train to experience your first contraction by holding your breath while laying down in bed.
In a group sport like club cycling, it can be everyone's responsibility to make sure that your fellow riders haven't gone either hypoglycemic or into heat stroke. We all watch each other so we can go a bit harder and the people who can still talk keep tabs on everyone else.
I understand that with submersibles and astronauts there's a bit of this going on as well. Everyone is watching everyone else for nitrogen narcosis or hypoxia. Maybe another reason the Navy doesn't like assholes on submarines. How can I tell if you're being a jerk today or we need to check the CO2 sensors? Better to notice Lieutenant Ivers only gets short with people when his blood ox goes a little south.
If you go to solo walking or running, now you are the only one tracking your mental state. Now you have to use your own judgement to try to detect when your judgement is going away. It's... tough. Personally I think it's easier if you've already had practice on team settings. But it's still tough.
Same thing with alcohol. There's a reason bartenders don't serve drunks. No judgement anymore. You should have put the glass down half a drink ago and had some water instead. And I think you can only learn that safely by slowly sidling up to it from the safe side, and have someone to look after you if you go a little fuzzy.
E.g. This was the strategy discovered by optiLLM for solving word problems:
*Refined Strategy for Solving Word Problems:*
1. *Understand:*\n * Read the problem carefully (multiple times).\n * Identify the question (what are you trying to find?).\n * List all given information (facts, numbers, units).\n * Clarify ambiguous terms/units.
2. *Organize Information & Identify Unknowns:*\n * Choose an organization method: (e.g., table, diagram, list, drawing).\n * Clearly identify the unknowns (what you need to solve for).
3. *Plan and Translate:*\n * Define all variables with units (e.g., `p = number of pennies`, `c = number of compartments`).\n * Identify relationships between knowns and unknowns.\n * Convert units if necessary.\n * Write equations or expressions, including units, that relate the knowns and unknowns.\n * Ensure units are consistent throughout the equations.\n * Outline the solution steps.
4. *Solve:*\n * Show work step-by-step.\n * Track units throughout calculations.\n * Calculate accurately.\n * Solve for the unknowns.\
5. *Evaluate and Verify:*\n * Check if the answer is reasonable.\n * Verify the answer.
