I know, it’s a little corny, but instead of writing out a “To-Do List” — which implies hard labor and/or something I force myself to do — these days I write “WIN” on the top of my index cards. WIN stands for, “What’s Important Now”, and I find that this change in wording changes my attitude towards the things that need to be done. Rather than thinking, “Ugh, okay, what do I have to do next,” I now think of these tasks as important to me, my future, and my success.
“I have no idea who that guy was, but I know that he just reset our karmic destiny.”
(A quote from the book, Love Everyone, that makes me wonder how many times our karmic destiny is reset and we don’t notice it.)
When you hear mindfulness people say something like, “Life is like a dream,” one thing they mean is that more than 99.99% of the stuff going on in our minds are thoughts about the past and the future. (Past happiness or regrets, and future hopes and concerns.) Because the only thing that’s real in the present moment is what’s actually happening in *only this moment*, anything that’s outside of this moment is in a strict sense no longer real.
Along this line of thinking I like Eckhart Tolle’s two quotes, “The present moment is all you ever have” — you know that to be true for sure if you’ve ever lost consciousness, not knowing if you’d ever open your eyes again — and, “The whole essence of Zen consists in walking along the razor’s edge of Now.”
vox.com has a story titled, In Colorado, a glimpse of renewable energy’s insanely cheap future.
According to ARK Invest, the cost of industrial robots will drop 65% by 2025. As they write, “Combined with advances in machine learning and computer vision, this drop in costs should cause an inflection point in the demand for robots as they infiltrate new industries with more provocative use cases.” (Image from the ARK Invest website.)
“The fact that #scala Future is not lazy just blows my mind. After years of using Scalaz Task, Future is now totally unusable.”
The last part of that tweet is a bit of hyperbole to me, as I’ve been using the Scala Future for a long time myself, and I’ve had no problems using it. That being said, the examples at the top of the Reddit page were interesting, so I decided to try to understand the differences.
Mark Burgess has a long article based on the keynote address for the Reactive Summit 2017 titled, Microservices, the future of society, and all that.
I’m working on a little app for my Scala & functional programming book I currently call “Future Board.” It works a little like Flipboard in getting news headlines from different sources, but it uses Scala Futures and a few other functional programming techniques.
Here’s a little example of how exceptions work with Scala Futures, specifically looking at the
onComplete ‘Failure’ case.
In this example I start three Futures that run for different lengths of time, and the shortest-running
Future throws an exception: