Skip to main content

Review: Grit for Kids: 16 top steps for developing Grit, Passion, Willpower, and Perseverance in kids for self-confidence and a successful life

Because I had written reviews of Grit and other some education related books Lee David Daniels sent me a review copy of his short book Grit for Kids. While the title would have caught my eye, I’m not sure that I would have stumbled upon it otherwise, and I’m glad that the author brought it to my attention. While the book, by nature of its length, leaves out quite a bit about the concept and its application of Grit to parenting, it does provide a useful, actionable, introduction to concept.

Grit for Kids is a short, application focused short book that can provide some needed guidance to parents who are struggling with how to help their kids follow through in the face of challenges, or just boredom. It says a minimal amount about the theory of “grit” and dives into scenarios and techniques you can use to encourage the right combination of endurance and passion with children in your care. The examples are realistic and address children of a variety of ages from later elementary to high school.

The author captures the essential parts of grit, including the subtlety that gets lost in many interpretations which focus on "persistence" over all else. As Angela Duckworth describes the concept of “grit,” it also means understanding your limits. I would recommend reading Grit, but that is a larger time commitment, and this book might just fill a gap. It will give you ideas to get started, as it is easily readable during a couple of short blocks of idle time, like a subway or bus commute.

The book would be better if the author pointed to resources to go more deeply, and it is a bit simplistic. But if you are looking for a way to understand how to help your kids get on the road to being grittier, then this is worth a look if the price is right. But do follow up with the original book, or at least the TED talk.


Popular posts from this blog

Continuous Integration of Python Code with Unit Tests and Maven

My main development language is Java, but I also some work in Python for deployment and related tools. Being a big fan of unit testing I write unit tests in Python using PyUnit. Being a big fan of Maven and Continuous Integration, I really want the  Python unit tests to run as part of the build. I wanted to have a solution that met the following criteria:
Used commonly available pluginsKeep the maven structure of test and src files in the appropriate directories.Have the tests run in the test phase and fail the build when the tests fail.
The simplest approach I came up with to do this was to use the Exec Maven Plugin by adding the following configuration to your (python) project's POM.

<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <configuration> <executable>python</executable> <workingDirectory>src/test/python</workingDirect…

Displaying Build Numbers in Grails Apps

Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. In the Maven/Java world, this is straightforward. Or at least I know the idioms. I struggled with this a bit while working on a Grails app,  and wanted to share my solution. There may be other, better, solutions, but the ones I found approaches that didn't quite work they way that I'd hoped.

My requirements were:
To display a build number from my CI tool, where the number was passed in on the command line. In Bamboo, for example you might configure a grails build as
-Dbuild.number=${bamboo.buildNumber} warTo only change build artifacts and not any source files.To not misuse the app version, or change the names of any artifacts.To be simple and idiomatic.I realized that that Grails itself changes the application metadata (appl…

Motivation Visibility, and Unit Testing

I've always been interested in organizational patterns (such as those in Organizational Patterns of Agile Software Development). I've recently found myself thinking a lot about motivation. I'm now reading Drive: The Surprising Truth About What Motivates Us and just finished Rob Austin's book on performance measurement. Being the parent of a three year old, I'm finding more and more that "because I said so, and I'm right" isn't too effective at home. My interests in motivation are closely related to my interest in writing software effectively. Writing software is partially a technical problem about frameworks, coding, and the like, but the harder (and perhaps more interesting) problem is how to get a group of people working together towards a common goal. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do yo…