metatation

I recently listened to the excellent "Fault Lines"[0] podcast from CBC podcast by seismologist Johanna Wagstaffe.

It describes the anticipated impact of the impending megathrust earthquake by examining the first moments, hours, days, etc after the event.

[0] https://www.cbc.ca/listen/cbc-podcasts/147-fault-lines

actually implemented in-depth testing beyond the anemic xcode support

I think this is the key motivator for people looking at alternative architectures. My guess is most people wouldn't stray very far from basic UIKIt/MVC if the established practices weren't so hard to unit test.

I see the experimentation with alternative approaches as the iOS community going through a phase of maturity, and is a positive signal. Many people in the community care deeply about issues of code quality and testability and while striving for simplicity. The increase in iOS architecture related articles is an indication of unrest and an active search for better practices. I suspect that it is only through these experiments that we will discover the balance we are looking for.

Similarly, I think articles like the OP are a healthy resistance against the pendulum swinging too far the other way. Although I agree with several points made I'm disappointed that testability isn't even mentioned and thus many points ring hollow.

Except that rotten tomatoes are not green..they are deeper red in color than a fresh one. Plus, why throw tomatoes at all if you like a performance. For me it's a completely broken analogy.

Maybe it's just me, but I find the "Tomatometer score" to be confusing. The combination of the tomato graphic with a number confuses an otherwise obvious rating.

I have a very strong (but false) intuition that the tomato graphic is a qualifier for the rating number. i.e. "Is this saying that 92% of people would throw tomatoes at this performance? Oh it's a fresh tomato...but wait, why would they throw tomatoes if they like it. Oh I see, the tomato is a lame representation of the rating, not saying something about the rating number."

Anyway, my false intuition is so strong that I still have to concentrate to ignore the tomato and simply look at the number (even if the number itself is controversial as noted by this discussion thread).

The following is a link to the tool he is using in the video. I've adjusted things so that it is displaying CO right before the emission event. Advance the time by 3 hrs to see the difference.

http://earth.nullschool.net/#2016/02/26/0000Z/chem/surface/l...

Does anyone have a good explanation for this?

I took a stab at this exact scenario years ago (1999?) and came to roughly the same conclusion. I ultimately decided to treat it as a travelling salesman problem where the distances between nodes (people) were weighted based on how recently they had matched with each node in the past.

This ultimately led me to create a TSP solving library that implemented a bunch of the known heuristic algorithms to approximate the solution. Worked out pretty well in the end and learned lots while I was at it.

How about a web server?

https://github.com/izqui/Taylor

You may also want to check out https://www.draw.io/

I'm not affiliated, but have used it many times.

It would have been interesting to see that heat map extend into Canada to see if the trend along the Rockies continued as expected. I found the following paper that at least anecdotally fits this theory:

http://www.pembina.org/reports/10_suicide.pdf

Apparently Calgary is going through a suicide epidemic:

"suicides are the leading cause of death for boys and men 10 to 49 years of age, ahead of murder, traffic accidents, and all other causes of death in this age group"

Note that Calgary is at high altitude as well, roughly 3500 ft.

Another strategy that I've often used is to just fix a few bugs that seem to be in the vicinity of the area you want to familiarize with. Heck, I even do this on my own codebases that I haven't touched in a while.

I find it helps focus the mind, provides a clear definition of success and forces you to think about a specific area of the code without requiring too much context.

This seems similar to what I've had to do with OpenCV in various iOS apps, but I think your results are more impressive than mine.

I had to sacrifice some quality in order to be able to do this with realtime video, but still, I should probably work out exactly what processing that command actually does and see if I can improve quality while still meeting the realtime requirement.

Thanks for sharing.

This made me think of Ken Thompson's Turing Award Lecture: http://www.ece.cmu.edu/~ganger/712.fall02/papers/p761-thomps...

I moved my family to Vancouver Island from Calgary in 2011. We ended up at Shawnigan Lake which is truly beautiful and a great community to raise young kids. I've been hosting the ios hacker group in Victoria as a way to meet like minded tech people. I'd love to connect with anyone interested...I'd be thrilled to discover someone else in the area too!

Consider following files with less.

I prefer tailing logs with less (rather than tail) so that the file is searchable (using '/ searchterm'). Then if you start following the file (using 'F'), your search term will be highlighted in the followed file.

I've experienced both styles for extended periods. I've worked with some really hard core engineering teams during my many colocation years and remotely for the past 2.5 years.

Over the years of working with many great people, I had built a habit of potentially over-collaborating with my peers. It was hard not to, considering how much smarter two people are than one. And with the right mixture of personalities and solving hard problems, it's almost always more enjoyable (even delightful) to work things through together. You get the stronger sense that together you are delivering a greatness that would be hard to achieve on your own.

I've really missed that part since I've been remote for the past few years. However I have had to learn to be way more self sufficient and resourceful. I think initially the transition hurt my productivity somewhat, but it also ended up making me much stronger and decisive because I couldn't fallback to the whiteboard anymore.

I think I still prefer the colocation style to some degree because working closely with great people is just so rewarding. Thankfully even while I'm currently in my fortress of solitude, I still have great peers to work and connect with through Skype. We have a team chat going all the time that is similar to the war room arrangement where we can socialize and discuss random (sometimes even relevant) topics.

All in all, working with great people is the key either colocated or remote.

EDIT: I should also mention that your ability to focus on your own dev work is great for personal productivity, but often your full value to the team is only realized when you shift your focus to helping the team. I've had many situations where I could have used one of those ticket dispensers because the line at my desk was out of control. I found that working from home for 1 or 2 days a week was a good balance in that situation. Time for some self focus and time for giving to the team.

My wife and I saw the HFR version and we were both put off by it. We're not exactly movie snobs or hard to please either...we've been to a theatre like 5 times since we had our first child 10 years ago.

I was completely unimpressed. It was painfully obvious that we were on a set instead of in some fantasy world. If this really is the future, then I hope that Knoll is correct that it will be solved by improved sets, props and lighting.

"we have plans for companies of all sizes starting at $12 a month"...couldn't find a link to more information on pricing.

Great Scott! That's almost enough to power a flux capacitor.

I think the "C++ is different in different environments, making it hard to write portable C++ code" argument is pretty weak. Is C++ annoying across different environments? Hell yeah, but I fail to see how is this any different/worse than production code.

I hate to be "that guy", but you have a minor typo on the home page.

"How does coffee affects your reaction time..."

It's unusably terrible for some people (like me). Apparently I now live on the moon: http://cl.ly/image/3q3v262G3P2s

Seems like there a general trend toward lower pricing transparency in online retail. Airlines have been doing this for years...sucks that it's spreading everywhere.

I get the humor of this library, but in reality wouldn't you just use HTTP 1.1 chunked transfer encoding instead? According to http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol, that would even work with your IE 2 users.

Surprising to me is that Amazon is charging more for the Kindle version than the hard cover of "Awakening Joy" ($19.34 vs $17.16): http://www.amazon.com/Awakening-Joy-Steps-That-Happiness/dp/...