# Model calibration plot

I finally read Nate Silver’s The Signal and the Noise. At the time of its release in 2012, it was a rather unique book. It discussed statistical modeling, Bayes theorem, and the art and science of predictions in a way that the general public could follow and understand. A book ahead of its time and it has held up nicely when I read it in 2019.

One of the things the author talks about in the book are weather predictions, and in the chapter, he has a short mention of model calibration plots. “Calibration plots? That looks useful!” I thought and my interest had piqued enough to try it on some of my own models.

When evaluating models we run into mentions of accuracy, f1 score, or confusion matrixes. Calibration is not something I see too often and it turns out it’s a pretty good view into how your model is performing.

In general terms, calibration is a comparison of the confidence of your model with the actual results. If a model is 90% confident in the prediction, what’s the percentage it is actually correct? Does it have “blind spots” where it is a model is overconfident consistently? Calibration plot can help you spot such trends.

The method to calculate it is pretty straightforward. Here is a snippet of code that illustrates the approach:

``````predictions = model.predict(X)
probabilities = model.predict_proba(X)

calibration_map:Dict = {}

for idx,val in enumerate(predictions):
true_outcome = y[idx]
predicted_outcome = predictions[idx]
confidence = float(max(probabilities[idx]))

calibration_key = int(confidence * 100)
# use 5% increments for calibration values (50, 55, 60, etc)
calibration_key = calibration_key - (calibration_key%5)

if calibration_key not in calibration_map:
calibration_map[calibration_key] = (0, 0)

wins_losses = calibration_map[calibration_key]
if predicted_outcome == true_outcome:
wins_losses = (wins_losses[0] + 1, wins_losses[1])
else:
wins_losses = (wins_losses[0], wins_losses[1] + 1)
calibration_map[calibration_key] = wins_losses

with open("calibration.csv", "w", newline='') as o:
writer = csv.writer(o)
writer.writerow(["index","real","model","number_of_games"])
for pct in calibration_map:
wins_losses = calibration_map[pct]
number_of_games = wins_losses[0] + wins_losses[1]
true_pct = wins_losses[0] / number_of_games
true_pct = int(true_pct * 100)

# don't bother with small sample size
if number_of_games > 20:
writer.writerow([pct,pct,true_pct,number_of_games])``````

What we are doing above is running through model predictions. For each prediction, round down to the nearest 5% interval and note the outcome of his prediction. Tally # of correct vs incorrect and you have the accuracy % for each interval. I output this into a CSV to later render with pandas:

``````import pandas as pd
import matplotlib.pyplot as plt
import seaborn as sns

sns.set()

df.sort_index(inplace=True)
df.loc[:,["predicted","actual"]].plot(figsize=(15,10))``````

Once you run this, you should see something like this:

This is what I see when I do a calibration plot for my NBA model for 2018-2019 games. You can see how the actual values are pretty close to what it thought it should be with biggest drift around 50% and 85% prediction interval. Pretty cool!

# Factfulness

I just finished a pretty cool book called “Factfulness“. It essentially presents a summary of the current state of the world from the big picture perspective with broad categories of income, education, and health. It deep dives into how misunderstood the world is by the masses, how biased is our outlook of the world, and the main reasons why we are so wrong.

An average person continues to have an outdated mindset about the world and assumes that things are much worse than they really are.
However, the reality is that the world is an incredibly better place than it was even as recently as 40 years ago.

The book begins with a 13 question quiz and the results he has collected over the years are downright abysmal. The majority get only three out of 13 right! (got 10 out of 13 but I am an optimist and basically, if you picked the optimistic answer, you were right most of the time). It did not matter how well educated the test takers were, what country they came from, or what profession. Not a single group of people that were polled beat out random guessing. 15% of test takers scored zero!

Bashing media was not one of the goals of the books, but it came up rather frequently when the author dived into the reasons why the population continues to be so disconnected from the reality. Our worldview is being updated by us reading the news. And news, especially in today’s world, are not interested in keeping us educated. The goal is to shock, entangle, and keep on coming back for more articles that shock, entice fear, and further cloud our thinking.

The news is not the same as it used to be. The amount of articles is ever growing and is insanely high today. The same story is distracted seemingly millions of times from various angles. So much fluff and irrelevant commentary. Media has had years of training on how to capture our attention with headlines and article structure. Keep the stories shocking, latch on to people’s fears, capitalize on uncertainty and our biological wiring.

