This is incredibly interesting, and something I wouldn't have thought much of before becoming a parent.
Since our son was able to speak, he was able to vocalize when we were near a family member's house (I saw this weekly as we drove from the San Francisco Peninsula up into the city). I was always curious what triggered him to know "we're nearby". We passed several unique structures (overpasses, apartment buildings, signs) but I was incredibly curious which ones he associated with being nearby this particular relative.
Eventually when he was a little older, and we asked, he was able to say a specific color building "told him" he was close. Super interesting. Child development and understanding in itself is so amazing to watch.
Every step of the way they were scheming how to get to feature films -- everything in between sounds like a means for resources (money, hardware, people, so on so forth).
Currently reading The Pixar Touch by David A. Price and they talk a lot about the types of software and standards for rendering they had to create over the years. Incredibly interesting looking back at what they were able to achieve. A talented crew for sure.
I immediately checked for that level of scope when they announced it, my post was merely a "this would be pretty amazing for security conscious end-users" not "this part of the API is cool" -- a wishlist item have you.
If they can combine this ease of accessibility for developers with a security model on the end-user side, I think it can be a solid win.
I'd love to see granularity in what the API can access, for example, TripIt may request something like "Grant access to emails from the domain travelocity.com, usairways.com, etc.," and I can know with confidence that they will not have access to the rest of my inbox.
When I first started work out of college I kept a notebook of "things I like/don't like" about my managers, mostly as a training piece for myself. One of the top qualities one of my managers had was his comfort level with admitting to me "I don't know the answer to that, but I think I know where we can find it".
Probably summed up as something like "check your ego at the door".
This goes for not only managers, but any member of an organization -- pretending to know something when you really don't and being afraid to ask questions is a huge red flag to me for both managers and employees alike.
And back to the list, IMO that's a pretty good list, especially coming from one person's experiences.
One of the bigger takeaways from this article should be to make a decision of where to set layout parameters, and stick with it. I'm sure we all have opinions on using the in-code method vs IB, and can debate 'till the end of time. As a relatively new iOS dev picking up an existing codebase, the biggest thing I could say is be consistent. The number of times I tried setting something in code only to find it was being changed in IB is far too many.
Short answer? Yes.
It has nothing to do with Codecademy though, it has to do with the fact that they were ambitious enough and had the drive to learn to code, and pursue it via some means (in this case, Codecademy). That speaks volumes.
Of course they'd be put through the same screening as anyone else applying for the role, so it's not like you're hiring someone that does not have the appropriate skillset for the job.
Frustrating...didn't think of this before posting, sorry to those of you who get the "Sorry..."
Maybe give TunnelBear a try? It's a free VPN service capped @ 500MB / month I think.
I made this mistake on iOS6, and swore I wouldn't let it happen again with 7 -- simple instructions, yet so easy to forget you need to move from beta -> release.
I remember seeing similar behavior trying to do testing in a cafe using a Verizon MiFi over LTE. I called up their support staff and they tried to blame the problem on me saying they don't block anything, it must be on my end...typical.
I can't say I've ever noticed this feature before on Dropbox. I came across it while searching for the correct use of the word/term packrat (with or without hyphen). Nice use of the word on Dropbox's part.