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:
Anonyome Labs | iOS Developer, Web Developer | Salt Lake City, UT | Onsite | Full-time
Anonyome Labs is a well-funded startup building a full-featured safety and privacy app called Sudo.
Sudo is a powerful new way to protect your safety, privacy and personal data when you’re socializing and connecting online and off. Sudo automatically generates private personas — complete with email addresses and real working phone numbers. And, they’re all securely and privately linked to your iPhone or iPad.
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.
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.
As somebody who is in a hiring position and aspires to a more gender-balanced work-place, I've found it really disheartening that so few applicants are female. We have mostly male developers and leadership, so I understand that a female coming into our office might not feel particularly attracted to it. I guess it is a slow process to try to improve that situation.
These are great! I think I've seen Bee Minder before. Honestly, it has helped me out tremendously to just keep committing. I have days where I commit some really trivial bit of code, just to keep things going, but first thing in the morning I'm thinking about what I plan to commit that day. It keeps me focused on my side projects.
I'm trying to do this right now. I challenged myself to do 100 consecutive days of commits to my side projects and I'm currently at day 94. Unfortunately, my private repos don't show up in my streak unless I'm logged in, but most of them are here: https://github.com/jonstjohn .
I've still bounced between about 3 projects in the past 3 months. I struggle with what seems like it should be the last 5-10%, although I'm looking at forcing myself to launch even if I'm not happy with everything.
The "we're changing the world" mentality is a bit annoying to me, as well. When I think about changing the world, I think about discoveries in medicine and science, people dedicating their lives to improving humanity, etc. To me, it's just a popular catch-phrase for 'the pitch' and relatively devoid of meaning in most cases.
I think the main benefit of ClimbingWeather.com is ability to quickly find climbing areas. Looking for the forecast for Indian Creek, Joshua Tree, the Gunks, Cathedral Spires? You don't need to find the nearest town or hope the forecast is right (maybe you'll find it is 10 degrees difference due to elevation). Agreed that the growth potential might be somewhat limited, but there is still a small and solid audience that likes the format.
It was ad-free for years, finally put some ads up last year and now it's covering my expenses. Haven't done much development in a couple years, but working on an updated Android app. A bit skeptical that I'll make much money from it, debating pay-app vs ads vs free-free. Now trying to pick up some real advertisers (currently adsense).
This is a cool idea but seems fairly limited when you take into consideration the state of the resources used in your application. For example, if I have a method that checks the balance of an account, I may hit that method with an account with a positive balance, make a payment, then hit the method again and have a zero balance. The method might take an account instance and the same account instance yields two different results.
I realize that this may be an issue with a poorly written method or un-anticipated side effects, but with legacy code, that is often what you have to deal with.
I've experimented with running headless tests using Firefox, in hopes of getting a good performance boost in terms of test speed. The results actually did not indicate much of a difference. If anything, FF in headless mode on CentOS ran slower than on Windows.
That's not to say there aren't good use cases for running headless browsers with Selenium. One huge benefit is not needing to run Windows VMs.