I can’t blame the writers. Their goal is to make money. How do you make money? By building audience and traffic and nothing generates traffic more than attention-grabbing headlines and shocking articles. The goal is not to educate or report the truth without embellishments or conjecture. I honestly believe we are far better off leaving the major media outlets. The negatives far out weight the positives of following the information flow.

Last year many of us said we will leave social networks such as Facebook (although not sure how many actually did). I went through with the departure and could not love it more. Couple months back I have started to cut out my consumption of news in general and it’s been refreshing. This book is making me think that I should do more and go deeper with the clearance.

The first thing I did after finishing the book is clear out my featured section for google assistance app on the phone. Previously it suggested news articles, and honestly, I visited that page at least 5-6 times a day. No more. Gone. That was the only news outlet that I let myself visit, and now it’s empty. I am sure I will need to replace it with something, but for now, I want to see how far I can go without any news dropped on my lap. I have a feeling that what I will replace will be specific blogs or authors and that’s about it. Let’s see how this experiment will go.

# End of the year reading list

Happy to report that the reading habit is doing well with a total of 26 books read this year, averaging about two books per month. Considering that the majority of what I read is non-fiction work, I think that’s a pretty good rate. The highlight has to be the book I just finished, called “Bad Blood”. I accidentally picked it up from my library’s featured section. It’s a story about a now-defunct startup “Theranos” that promised cheap and superior blood testing technology, rose to 10 billion dollar valuation and the founder was considered as the next Bill Gates, etc. All of it came crashing down when it was discovered that the company lied about its capabilities and had created nothing but barely functioning blood testing devices that could only do a few tests and even then performed terribly. The story might not sound that amazing since many companies rise and fail. What makes this one different to me is two things. One, the lengths that the company and the major players went to hide the shortcomings of the technology and all the “lawyering” it employed to survive. The second reason is that the book is just well written and the reporter stayed out of the way so to speak and presented the timeline in an incredibly coherent and clear fashion. Highly recommended. Here is my month to month breakdown: January: no books, sad February
• Principles: Life and Work – Ray Dalio shares his core principles for various areas of life. It was excellent, causing me to blog about the book and the author’s way of explaining the expected value calculations.
March
• Happiness by Design: Change What You Do, Not How You Think – a somewhat typical self-help book that gives advice on how to live a happier life. The main idea was that happiness comes from having pleasure and purpose and there are ways to increase the amount of each with various advice on how to do so.
• Skin in the Game: Hidden Asymmetries in Daily Life I am a big fan of Nassim Taleb and this book did not disappoint. I can’t summarize the book in a single theme as his touches a large variety of topics, as usually is the case. Most of it is around the probability of events, the importance of understanding probabilities and causes if you are going to make decisions for the future. And of course, the usual Nassim’s digs at journalists and academics that don’t avoid work in the real world.
• Designing Bots: Creating Conversational Experiences – this book was meh, a summarize of what it takes to design a bot and some tips.
• War Against All Puerto Ricans: Revolution and Terror in America’s Colony -not the book I would typically pick up but read it based on my wife’s recommendation. It was an interesting diversion from the usual science/software reads into the history but that’s about it. Summary – being colonized sucks and it’s not as glorious as the victor’s try to portray it. What else is new…
April
May
June
• Ego Is the Enemy – this was a good reminder of focusing on your work and goals and ignoring the desire to get fame and recognition. It’s a tough balance to achieve as recognition can serve as a source of energy to continue going and working hard but ultimately the book is right: recognition is fleeting and often fake, find the reward somewhere else.
• Nine Algorithms That Changed the Future: The Ingenious Ideas That Drive Today’s Computers – it was a decent summary of things like encryption, compression, etc.
• Designing Distributed Systems: Patterns and Paradigms for Scalable, Reliable Services – I had high hopes for this one and was very much disappointed. It was basically a collection of patterns expressed via Kubernetes templates, boring.
• Writing High-Performance .NET Code – I picked this one up after somebody I know mentioned it on twitter, it provides an excellent insight into troubleshooting and writing fast performing software.
July – no books, not unusual for me to skip reading during summer days. August – no books read, same as July. September
• Getting to Us – as is the case almost everywhere, eventually I pick up sports books and get my sports reading binge going. This one summarized several high profile coaches and profiled what were the key things they did with their teams to achieve success.
• Gridiron Genius – continuing the sports reads, this was a book by a football scout and front office executive that worked with Bill Walsh, Bill Belichik, and Al Davis and shared some of this thoughts and stories on leadership and successful team execution.
• Python Machine Learning Cookbook – had very low expectations for this book and instead was pleasantly surprised. I would consider this a must-have if you are doing machine learning with Python. A good guide to solving a variety of problems and can serve as a way to get surface level info on a topic before diving in deep somewhere else.
October
• Algorithms of the Intelligent Web – Ideas on how you could make the software more intelligent (user recommendations, machine learning, search, etc). The topic sounds good but the book itself is not detail enough to be useful.
• The Master Algorithm – I consider this a must read if you have started with Machine Learning applications. The author does an excellent job dissecting the history of machine learning techniques and tries to anticipate what is the holy grail/final frontier for the machine learning industry. I absolutely loved this book and how it walks the reader through the history while tying all the different pieces together and explains what is happening in machine learning today.
November
• The Site Reliability Workbook – a follow up to highly regarded, “The Site Reliability” book, very disappointing to be honest. Maybe my expectations were too high? I recommend skipping this book if you are considering reading it.
• Building Algorithmic Trading Systems – I got this book to learn some of the tips and tricks for building a sports betting system. I felt like there are some parallels between sports event and betting on them and the stock/futures market and betting on those. Definitely got some good insight on how to evaluate the prediction systems, I think that’s where I found it the most useful.
December
• When – lukewarm about this one, perhaps because most of the material it presents I’ve heard it before.
• Kids Are Worth It! – I read one or two books per year usually on raising children, just to get some ideas and thoughts on dealing with the little ones (have three of them in my house). I thought the author was too conservative, but eventually, I came around and loved this book. A lot of very practical advice on dealing with children issues from the time they are two to until they go to high school.
• Dopesick – The information presented inside is very powerful and paints a detailed picture of how prescription medicine addiction comes around and leads to other drug use and the demise of communities and institutions. Eye-opening information on how pharma industry played a critical role in introducing painkiller addiction to the masses and how the rest of the system furthered it along into an epidemic that you hear about today.

