Probably to highlight us investment and get authorization for buying Chinese memory
102 karma · joined April 11, 2022
Cardio goals, current FTP, days to train, injuries to avoid
3 lift day programs with tracking 8w progressive Loop my PT into warm ups
Alternate suggestions.
Use whole sheet to get an overview of how the last 8w went and then change things up
Let’s say you need 50m^2 solar panels to run it, then just a ton of surface area to dissipate. I’d love to be proven wrong but space data centers just seem like large 2d impact targets.
You still can
I more often get burnt in zsh to bash than that however
Having bought a Subaru, I really tried to see where the consent is in the process. In my case, I think it’s the account establishment process that the dealer did.
Protected branches and associated secrets. Much cleaner construct on gitlab.
GitHub actions defacto seems to be tracing yaml to compiled JavaScript to hopefully that right source to shell commands.
Gitlab seems to be yaml to shell commands.
Nested projects. Nice midspot between monorepo and access control management.
API. I may be out of date on it but I recall the gitlab apis as pretty sensible. The github apis for administration has a very odd rest/graphql split.
My other TV about the same vintage is starting to have stuck pixels in the corner.
Modern failure modes aren’t nearly as graceful.
The FTP calculation is also annoying because it can’t differentiate types of rides.
Views are so much faster to pick settings in Excel. You can format tables and indent them (nested ledger) You can get higher information density.
It’s always amazing to me to wade through “how to x” in Google and see 100s of people asking for years.
Google docs and numbered headings is one of those.
Hiring a n TA to delegate grading that’s hard to verify seems like will cost more than you think.
Oh look, another signature issue…
https://github.com/advisories/GHSA-2xp3-57p7-qf4v
When googling for a SAML dependency, if a library doesn’t already have CVEs for this stuff, it’s likely never been tested.
Doing what feels fun is always going to create a path where what you want to do will be different than the annoying thing you need to do.
1. Everyone tests authenticated user can do the right thing.
2. Can <wrong|expired> authenticated user access the data?
3. Can an unauthenticated user access data?
If there’s a testing framework that does this scaffolding automatically, I’d love to hear it.
I always am happy when I get an elegant query working. Often however I just find I wasted time looking for a clean 1 query solution when iteration by caller was the only solution.
This is a bypass game on something like proof point url protection that rewrites URLs to go through a central redirect so that reputation check can be separated from reputation delivery, usage detected, and one liner URLs still work. I’m over a decade out of this space so take with a grain of salt.
The tool could do a better job inspecting “oh that’s a pgp formatted massage”. You could probably just route them all to spam and almost no one would notice.
Didn’t make the “what was going on then in physics “ connection until now.
One of the younger seniors says “I remember when my Dad used a palm pilot!” The room had the same experience.