Book: The Inner Game

The actual title of the book that I just read is called "The Inner Game of Tennis", but this post is not about tennis.

This was a great read, and you should read this book if you play sports and have ever wondered why you play good one day and bad the next. This book may help you have a more consistent and higher gameplay.

I wrote a whole bunch of notes as I read, and you can read them on GitHub.

If it's too much trouble to click a link, then here's the TLDR (Too Long; Didn't Read) that shares just a few of the biggest points:

• There is an inner game and outer game. There are already many great resources on the outer game.
• During practice, analyze your movements (methods includes "feeling" it, mirrors, video playback) and don't try to force any change. During game play, just let it happen naturally; trust yourself.
• Experiment with many different playing styles. The "right" style may be different for different people.
• You still may need some good outer game practice in order to gain more from these inner game tips.
• If you dislike competition, then you have the wrong idea about it.
• When playing, if you have any anxieties or frustrations, then you aren't a player of the inner game.

And, if you have already read this book or any of the other "Inner Game" books, then I'd be happy to hear your biggest take-aways.

~ Danial Goodwin ~

---

My Android Apps | My Windows Phone Apps | My Developer Blog

Working Title, "Basically, Android Expained"

I am an Android developer. I have been one for a few years now. In that time, I've had the pleasure of helping many people with technical questions. I believe one of my specialties is being able to explain complicated concepts in simple, laymans terms.

Over the years, I was bound to give repeat answers eventually. So, in order to keep myself more efficient, I will start adding all of my layman explanations to a wiki, which I will eventually probably turn into some sort of ebook.

The book will be titled, "Basically, Android Explained". I still have a few working ideas for a tagline.

I chose to title the book this way because almost all my explanations start off with "Basically, ...". This single word is very important to my explanations because it signifies that what follows is NOT everything explained. It is just the easiest explanation for a non-developer or a new developer.

I'm not sure of the entire structure that I want to use for my definitions, but one way is to have the first sentence be "Basically, ...", then the following sentence would be a more technical definition, then after that will be the reasons for using it.

For good measure, here's an except:

KeyStore: (also referred to as a Java keystore or keystore file) A security certificate used for authorization. Basically, an app's signature. It proves that the app was made by a certain developer. This is a precautionary security measure that prevents malicious apps from replacing another app."

That was just a quick rough draft, I have a few more ways to explain this concept. Feedback always welcomed.

~ Danial Goodwin ~

Title: Basically, Android Explained
Description: Where advanced technical concepts are abbreviated to quick/light readings.

---

My Android Apps | My Windows Phone Apps | My Developer Blog

Things People Should Know: Parkinson's Law Of Triviality

(For people that have to work in groups or have a "project manager")

Also sometimes referred to as the "Bike Shed Problem" or "bikeshedding".

This is the newest phenomenon that I have added to my great list of Things People Should Know. It is not a new concept (first mentioned in 1957) and I have known about it for awhile, but recently I have been noticing it more.

What is the Bike Shed Problem? Let me provide an example: (From Parkinson's book, as quoted in Wikipedia)

In the third chapter, "High Finance, or the Point of Vanishing Interest", Parkinson writes about a finance committee meeting with a three-item agenda.

The first is the signing of a £10 million contract to build a reactor, the second a proposal to build a £350 bicycle shed for the clerical staff, and the third proposes £21 a year to supply refreshments for the Joint Welfare Committee. 

The £10 million number is too big and too technical, and it passes in two minutes and a half.
The bicycle shed is a subject understood by the board, and the amount within their life experience, so committee member Mr. Softleigh says that an aluminium roof is too expensive and they should use asbestos. Mr. Holdfast wants galvanized iron. Mr. Daring questions the need for the shed at all. Mr. Holdfast disagrees. 

Parkinson then writes: "The debate is fairly launched. A sum of £350 is well within everybody's comprehension. Everyone can visualize a bicycle shed. Discussion goes on, therefore, for forty-five minutes, with the possible result of saving some £50. Members at length sit back with a feeling of accomplishment." 

Parkinson then described the third agenda item, writing: "There may be members of the committee who might fail to distinguish between asbestos and galvanized iron, but every man there knows about coffee – what it is, how it should be made, where it should be bought – and whether indeed it should be bought at all. This item on the agenda will occupy the members for an hour and a quarter, and they will end by asking the Secretary to procure further information, leaving the matter to be decided at the next meeting."

So, now that you know about Parkinson's Law Of Triviality, hopefully you will be able to better recognize when others do it and when you do it yourself. It is a natural thing to want to give input when you can, but don't let it become a hindrance to getting the most important things done.

If you know ultimately that a feature really doesn't matter, then make sure you work on the important stuff first. Also, be aware, don't always think you know better than others.

More Reading:
- Coding Horror
- Wikipedia

~ Simply Advanced ~

---

My Android Apps | My Windows Phone Apps | My Developer Blog

The Math Instinct

Why You're A Mathematical Genius (Along with lobsters, birds, cats, and dogs) by Keith Devlin

Interesting math book that I've started reading. It begins with describing how babies younger than a two years after being born recognize numbers and can do simple mathematical calculations. Also apparently many animals and plants do natural mathematics that compare to humans' calculus, trignometry, geometry, et cetera...

Anonsage