I really enjoyed reading Domain Modeling Made Functional, an excellent intro to modeling and implementing software requirements using a functional language (F#) with Domain Driven Design (DDD) principles.

I don’t use F# (but appreciate functional programming in general) and the reason why I picked this book up is to learn and revisit DDD concepts.

The first two chapters of the book were the most valuable. The main takeaway: when doing DDD, start with the events and not domain objects! I know that when I approach a problem, I always start with trying to define the domain objects. This seemingly small switch to focus on events instead felt profound as I was reading the first few chapters.

The biggest value that software gives to its users is not in the domain objects it stores and retrieves, but in the transformation of the input data through the domain, usually via workflows which are triggered by … events! Identifying the events will give you a good idea of possible workflows that either exist or will need to exist which then lead to defining commands, bounded context, domain objects, aggregates, etc. It all starts with events.

The process of identifying the events occurs during the eventstorming sessions (a good intro here). Eventstorming unites implementers and business users together as they work on defining the events, commands, and bounded contexts. Pulling people together during this phase is a great way to make sure that as little as possible gets lost in translation when somebody takes the requirements and then “translates” them to the implementation group. Instead, implementers are active participants that learn and define things together with the users.

A domain event is the starting point, always termed in the past as it has occurred and cannot be changed. Eg. user created, user added, etc. Events can start workflows which then end with usually another event that other contexts can subscribe to and act upon.

And then the rest of the book was more around F# approach to design and implementation. Several rules stand out, such as: avoid names and concepts that are not directly described by domain experts;  build the smallest units, functions, that do the work, connect the functions to form services. Connect the services as pipelines to form workflows.

Really neat book. Even if you don’t use F#, this books introduces many great concepts and if you don’t dabble much in DDD space, gives you topics about DDD that you can then go and explore on your own.

# Expected value calculations

I am in the process of reading “Principles: Life and Work” by Ray Dalio. Overall the book is very good and informative but one chapter really caught my attention: Learn How to Make Decisions Effectively.

In particular, what stood out there was the author’s explanation of making decisions as expected value calculations.

When you make a decision or take action that can either result in success or a failure, you have these factors to consider:

• the probability that the action will result in success
• reward gained if the action results in success
• the probability that the action will result in failure
• penalty/loss if the action results in failure

The expected value (EV) for such a decision then can be defined as follows:

EV = Probability of success * reward – probability of failure * penalty

EV greater than zero can be thought as a winning decision and if you have multiple choices, pick one that has the highest expected value.

A quick example from the book: let’s say the reward for being right is 100\$ and the chance of you being right is 60% (0.6). The penalty is also \$100 dollars (and the probability is 0.4 arrive at 1-0.6). Then EV = 0.6 * 100 – 0.4 * 100 = +20.

This simple example is all well and good but check out couple thoughts now to branch out further.

The best bet is not always a bet with the highest probability. If something is very probably but has a small positive outcome and very large negative outcome, the EV is negative.

A decision can have a relatively small chance of success but if the payoff is much larger than the cost if you fail, that decision has a positive EV and is the right choice as long as you can cover the loss. This is where investments in risky but highly rewarding endeavors can pay off greatly. Again, as long as you can cover the losses.

If you stick to “playing” with EV positive outcomes, over time you will come on top. The key is to make sure you have a good information and feel for the event’s probabilities and costs.

What’s cool is that when taking an action or making a decision, you have four things that you can leverage to increase your EV: increase your chance of success, increase your positive outcome, decrease the chance of failure, decrease the penalty. Not always all four are malleable but you would be surprised how often there are other options to consider that increase the expected value. Following such thought process teaches your brain to search for alternatives that influence the four factors I just mentioned.

Furthermore, when you start searching for different options with better odds, the actual odd value is less important than knowing that the decision you are picking is either less risky (you are decreasing the chance of failure) than the previous one or is more rewarding, etc.

Now whenever I am working on let’s say a feature release, I consider expected value formula and ask myself: what’s my confidence level that what I am releasing will work correctly? In my profession (software) this is often tied to proper and extensive testing and validation. If I get a feeling that I could have done more testing, I right away do so to increase the chance of success. If the release goes wrong, what is the worst that can happen? This often makes me re-evaluate the size and scope of the release and if possible I break things up into smaller pieces which means the impact of a negative outcome will be smaller.

I am continuing to dig and have thought exercises with this rule but so far it has been very beneficial.

# Book review: How to Fail at Almost Everything and Still Win Big

The book was highly enjoyable and packs so much useful information and advice. I am impressed how succinctly and clearly Scott has expressed his opinion on a large variety of topics.

It is essentially Scott’s take on life and how to succeed. Success can mean different things to different people, but I can safely say many will find information in here that they can use. I would highly recommend this book to anyone who is looking to get a good sense of how one can accomplish difficult tasks and live a fulfilled life.

At a high level, his take on life boils down to several key points (which I hear repeated in various forms over and over again in other books):

Increase your energy capacity by eating right, getting a good amount of sleep every day, and exercise/stay active. These are the foundational pillars that enable you to work hard, think clearly, seek out knowledge or adventure, and in general lead a fulfilling existence. Beyond that, you need luck, be at the right place at the right time so to speak. But luck is not a fixed concept, you can increase your odds of luck by picking up new skills, mastering concepts such as psychology, finance, social interactions, public speaking. The additional skills will increase your surface area of luck, so to speak and the rest is up to you: once given an opportunity, take

Through it all, embrace the failure for it is a valuable signal and a learning material that if utilized properly will enable you to grow.

The topics that the book covers are rather varied and all expressed from Scott’s point of view and what he learned. The presentation style though is fun and engaging which makes it easy to read and learn.

A couple of ideas that stood out to me in addition to the above big level concepts:

• Systems vs goals. I’ve had heard this distinction before but did not fully buy into it. The author has some really interesting points and examples of how expressing your goals as systems instead can make a huge difference.Let’s take reading books as an example. You could set a goal of reading two books per month. It’s measurable, you know when you succeed or fail. And is actionable, action being sitting down and reading. But putting that number out there, Scott argues, makes you feel somewhat inadequate if you don’t succeed, you are always in a state of failure until you reach that number.

Instead, you should come up with a system for reading books, such as: anytime you commute on a train, you will read a book (instead of looking at twitter/fb/etc on my phone). Or every other day during lunch you will read. etc. You pick what works for you and do the action. You don’t worry about the count of books, just make sure you put a system in place that allows you to spend time reading. Then pay attention to how well you are doing. If you are not reaching the amount of reading you want, try to find a better system. Iterate.

It’s a simplified example, but if you apply it to enough behaviors, you can have a pretty good setup going on for reading and anything else. For instance, I have couple systems for reading (that I setup without even knowing): 1) keep my kindle in the commuting backpack 2) when on a train, read 3) when I see a book I like, buy it. The number of books per month varies, but I feel like I am always reading. I am almost at the end of the month and have finished four books. Last month 2, a month before 2. I am happy with the amount of reading I do and sometimes it drops to zero but that’s OK.

