I am an extremely-overweight, athletic person... meaning I am about 80 pounds overweight but can still a wide range of sports on a competitive level with average citizens minus the endurance.
I did Day 1 almost a week ago. If it weren't for my laptop overheating ten minutes of the twenty minute video, I probably would have died. I was so out of breath. They were doing about 90-100 reps while I was struggling to do 1 properly and managed maybe started at 20 which soon dropped to 5-10. But at the end of the day, my body felt good. My glutes were so tight, I had trouble sitting and getting up for the next 3 days.
I just finished Day 2. I managed to complete the whole 40 some minutes. I was able to manage a reasonable pace for about 15-20 minutes which felt like an hour. Near the end with the push ups and plank-position exercises, I had trouble following as I had to face down which then I couldn't look up to see what I was supposed to do... but who am I kidding... I was surprised I wasn't lying on the ground. Occasionally, I just did some of the run-in-place exercises to watch what they were doing while keeping my heart-rate up. Although my muscles weren't too sore, after a few minutes of rest, I started to feel some of the workout sores. We'll see how I'll manage any non-horizontal positions tomorrow.
For a run down of the exercises, this blog (last update in Dec 2014) does a great job with a fun-style read. https://optforinsanity.wordpress.com/2013/10/22/day-2-plyometric-cardio-circuit/
Thursday, May 18, 2017
Tuesday, May 16, 2017
GridView with multiple columns with the same name
Microsoft ASP.NET 4.5
Visual Studio 2013
Scenario: Joining to tables that have the same column names but different uses without using alias (because sometimes you don't have access to the data or query).
Solution: The first column will be the original column name. Each additional column will have an integer counter starting at 1 appended to the end of the column name.
Exampe: If the column name is XXXXXX, then the first column will be XXXXXX, the second column will be XXXXXX1, then XXXXXX2, etc, etc.
Visual Studio 2013
Scenario: Joining to tables that have the same column names but different uses without using alias (because sometimes you don't have access to the data or query).
Solution: The first column will be the original column name. Each additional column will have an integer counter starting at 1 appended to the end of the column name.
Exampe: If the column name is XXXXXX, then the first column will be XXXXXX, the second column will be XXXXXX1, then XXXXXX2, etc, etc.
Labels:
C#,
data,
MS SQL,
programming,
Visual Studio
Tuesday, April 11, 2017
Buggish: "We found your Charge HR" but still get error "Bluetooth issues" on Droid Turbo
Rebooted phone several times, restarted FitBit app several times, finally tried rebooting the FitBit itself (hold down button for several seconds while plugged in) which seems to finally work.
Symptom: FitBit no longer synced with phone. Thought maybe I had to re-pair the device, I removed the device. When re-pairing, I continually received the error "Bluetooth issues" "if you see this message for the first time..." Occasionally, I was able to get the app to show "We found your Charge HR" but would still popup the Bluetooth issues error box.
Solution: Called tech support, explained the situation, and they were able to cover a replacement under the warranty. Which was really nice since I didn't think there was warranty. The experience was positive although I really wanted to know what was wrong with my current one.
So far, I am not exactly sure what the fix is as I cannot replicate the issue. It appears restarting the Fitbit fixes this problem. But may also include restarting phone and app. Restarting app fixed the problem of pairing as it appears to only work on the initial attempt. If I retry then the FitBit appears to no longer attempt to pair even though it says it is searching. The FitBit is definitely in some sort of off-mode during this time as the steps are not registered either. That is about all the information I think is relevant.
Symptom: FitBit no longer synced with phone. Thought maybe I had to re-pair the device, I removed the device. When re-pairing, I continually received the error "Bluetooth issues" "if you see this message for the first time..." Occasionally, I was able to get the app to show "We found your Charge HR" but would still popup the Bluetooth issues error box.
Solution: Called tech support, explained the situation, and they were able to cover a replacement under the warranty. Which was really nice since I didn't think there was warranty. The experience was positive although I really wanted to know what was wrong with my current one.
So far, I am not exactly sure what the fix is as I cannot replicate the issue. It appears restarting the Fitbit fixes this problem. But may also include restarting phone and app. Restarting app fixed the problem of pairing as it appears to only work on the initial attempt. If I retry then the FitBit appears to no longer attempt to pair even though it says it is searching. The FitBit is definitely in some sort of off-mode during this time as the steps are not registered either. That is about all the information I think is relevant.
Labels:
buggish,
FitBit,
mobile app,
troubleshooting
Subscribe to:
Posts (Atom)