misev
Joined 12 years ago
Joined 12 years ago
int* ptr = ((v != 0) * lwr) + ((v == 0) * rwr);
I doubt it would be faster than the ternary though. <category code> <time> <optional description>
e.g. S 2000
W 0800
F 0900 banana
P 1010
...
(S = sleep, W = wake up, F = food, P = poop, etc.)
Every few months I copy paste the messages from Telegram into a text file and have a script to parse, clean it up and add the dates. Would be fun to try some data science on the past few years of this data.. at some point :)What an amazing improvement to 4:30 pace at 140 bpm btw! I've had a similar relative improvement over the first year when I think about it, from around 7:00 to 5:20-5:30 at 140 bpm. But my training was mostly 1km intervals at high end of zone 3 (still quite below threshold), translating to a lot of tempo running on average, plus one session of 200s or 400s faster intervals per week. Been stuck with little progress for a while though, and was thinking to try a more polarized approach like yours with higher volume; thanks for explaining it!
Unrelated, out of curiosity, when you say 80% of your training: is it in mileage/time? Or some effort metric like TRIMP, calories, avg. HR, or so? Or something else?
This query language that looks like SQL is an official part of SQL now [1]. Surely there is place for integrated DB solutions that let you work with both relational and array data in one place? There are more benefits in this than just performance/scalability. Think of building services on top of big array datasets, beyond one-off data science experiments.