• Happiness level of a human being depends on the direction of the progress and not the current state. (e.g. A rich person that goes from 2 billion to 1 billion dollars in fortunate is often sadder than a person who is increasing his earning from 90k to 120k).
• Affirmations, a somewhat vague and controversial concept of essentially wishing for a certain outcome and it becoming a reality. Scott presents multiple examples from his life and makes sure to mention how there is no science behind it and it all could essentially be bullshit. Yet he seems to have used them in the past and tends to believe there is something there.
• Avoid career traps that require you to sell your time for money. I am definitely in that stage right now, basically, my time is what earns me money and this book is making me strongly consider what other revenue streams I could add to improve this situation.
• Happiness is being able to do what you want when you want it. The flexibility of choosing when to do the activity that you want to do is very important to us, it appears. I can attest to that and could explain why I am very happy at my current job: the flexibility of my schedule.
• One should be familiar with or get a good understand of topics such as psychology, public speaking, accounting, and a few other foundational skills. I jotted down the list and see which ones are my weak points. I am always taking courses in my field of profession, but this book is making me consider if I should try to branch out and see if I can learn a complimentary skill that is not necessarily tied to my current profession (software engineering).

Again, if you are a looking for an easy yet educational read, I highly recommend Scott’s book. Enjoy!

# Book review: Antifragile

