After 10 years of crit racing I finally got to be The Problem: the person who let the break get clear. And then finished just about DFL. So much fun being terrible at this. 🤪
youtu.be/db6g_Iw6SBA
You designed failure into your process. 🤷♂️
A chart showing a breakdown of a Zwift workout focused on alternating between 80rpm and 90rpm cadence. Interval data sits above each column showing average data for that interval, including average power, heart-rate, intensity (power as a percentage of functional threshold power), cadence, speed (irrelevant in this graph), and SPI, which evaluates the efficiency of power/cadence. Intervals with higher cadence (90rpm) typically have higher heart-rates, though this also follows the elevation contours of the course. During these intervals, it was easier to respond to variations in power without shifting gears, which is a main reason racing cyclists cite their preference for higher cadence. By contrast, lower cadence, or "dieseling", produced much flatter power and heart-rate with more shifting of gears to adjust to terrain. By 100 minutes, I could no longer reliably generate 90+ rpm for more than a minute at a time. Both cadences (80 and 90) were taxing to a system that generally settles around 85.
Did some @gozwift.bsky.social science for @alyssam-infosec.com to see how cadence really impacts the workout. 10 minutes 90 rpm, 10 minutes 80 rpm: repeat until...? I made it 100 minutes before I had to pull the plug and just ride. 90 felt fast but responsive with higher HR, 80 showed better torque.
Your cadence may be holding you back. ~60rpm was where I started, and I finished every ride super exhausted. Most folks shoot for 80 - 90 rpm average. Your heart-rate will rise slightly as you adapt, but you'll be able to tolerate longer rides in greater comfort. YMMV.
...and all of their gov't contracts need to be shredded, ill-gotten gains impounded, and maybe just a dash of corporate asset seizure for good measure.
This was my August thru early December. My lower back is a trainwreck, and it took a lot of experimentation to figure out how to manage this most recent flare-up. 4 rounds of "try this--it may not work, but let us know in 6 weeks" while silently erasing all your future plans.
I would love to know who on the MS Purview team decided that clicking on a solution should take you to information ABOUT the solution, rather than the tool itself. What problem were they trying to solve? Not a fan of picking URLs apart to actually get to DLP or sensitivity labels.
50 days later and I'm crossing 1K lines again, moving to dot-source functions, and laying the groundwork to move from WAM/WebView2 delegated auth to app-only.
The hidden prompt is bad, but was only the first part of my Very Long Day chasing this. Role assignments aren't honored if you combine the auth flow with auth-strength CA and legacy per-user MFA, but no errors are captured in Entra's logs. Agree, tho: it's a terrible UX
I'm sure I'll come to sing its praises soon, but I'm not digging the hidden auth windows with WebView2. Really hope they find a way to bring those to the foreground.
PowerShell nerds! Yell at me later, but if you're trying to figure out why elevated commands don't work even with all roles activated, it could be the new WebView2 + Graph module 2.34 + per-user MFA. This combo lets you sign in but fails authentication-strength requirements for elevation.
PowerShell lifecycle:
1. Incredible idea!
2. Scavenge old code for connection strings.
3. Aghast at old code. Rewrite!
4. Completely forget the reason I'm here.
5. Abandon project
6. Restart at 1
All this fawning over 2016 as if that wasn't the year the US first installed the orange despot. Pick something better to be nostalgic over.
Couldn't get back into my PowerShell project after taking 2 weeks off. Finally decided to just change the color of the status messages, and it revealed skipped functions that I hadn't noticed. So simple, and it showed where I needed to focus my efforts.
Veloviewer annual infographic showing how much time, distance, speed, and elevation I attained on the bike in 2025. 8880 miles, 435 hours, 380K ft of climbing.
Annual bike brag presented by @veloviewer.com
A big year. Not my biggest, but I lost a lot of ground in Aug-Oct to back issues.
My dog Junie wearing a festive "Happy New Year" tiara.
Junie wishes you all a very happy new year!
Hey welcome to Zwift! I've been on the platform since December 2015. It's a godsend in winter.
I love when half the evidence looks like Boba Fett's on-set photo complaint about craft services.
This is the same company that just announced plans to remove WINS. support.microsoft.com/en-us/topic/...
Sticky note that reads: "no more than 2 packs a day"
My youngest telling my oldest to share the pop tarts sounds more like she's getting to get him to stop smoking.
Signing a permission slip with a gigantic fuzzy blue pen
Just a totally serious guy doing totally serious things
After 10+ years of paying annual maintenance on my propane tank, I got a form letter telling me I'm no longer an "active" customer. It kindly offered that I could keep the tank for $250 or they'll come pick it up. So far my efforts to resolve this have been 100% AI interactions with no solution. 🤬
Lies, damn lies, statistics, and now a magical 4th thing: ~synthetic statistics~
'memba that time Microsoft released Loop in preview but you had to enable it in the Office Policy Service?
www.synergy-technical.com/blogs/micros...
...except the entries are not in the Purview Audit log. Queried all actions for the past 48 hours and just...nothing. If a change can be made, but can't be audited, no version or modification date info is changed, and it can't be queried, how do you know what or where to check when something breaks?
I stumbled on this article from December 2024 that says of course OCPS plays nicely with the other children! You can track all changes in the Purview Audit log. You just have to know to go there and know exactly what to ask for. This is not well-designed. techcommunity.microsoft.com/blog/microso...
Ooh a sternly-worded private message? My pearls!
A policy in Office Config Service that has been changed, but provides no evidence of change.
13 minutes after a major change, there's nothing. No way to know that 10+ settings just got added to this policy. I know every few years somebody in Redmond is told to dust off the old OCPS and force admins to use it, but it has to play nice with the other services.
Supposedly these actions get logged in the Entra audit log for compliance, but I'm hitting refresh like crazy and nothing's there. Even if they do get logged, that data's gone at 90 days, and I'm left with no version or history on the policy. 😮💨
Office Policy service setting managed by Microsoft baseline security mode in M365 Admin Center.
You click that blue 'save' button and this guy gets...created?...updated? with new settings.
