This Sunday I decided to take a different approach to my morning. I didn’t turn on my computer as soon as I had my shower. I did not check my notifications (interestingly, I had none of note). I embraced what I felt like I wanted to do. I am in a bit of a creative rut with my programming. I like to write code but I do not like to write code that has no purpose. I feel like I am wasting time when I am working on a software project that has no goal.
Last week, I thought about creating a news aggregator for coffee. I decided against pursuing this idea. I’ve already built a news aggregator in the past. I know, roughly, what I need to do to build a news aggregator. It’s a fine idea. I read a lot about coffee online and I would like to share what I am reading with the world. I feel like a news aggregator is yet another project for me to worry about. Would I even be using it in three months?
I am starting to try new ways of measuring my productivity. I don’t use any particular measure. I have an internal compass. I know, on any given day, whether I have accomplished as much as I would like to. I don’t like to force myself into too many routines. There is an old saying about repeating routines. If you do the same thing over again and expect a different result, you are foolish. I cannot remember the exact wording.
You’ll notice this blog post is different to all of my others. I’m trying a new approach. I am sharing what I am thinking about instead of a technical problem that I am trying to solve. There is plenty of time for me to talk about software projects but only when I am working on one. I don’t want to write something that I do not believe in. That’s why I am trying a new approach.
Enough of the obvious self-justification of my approach for this morning. I took a morning away. I woke up and read almost two sections of The World Atlas of Coffee, a book by James Hoffman. My first impressions of James Hoffman were that he was more of a “personality” than anything else. I know that coffee is a creative industry and a lot of people have “presences” but I was concerned that I’d end up chasing trends more than learning about coffee. I watched a few of his YouTube videos last week and I was impressed. I like his style of writing.
I advanced toward the end of the second section, From Bean to Cup. I do not often read books and so I am unsure how I should share my thoughts. Perhaps I should write a book review? That would be a good way to summarize what I have taken away from the book. For now, I’d say that it is an excellent read. I am learning a lot about all the different brewing methods. I’m particularly interested in the siphon. I probably could not brew using a siphon at my current level of knowledge but it looks like a cool method of making a cup of coffee.
I did learn that there are two main methods of processing coffee: wet and dry. In the wet method, water is used to remove the mucilege (the stuff around the coffee beans) as soon as the beans are picked. Then, the coffee is dried. In the dry method, coffee is dried on large beds that are exposed to the sun. Then, the excess is washed off. I may be missing crucial details. I’m still learning. That’s why I picked up this book: I am hoping to widen my knowledge of coffee.
That was my morning. The morning is not even over yet. I find that it’s easier to write about things I have done. I usually write about programming. I could use this approach again. I could write about non-tech parts of my day. I drew a picture. Would readers be interested in reading about that? Well, that’s not the right question. I should be asking whether I want to write about my day. I think I do.