Antifragile

Absolutely loved the book and its main messages. It’s deep, ambitious, and very thought provoking. It was an immense pleasure to read.

Things that jumped out of me, in no particular order:

• Term “Antifragile”. As defined by the author, antifragile is something that benefits from random events, somebody that gets stronger when stress is applied to it. This is a step above “robust” where robust most often means ability to deal with stress. Love it as a concept. Netflix’s Chaos Monkey seems to be something that you could define as a tool of antifragility. By randomly killing cloud instances, it helped Netflix build a more resilient architecture that now survives all kinds of cloud service failures. It actually gains from AWS going out as the rest of the services scramble, they stand strong and get positive press, admiration, tech fans that want to work there, etc. Evolution is another example. Individual participants (a human, animal) dies and disappears but the concept of genome continues to survive and actually gets stronger as individual members experience stressors that take out the weak and let the strong survive.

• Barbell strategy, a way to build antifragility. There are many ways to explain this strategy, but it boils down to playing majority of the time safe, and be very aggressive otherwise. NO MIDDLE GAME. Playing safe you are not exposing yourself to destructive events that could take you out, so to speak. At the same time, if you truly pick a smart but aggressive investment or activity, since it’s loss magnitude is small, even if all of it disappears – that’s just a small percentage lost. But if you hit “gold”, you benefit greatly. The key is finding an activity/investment that has such a great upside and whose downside is small. Seems obvious at first, but I think in real life we play mostly in the middle. Very little on the safe side, very little on the risky side and fat column in the middle. This thought is really nagging at me and making me reconsider many of my own activities and actions.

• Optionality, another way to build antifragility. When you have little or no options, you are limited in your actions and when you have no options, a catastrophic event can wipe you out. You don’t get better when Black Swans hit, you either suffer greatly, or survive. Options can enhance you ability to benefit from the Black Swan.

