Words On Wednesday

A little while back, I was determined to win some stuffed penguins from a claw machine for my kids, but it took over a month to actually get the opportunity. Our church has a claw machine in the lobby near the entrance. They have different things in it, but the bulk of the contents are usually stuffed penguins wearing shirts with the church logo on them. Somewhere around the beginning of summer, I decided that the kids would like to have one. They both like penguins and I figured the money would be going to a good place. The first Sunday that I decided to look into it, I checked the machine to see what kinds of payment methods it accepted. Upon inspection, I noticed that it took coins and bills, but no credit card payment. Fair enough, that’s pretty standard. Credit card payments usually have a transaction fee associated and the readers are often finicky. I wasn’t mad. I took a look in the truck for cash, but I couldn’t find any. That week, I looked in the truck again and discovered th

For the first time in the history of Words on Wednesday book reports, I’m covering a cookbook. I like to cook and I like to read. You would logically think that would mean I have a ton of cookbooks, but I really don’t. Usually, I either just get individual recipes directly from the internet or I go rogue and come up with my own stuff. We have a few cookbooks, but I use them more for inspiration than actual sources of recipes that I’ll cook directly “by the book” (pun intended). With “Big Little Recipes,” I actually first encountered the book through a social media post about a particular recipe in the book. In particular, the author highlighted the 2-ingredient sour cream dressing that is simultaneously easy and delicious. Easy and delicious are great individually, but they’re even better together. I was intrigued. I didn’t particularly want to buy a cookbook from a single recipe. Although I didn’t anticipate this book being available at my local library, I had to check it out. SURE EN

Work in any industry is often broken down to man-hours, the expected amount of work that an average person can finish in an uninterrupted hour. While that’s great for planning and budgeting purposes, I think it’s a terrible measure that gives inaccurate estimates at best and coerces people to work absurd amounts of unpaid hours at worst. And much like Fred Brooks probably suggested in 1975 (I’ve never actually read the book that I based this title on), there are several reasons why basing expectations on the work capability of some theoretical person in some theoretical hour is unhelpful and often harmful. The first problem with man-hour estimates is the amount of work. Who is this average based on? In the software engineering industry, there are vast differences in experience, specification, and familiarity with different products. If you ask me to build something in a language I’ve never written for an industry that I have no exposure to, it’s going to take a while. A recent code sch