jonstjohn

I’m an advocate of UTC everywhere.

I landed in Australia this morning and as soon as my phone updated to Dec 2 on the new network my phone started locking up immediately. It would go to the loading screen (spinner in middle of screen) every 8-12 seconds then reset to lock screen after 4-5 more, making it nearly impossible to even access settings for more than a few seconds. I was able to disable local notifications for the apps that I know use them after 3 or 4 tries (required some quick navigation to get to the right screen before it locked up). I captured the logs on a number of occasions but and saw a few anomalies in the logs including this one:

iPhone kernel[0] <Notice>: 2404.102 memorystatus: killing_highwater_process pid 736 [SpringBoard] (highwater 16) - memorystatus_available_pages: 26834

Possibly SpringBoard consuming too much memory because of the bug?

Additional saw some of these, although not sure if they are a factor:

iPhone dasd(DuetActivitySchedulerDaemon)[107] <Notice>: com.apple.healthd.achievement-asset-manager:E60402:[ {name: NetworkQualityPolicy, policyWeight: 11.400, response: {Decision: Must Not Proceed, Score: 0.00, Rationale: [{[wifiQuality]: Required:100.00, Observed:50.00},{[networkPathAvailability]: Required:1.00, Observed:1.00},]}}

Thanks! I'll have to check that out. I really love the CircleCI service - incredible time saver in getting continuous integration setup and so many features out of the box. Would definitely recommend it to anybody looking for a hosted CI solution (good price, too!).

Agreed about the conventional wisdom. Unfortunately, I think many companies aren't 'doing it right' and end up with somewhat bloated systems. From what I'm hearing, most companies roll their own solution to that problem and don't use any specific tools to address it. I'm seen some rudimentary statistics in Sauce Labs, as well as built into Jenkins.

Great tips - thanks! In addition to some slow-running tests, we do have a lot of test duplication. It's probably time to step back and evaluate what tests are overlapping functionality.

Do you use any tools to facilitate your workflow on fixing tests? Typically, we run a regression build on a branch and may find a half dozen failures. With 4-5 developers on a distributed team, we've built a utility for 'checking out' and marking a test as fixed (to be verified on the next build) but haven't seen any similar functionality in the CI systems we use.

Did this protest make it into the event? I did hear some yelling during one of the keynote talks.

I actually have a similar problem with UPS. Last year we had a dyson vacuum delivered to our house that was left on the front porch, about 10 feet from the sidewalk. The box was the manufacturer's box with pictures of the vacuum and the brand written in big letters. We weren't home but when we did get there, there was no package.

It was ordered from Costco and their service was fantastic. We had a replacement within a few days. The problem was UPS. After that incident, every single package had to not only be signed for, but actually have a person present to receive the package. I'm not sure if this was retribution on behalf of the delivery person, who probably got into some kind of trouble, but it is what it is. It is very difficult for us to get packages at home now.

I love prime, but it would be fantastic if I had the option to choose a shipper, even if I had to pay a couple dollars extra. USPS is actually much better about leaving packages, which are by far usually under $20 and small.

My problem is that I tend to wear out card before I get a replacement. For example, my debit card currently requires 3-4 swipes to get it to work. I'd probably keep a backup card in my wallet if I decided to get Coin, just in case, but really like this idea.

For most self-swipe checkouts, it seems like this card would work well (coffee shop, grocery store, etc). But, it isn't too uncommon to have a merchant request to see the card, and some larger retailers (e.g., Lowes) have to input numbers off the front of the card, as well.

A wallet is a single point of failure device. It's a lot more of a hassle to remotely wipe my wallet (remember all the cards, cancel them all individually).

I recently did a challenge of 100 days of commits to side projects and I'm now at day 96. I think this was awesome for me, as it kept me really focused on my projects, even if some days I had only small commits.

I think my next challenge might be even more focused and look to launch one of my prototype projects in a specific amount of time. This will force me to focus and launch something, even if it isn't perfect.