Skip to main content

Mini Habits: Smaller Habits, Bigger Results

Mini Habits: Smaller Habits, Bigger Results
Stephen Guise  (Author)

ISBN-13: 978-1494882273

I’ve read quite a few self help books and while they always seem really good at the time, I’m not particularly good at following through. I guess I don’t necessarily have the willpower or the presence of mind to do what they recommend.

Mini Habits are different. They’re to small for failure.

There’s lots of repetition, which is slightly irritating until towards the end of the book the when the author hints as to why. As the author often says, you start with ridiculously small habits, the reoccuring examples are one pushup a day and writing 50 words a day, because it gets you into the habit, making it easier to do more. But you only have to achieve the small habit you set out to do. That’s what success looks like. So you can’t fail.

The book was recommended to me by my good friend Tom Bool. Soon after I started reading the book I started walking everyday right around the park. This took a good 30 minutes or more. Will power failed me some days. Now I make sure I walk for 15 minutes every day. Most days I do more as I walk to work. If I don’t walk to work I do 15 minutes or more in the park.

In addition to this my habits are drinking a pint of water a day and reading two pages of a book a day. Everyday I drink more than a pint of water and my incentive is that I don’t have a cup of tea until I’ve drunk my pint. I’m finding reading is enough reward in itself and I’m usually reading more than two pages a day. But if I haven’t found the time to read, I know I can read two pages just before bed.

I wish I’d read this book when I was still responsible for sales calls, because I could have done one a day which would be much easier than the 10 I’d often try and I could have been a success every day.

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...