• Via Negativa. Another way to increase antifragility, as well as a way to look at life. Don’t try to add, but work hard to remove. When looking at a design of the systems, adding functionality adds complexity, which adds fragility. Simplify, remove it, and remove some more. A noble goal in any profession and in life. It’s something that is really hard to do as adding can be tempting and short-term gratifying. Also, rarely did anybody receives an award for not doing something. Bigger/complicated systems seem to hide failures underneath the surface and it eventually all comes out in a large (Black Swan) event that has catastrophic repercussions. Large governments, top-down as opposed to bottom-up, are inflexible, fragile, and susceptible to large crises. Think of how much infrastructure and layers of bureaucracy that exist within large governments and corporations. When you get an inside look, the picture is not pretty. According to the author, such setups are just a matter of time before they get hit with a Black Swan event that can wipe them out. At the very least many people suffer.

• Lindy effect. The longer the technology is around, the longer it will survive. Another way to spin it, don’t trust something that is new because by the mere fact that it is new, it has a really high probability not sticking around.

• Skin in the game. A large topic but it boils down to an idea that don’t listen/rely on somebody who is not impacted by whatever they are saying or asking you to do. A doctor that suggests you a procedure which he himself would never under go (e.g. risky back surgery), an investment advice from somebody that does not use it themselves. These appear to be obvious but are not obvious in real life. There are a ton of forecasters and prediction people that get things wrong all the time, their false forecasts or news being used in real life with negative consequences. Yet the forecaster suffers no consequences. That’s the reality of the modern world. We are too large, too big, we seek out commentators on anything and everything and then follow them without asking if that person has anything in it or just spewing nonsense for profit and moving on.

In general, the book praises the life of stoicism, small size, and simplicity, suggesting the reader looks at Mother Nature, the most antifragile thing that we know of, for clues on how to live and advance.

I love this book so much that I will buy a print copy to refer to from time to time.

As a side note, I found it fascinating to see how many people absolutely deplore the author and this book. I can see how the ideas can be unsettling, and the author’s style is rather rude. I actually like it, no sugar coating and straight to the point. If you are offended by it, move on. The message is simply not for you.

# Book review: The Wisdom of Insecurity

I don’t possess good enough writing skills to review such a book in detail.  Instead, I would like to link to Scott Young’s review. He does a much better job than I could and then, with Scott’s review being quite large, I would like to share a couple of my own thoughts below.

Would I recommend it? If your interests are starting to steer towards the philosophy of living in the present, Zen and Buddhism (those are not mentioned in the book directly but the philosophy is there), you should give this book a try. It’s relatively short and has some good ideas.

The book was written in the 1940s but very much applicable to today’s age. The main theme of the book is our search for security in the ever-changing world. In Watt’s view, such attempts are fruitless and are only spent by people who cling to a false idea of what life is all about.  To seek security in your life is to misunderstand life itself. Change, wars, successes, and failures are all part of life and trying to “fix” them in place is a losing fight. We use words as labels to try to define things we don’t understand or can’t control. Yet so much in life is not under our control.

One of my favorite sub-themes of the book is how we as humans fail to live in the present. We search for happiness, that always feels like a thing that will happen in the future. We define and come up with ideas of what happiness is based on our past experience. So we look towards future informed by the past and ignore the present.

The book also includes many discussions around the role of science and religion. In a way, to the author, the two are identical in that it is a human invention that tries to explain the world around us. Science uses scientific methods while religion assigns certain beliefs and urges its followers to adhere to them. Both trying to define the same thing while using a different language.

I am walking away from this book with a good reminder that nothing stays on forever, that change is part of life, without pain there would be no joy and vice versa, and the best we can do is appreciate the present moment we have while we are on this short adventure called life.

# Book review: The Mastery

Mastery – a guide to discovering the inner force and principles for achieving mastery in any field or activity. It does not dive into the specific areas or skill sets but instead distills a set of general principles that one must follow on their path to achieving mastery in a field or subject of their choice.

The book is very dense in the material it presents. You could unpack each chapter for hours and dive into them deeper with more books and materials. What helps for the book to stay clear on the message and follow along is the format it chose. It expresses the principles by looking at contemporary and historical figures that were highly influential and respected personas in music, business, and technology and weaves all principles in mini stories that are easy to isolate and dissect.

The common theme of the book is that we all posses the ability to be great. It is not about the talent; it is not about “born genius,” or mystical powers. Luck plays a great role in our lives and cannot be dismissed. But you have to be prepared to accept and use luck to turn into anything meaningful. You have to be ready to receive it before it can make an impact on you. Through it all, it is all about hard work and more work, tactical plans combined with an ability to be flexible with a capacity to learn from others and stay on course despite the challenges that the life will present you.

