Skip to main content

Gulp! (Book Review)


It could be that I'm the parent of a 7 1/2 year old boy. It could also be that the book has such great footnotes ( when I was in grad school working on a paper for a group project, one of my fellow students commented that I wrote great footnotes), but I found Mary Roach's book Gulp: Adventures on the Alimentary Canal to be very engaging and entertaining, as well as educational.

Gulp is a very approachable "top-to-bottom" tour through the human digestive system. Combining fact, history, some editorial commentary, and much humor you can't help but get pulled into this book, and even pull in those around you. At various points I found myself laughing out loud, leading my wife to comment that I,  have a lot more in common with our 7 year old, or at least that there is a certain timelessness to that sort of humor among certain demographics. The chapter on flatulence was particularly amusing, and was a great example of how Roach uses humor to help us learn about socially awkward topics, and to make details memorable.

One of the charms of this, and the other books of her's that I have read, is that she is adept at staying on the correct side of the boundary between humor that makes us comfortable (and makes facts memorable), and humor that is just awkward. She did a similarly good job with Stiff: The Curious Lives of Human Cadavers.

While this isn't the book to read for serious research, it is a good place to learn some fun facts about a subject that is not often discussed in polite company. With footnotes and references, you also have a good starting point in case you want to learn more. The only down side of reading the book is that you may find yourself laughing out loud or at least finding it hard to share a particularly amusing storing with whoever is sitting next to you while you are reading.

Gulp is a great example of how you can be entertained, informed and educated at the same time.

Gulp: Adventures on the Alimentary Canal

 

Comments

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…