I had the pleasure of working with Made By Rocket (makers of Concentrate) when I was a senior in high school (I was 17). Living alone in downtown Boise Idaho, working 40 hour weeks for two different startups, and finishing high school, man that was a rough year.
Enjoyed all of this aside from the "finding a partner" section.
Finding a partner is trivial, keeping that partner is the hard part. Unless you want to keep finding new partners all the time (some do).
Maybe it's blasphemy for me to say this, but in my life it's been a lot harder to start a relationship than to keep one. Relationship books say that you have to work just as hard to keep one but that's nonsense. I don't need to buy my spouse flowers constantly or go on dates every weekend. (But surprise flowers are always a good idea.)
It's the same in my experience. It was very difficult for me to start a relationship, and much easier to keep it.
Starting one still looks rather random to me, you roll the dice until finally someone that you like likes you too, and that's most of what there's to it. Your attitude or effort can give you some small modifiers or penalties to the dice roll, but that's about it. It might sound childish but honestly, if I have to start a new relationship at some point, I'll be as lost in a sea of pure chaos as I was the last time.
On the other hand, keeping a relationship is pretty rational. Love the other person, care about her, don't be a dick, be emphatic, try to make her life as good as possible, and if you are not unusually unlucky you'll normally succeed.
Maybe it's also that as people that for one reason or other have a very hard time looking for relationships, we tend to value them more and make more effort to keep them than those who have it easier to get into one.
Well they're sort of right, but those material things aren't actually "working on the relationship", IMO. I've always taken it as "working in being the best person you can be" -- seems to have worked for the past few years for me so far :)
While recently digging into CoreLocation's CLLocationManager recently I also discovered that any app which is given location privileges can be saving your location every 10 min in the background. It was a surprise to me too.
This, along with the M7 motion co-processor in the new iPhone 5S, and Apple's pretty substantial investment in iBeacons, tells me that Apple sees the future of the iOS ecosystem as a series of experience-enhancing physically-aware ambient apps.
(The kind of apps that require a good notification center - like the one in iOS7 - cuz they're spewing so many little bits of suggestions at you.)
I suspect Apple will tread carefully in these waters, but initial signs are worrisome. Let's hope that they can figure out the personal analytics thing and work in some privacy with it too. They're not an ad company, so it's possible. :)
@rudyrigot and the team @prismicio http://prismic.io really have a handle on this problem.
They believe a github-esq content management system makes the most sense for content creators, and a content API makes most sense for engineers to distribute that content inside of a variety of platforms (mobile, a rails app, whatever). Saw Rudy speak at Zendesk/Rails meetup this month, it was a very good presentation (I am not affiliated with Prismic).
I've been playing with their ruby-kit, so far so good, really liking this approach and plan to see awesome things ahead.
The article is stating that developers should lean towards going static versus using any content management system. Would you like to provide a meaningful comment about how Prismic voids this author's argument?
Prismic allows you to "go static" for very little dev cost. Your content creators get a nice editor and can publish their content as needed, effectively making it static for you (the dev), as though it went through a build script (Jekyll or something "static"). The CMS gets out of your way, and you get to concentrate on making your app work, not getting into the complexities of building/maintaining a custom CMS.
I mean, that's what the assertion that static is the way to go eludes to, unless I am incorrect about the entire point of the article. It's about not getting dragged into the bog of making a CMS.
The author outlines various scenarios: do it yourself, to building your complex app on a CMS (ugh), or just going back to static because it is the simplest, hardest to fuck up option. I don't think he explored the idea of content management as a service fully, which is why I brought up Prismic—it is another option, and in my opinion, a very good one.
I should've made it clearer, sorry. When referring to CMS in the article, I refer to the wider meaning of a content management system, the code that you write as a developer of your own site, which happens to manage your content. Not a CMS that one could download and install.