It all starts with the process. First, you need to know what your big goal is. What are you trying to achieve? What is that you are trying to become? It is a difficult thing to define, and you need to spend time thinking about this deeply. Sometimes we get lucky, and we just know in our hearts what we want to do. In that case, the big goal is already defined, otherwise work to set it.

Second follows an immense practice and learning of your field or subject of interest. Not superficial tutorial here and there but full immersion and intentional practice. We need to anticipate that once the initial excitement wears off, the difference will be our ability to stick around and continue to study, learn, and practice the field. Push hard, let go, relax, push hard, let go, relax, push hard, let go relax … a cycle that will get you working hard and at the same time keeping you re-energized for more. The key is that each time you learn something, more unknowns open up and you continue to dig deep to understand the field or whatever it is that you are trying to master. The practice must be deliberate, that is with a goal in mind, and each stage has to have a purpose behind it. It’s a challenging work, but the rewards can be great.

During this time you must be strong enough to deal with self-doubt and potential criticism of others. Accept it but don’t get discouraged. Another roadblock here could be people close to you that will advise you against going for something big and steer you towards fields or topics that have quick short term gain but usually are dead-end occupations or endevours that will leave you unsatisfied. You need to find the calling that attracts you, that also is useful to the world, and then go after it.

All of the hard work is for one goal: developing of intuition. The greater the mastery, the better the intuition. There is a feel that gets developed that hints to you what approach is right and what is wrong. The deep intuition also helps you develop the connections between the subjects and fields that deepen the learning AND fuel the discovery. This is why the people that are in the field for a long time can know right away what the issues are, can solve them fast, and move past the complicated concepts in their field. The intuition is guiding them along th way.

You can enlist the help of mentors to accelerate your development. If mentors are being available, the next best thing is books and learning materials. The key is to be tactical about what is being studied and the approach that is used. The mentors can be incredible accelerators of the development and are highly recommended to be seeked out. Unfortunately in this area I have no experience as I have only occassionally encountered somebody who I could call a mentor in some capacity. The book advices on how to find such a person, how to approach it, and how to work under them. Don’t expect the mentor to have you as their primary concern. Instead you have to be creating some sort of value for the mentor in exchange for the mentorship. At the end, don’t be surprised when your hard work is taken over or adapted by the mentor. It is OK, and can happen. Accept it and expect it. And then if you follow the right path you will outgrow the mentor and move past it. The key is to recognize when that time comes and move on.

Another section that was immensily helpful and I found very useful was the section on social intelligence. Along the way to mastery, you will work with other people and organizations. The ability to read and navigate social situations is as useful as knowledge itself. Knowledge in a vacuum is useless. It has to be presented to others, allowed for others to take it apart and criticize it. Beware that at the end, people only care about themselves so potential “political” meddling and situations can arise. I love the book’s advice on it: expect it, embrace it, and move away from it. Don’t play “political” games if the goal is the mastery and gaining the knowledge. Instead, be prepared for it in a way that it does not surprise you or blind side you and do your own thing.

Overall the book was a great read. I have a feeling that I will be coming back to it from time to time. Also, just picked up a few of other Greene’s books that have similar rave reviews as Mastery. Here is to more reading and learning!

# Book Review: The Richest Man in Babylon

Rating: 4 stars.

I wish I had read this book sooner.  I found it very useful, despite its unusual, parable-like, story style. The stories teach the reader how to achieve financial success. Even though the setting is ancient times, the advice conveyed is very practical and applies today as well.

When we think about “financial success,” we often think of immediate and big gains: stocks that multiple overnight, big payday, bonus, etc. The reality is quite different: financial success comes to those that work hard and smart, plan for it, and then take patient and steady approach.

The book, which was written in the 1920s by an American author, shares stories that are mostly about a wise man Arkad and how he achieved financial wellness.

• Save 10% of your income

• Spend less than you earn, after you put away that 10%

• Once you have a nice amount of money saved up, don’t keep it idle but instead make it work for you. i.e., invest it somewhere so it earns money.

• Invest it wisely, don’t invest in the areas you don’t understand without an expert guiding your way. Make sure you can get the principal back safely.

• Own the place you live in, i.e., don’t pay rent