207 karma · joined May 27, 2012
It describes the anticipated impact of the impending megathrust earthquake by examining the first moments, hours, days, etc after the event.
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.
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).
http://earth.nullschool.net/#2016/02/26/0000Z/chem/surface/l...
Does anyone have a good explanation for this?
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.
I'm not affiliated, but have used it many times.
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.
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.
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.
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.
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.
"How does coffee affects your reaction time..."