Posts

Well, it's the twelfth month of the year, which means this is my twelfth reading log blog post. I did not hit 40 books this year, but I did manage to finish 29, so nearly 75% completion. I didn't really keep track last year, so I don't know how much more I read, but I did read much, much more than 2023.

In December, I read:

Revelation Space - Alastair Reynolds

It took me two tries to read this one. I will not be continuing in the series. The first third of the book felt confusing, with different characters in different times dropped right into an entire universe that doesn't get a whole lot of explanation later in the book. Humanity has spread to new stars and has split into different factions with their own norms and histories. There are also interactions with alien species, but again, lacking any connection to the plot unfolding.

Several of the characters are there without much reason and several don't reveal any motivations for their actions. The second third was better than the first, but the ending felt flat. The conflict plays out and some questions are answered, but I'm not convinced the book needed over 500 pages to end where it did.

Accidental Astronomy - Chris Linott

This is brand new and happened to be on the "New Nonfiction" shelf at the library last time I went. I can't really focus on nonfiction during the school year so I try to cram some learning in during breaks.

A wonderfully written, easy read about some of the weird discoveries in astronomy made completely by accident. Linott's writing style is casual with enough technical detail balanced out with clear narrative and witty footnotes on almost every page. I enjoyed this book immensely.

As we roll into January, I will start my count again. Here's to the 2025 reading log!

All of my reading is on LibraryThing if you want to take a look at everything I read in one place.

My hobby project is a self-hosted grading/feedback platform for students to track progress on learning standards. I call it OutcomeMaps, mainly because standardmaps.com was already taken, and it is probably the second most-used site on my machine each day.

Everything we do in chemistry is linked to a speciifc learning outcome - usually a skill based on theory (describe the structure of the atom) or on computation (calculate the mass of product expected from these inputs). Every unit has two or three defined, each unit building on the previous, and students are graded on their proficiency on these standards. The problem is that I didn't have a great way to track progress on their learning.

So, I set out to build a little frontend for a database. It's simple in the sense that students are essentially read-only users and they can see a catalog of all feedback they've received through the year and a dashboard of their progress on any given standard. As the teacher, I can create/edit/score anything, but the main interaction layer is feedback on the skills.

The key is that it helps me make decisions and helps students see their opportunities for improvement. I don't think there's one way to quantify "proficient" but this system has helped me collect data which can then be used for plan for instruction and address emerging needs.

One thing I changed this year is to give binary scores to students. I started thinking about this switch back in March, mainly becuase my grading scheme at the time had areas of uncertainty in the scale that I wanted to eliminate. On paper, this turned into a 0-1-2 scale: no submission, improving, demonstrated. Students have been trained to glance at the number but, more importantly, pay attention to the written feedback. Based loosely on the single-point rubric, it does a better job of getting students to think about their thinking and not just about task completion.

On the web, I turn that into a "check or x" - the UI doesn't actually show their score, just a checkmark or an "x" to note proficiency on that thing. The feedback is displayed right alongside each assignment's result so they can identify their own strengths and areas of improvements for each standard. The goal is to reach a check by the time the unit test rolls around.

This year, I built out an admin panel with some simple charts that will help me - at a glance - look for patterns in each course.

At this point, I was calculating proficiency on the fly with each request because it was just one roster at a time (~25 students per class). This chart needed to generate three objets with data for each standard, so I was looping over each student multiple times. The chart took several seconds to load, which was less than ideal.

I did some work on the database to create a new association table that would record when a student was proficient - generally after taking a test - and I could store that record permanently. I also wrote in a method to override proficiency manually - the use case being that a student might come after school and do some one-on-one work that wasn't on a specific assignment. I can store that proficiency with a click instead of creating a new assignment for that one thing.

This let me query all of those records at once and cut down the load time by orders of magnitude. It also allowed me to set up per-standard comparison charts in the admin panel:

Now, as we're in the unit, I can look at the progress for each class on one screen. This used to be manual - I would look class by class and think over next steps. Now, I can reflect more on what I do differently from period to period and how that translates into success on the skills.

This year pushed me in terms of my coding ability. I've never been comfortable with database joins, but I'm using them all over the place now. I also have a better handle on how to set up models to get the data I want. I'm also coming up with ideas about how to help shepherd students through their own reflections on learning. One goal for this next year is to introduce tagging on standards ("theory" vs "computation", for example) which can help target even more interventions and study strategies for students.

Beyond that, I'm more strategic about my CSS and template structures. I've done a lot of maintenance work to clean up templates and I'm getting ready to tackle a full CSS cleanup (it's a hot steamy mess right now). It's by far my most long-lived project in terms of raw code written to do a thing (as opposed to raw words here) and I'm really proud of how far it has come from my really bad first couple of versions.

Year 15 in teaching, another post on grading. I'm still using standards based grading and I'm still thinking (overthinking?) how to represent student progress on each standard.

I've gone through several scoring style changes. Most recently, I've switched from my old four-point scale to a two-point representation, mostly based on an old post from Kelly O'Shea on her SBG system. Students are given a 0-1-2 score on any skill we work on in class. A 2 means they've demonstrated the skill successfully. A 1 means they've got some work to do and a 0 is reserved for "No evidence." It's simplified my scoring and I think students have a better overall understanding of what "showing proficiency" means in practice.

My deeper struggle is how to represent the final result to students. Each of the feedbacks they get through a unit points them to in-progress fixes. In other words, small errors in their processes get caught and they're able to fix those things on the next attempt. They can see the linear growth from 1's on assignments to 2's. But what about at the end of the unit? How is all of this wrapped up?

Like Kelly, I've decided that tests are the "hard limit" check. If it's not perfect on the test, then it does not show proficiency. All semester, I've been putting that standard score is more or less based on the test attempt. So, even if they've been proficient up until that point, mistakes on a test will cause me to hold off putting that last binary yes/no on the skill into the book as completed.

Kelly's rationale is that the test should be their best true demonstration of understanding, and I agree with that mindset. It's a controlled environment in which they're asked to do the thing correctly. This requirement also helps reinforce the fact that copying and/or otherewise doing unauthentic work leading up to tests is a waste of time for the student becuase the still have to be able to perform the skill at the end of the day.

To help collect evidence over time, I've got a little web app students can use to see their progress on standards. All feedback goes on their papers but it also goes into this app so they can watch their progress throughout the unit. A student may be showing proficiency on a skill throughout the practice work only to be hit with a "not proficient" based on that test. I'm trying to reconcile that story in my mind so that it makes the most sense for them.

The message I need students to really internalize is that learning is a process. Tests are a way for me, the teacher resposible for fostering and reporting their growth in the content, to check that growth reliably and with validity. Reporting their standard proficiency based on the test is the best true check. Their growth up until that point is their indicator for what to fix leading into that final check in the normal flow of the class.

I finished two books in November, which is on par with the rest of the year. Here's what I read:

Contact - Carl Sagan

I picked this up because I really love the movie adaptation, but had never read the novel. The science is much more thick in the book, so some parts were tough to decipher. The plot is also much more intricate (as books usually are), but in good ways. Ellie is hyper-driven to be successful and to stand out in every way. She struggled to really feel like part of the team. In theory, she changed as a result of the experience, but it doesn't come across much in the end. For me, I think this is a rare case of liking the movie over the book.

The Warden and the Wolf King - Andrew Peterson

The ending of the four-part series is one of the best I've read. This book, more than any other (or as far as I can remember, at least) makes me incredibly emotional and I wept (again) in the final chapters. The themes of hope and redemption are overwhelming as the family faces their biggest challenges and have to decide how to respond.

I'm plowing into Revelation Space right now, and I'm hoping to finish it for the December roundup. It's my second time starting it (gave up the first time) but now I think I'm following the story a little better, so I'll probably finish it.

More books and my meager reviews are on LibaryThing. I've had some friends ask to move back to Goodreads and I might make the jump back next year. I miss the social aspect that I had going over there and I might just swallow my distaste for the ads to get that communal reading thing going again.

Only one book read this month. School is pretty busy, so I'm working many evenings on grades and other teaching related tasks. I'm able to read a few nights a week before I go to sleep.

The Book of M - Peng Shepherd

I picked this up after I finished reading The Cartographers, which I read in September.

This book took a long time to develop and felt like the middle was really dragged out. The story is split between several groups of people all living in the same dystopian world. Their stories converge and lead to an ending that left me feeling really unsettled, but satisfied. The premise of the book was very difficult to suspend disbelief for and I think that was its biggest sticking point keeping me from really enjoying it.

This is my 25th book of the year, so I will definitely not be finishing 40, but I'm okay with that. Onward!

I had a small coding itch today after giving the PSAT, so I decided to finally add back in an easy way to share posts from the blog. ShareOpenly is a service which allows anyone to share to any of the federated platforms from any other place. There's no account and no login needed to use the link, but you do need an account on the fediverse (Mastodon, Threads, etc) in order for the link to work.

I used to worry about how much people shared what I wrote, especially when I was on Twitter a little too much. Those days are gone, but this was an easy way to touch a little bit of template code today and make things a little easier.

In addition to adding the button at the bottom of each post when it's generated, I cleaned up a little bit of CSS and added some headings to my sidebar containers. There's still fixing I want to do to the theme, but that'll come later with more time to test the changes. In particular, I want to take what I'm learning from Every Layout and apply it here so I have a more flexible, fully-responsive layout.

Onward.

The point of a blog is to catalog writing. I've switched platforms a couple of times and I decided it was time to get archives front and center again.

With this small update, there's now a link to posts by year on the right (you might need to do a refresh to get the addition). This is an easy way to jump from one spot to another and will help me wander back through old timey Brian.

I still need to get search working again, but this was a nice little task for this evening.

Warning: this post is about raising and processing (ie, butchering) chickens. There are no graphic details, but it does recognize that meat comes from animals which are living up until harvest day.

For the last six years, we have raised and processed our own chickens to feed our families. Every July, we receive chicks from the hatchery which will spend the summer on the pasture in the chicken schooner while they grow and leave their droppings on the grass. It's a small way to get nutrients back into the ground and to provide organic, grass-raised chicken for our family.

Our family raises Rudd Ranger chickens, which are hardy birds that do well fully outdoors. They grow to full size in 12 weeks, so we're butchering after the hottest part of the summer, but before it gets too cold. This particular breed grows slower than other meat breeds, but they're less prone to disease and they don't balloon up and run into joint issues and disease like the Cornish Cross, especially being raised outdoors.

The schooner is moved every day during the growing season so they're always on fresh grass, eating insects, and putting nitrogen back into the ground. This particular pasture needs the nutrients and we can tell the strategy is working because aerial photos of the pasture clearly show where we've had them over the last several summers. The long dark green swoop in the picture is last season's schooner path. The grass is thriving in these areas which is good for the other critters, including the cows when they're grazing out here.

Butcher day is bittersweet. We've taken care of these animals for three months. They're not pets and it's definitely work to make sure they're healthy. At the same time, we cannot dissociate ourselves from the fact that we are living today because something else died. We start early in the morning and work through until every animal has been processed and is either bagged whole in the freezer or is cooling overnight in the chiller.

The second day of work is spent quartering chickens to package as thighs, breasts, and wings. With three families buying in this year, we each ended with about 65 chickens split between whole and pieced up packages.

This is, by far, one of our most hands-on tasks on the farm. We all contribute energy through the growing season, splitting the brooding, feeding, and raising evenly. This is the day when we all put in sweat equity to provide a large portion of our annual meat diets. There is a lot of laughing while we work, but there are also serious moments. When the first animal is started, it's quiet. We're thankful that we have the opportunity to raise our own food. We also understand - and teach out kids - that taking a life is serious business. We don't take butchering lightly and we make sure our kids see the sanctity of the task.

The same is true for the last chicken. After several hours of doing some dirty work, we're glad when the last one is finished. We can sit down and look at the fruits of our labor. It's a very tangible process.

It also really feels like the end of summer. Chicken weekend is a marker for the end of the growing season - gardens are taken out already and this is one of the last jobs to do while we prep for winter. Every year, it's a time for me to reflect on the weeks of work to prepare for this day and I always walk away feeling more connected to this place.

Not much reading again this month. I gave up on The Aleppo Codex because I didn't have the brainpower to follow all of the names and dates. The premise is interesting, but I can't dedicate reading time to something so intense during the school year. Maybe I'll revisit it during winter break.

I did finish two books.

The Monster in the Hollows - Andrew Peterson

This is the third book in the Wingfeather series that I've been reading aloud to my middle two girls. In this installation, it seems the Wingfeathers have finally found haven in the Green Hollows, but the entire family needs to adjust to the new culture. This is made doubly difficult given the challenges they've overcome and the scars they bear as a result. It asks everyone - including the reader - to consider their own monsters.

The Cartographers - Peng Shepherd

This was on a recommended book list when I searched "mystery" in the Libby app through our library. The premise was interesting and I was happy with the mystery that evolved. Then, it turned into a flashback series for the main plot and had a lot of holes in the end...I was left with a lot of questions about why some things happened one way, but similar situations later had different rules applied. I ended up being disappointed.

These were my 23rd and 24th book of the year since January. I'm probably not going to make my goal of 40, and I've made peace with that. Until next time...

I'm not sure "autumnish" is a word, or if it is a word, if it is spelled correctly, but I do what I want here.

After an absurdly hot first three-quarters of September, we're finally enjoying the southwest Michigan start of autumn we moved here to enjoy. The days are warm and the nights are cool. Rain comes and goes each week and there is still a lot of life around us, but just with less gusto. Things are winding down both cultivated and grown as well as the life all around us.

We kicked off the weekend with a fantastic apple crisp made with seconds (ie, not good enough for the expensive bin) from the local apple stand. The couple who run the farm know their stuff and recommend apples based on what you want to do with them. Snacker that isn't too and brings some sour? Cortland. Jonathan apples for the kids becuase they pack that sugar punch the kids just go bonkers for. If you enjoy a crisp every now and then, throw in some cranberries (you can find whole cranberries in stores this time of year) and leave a comment later.

Saturday was split between harvesting our honey from the hives and getting the new batch of chickens acquainted with the old ladies. We modified our coop so the new chicks have some outdoor space where the OG hens can see them and get used to some new chickens in the flock. They'll stay separated for a few weeks until the new ones are ready to join the main group.

We landed on about 130 pounds of packaged honey this fall. This is our family's crop, so we don't really package it for selling like we do our spring crop. That said, we can't eat 120 pounds of honey ourselves. We'll keep about 70 which includes enough for us to use all year, some to trade with family for maple syrup in March, and some for gifts for neighbors, collegues, and the various other people we interact with on the regular.

The last thing on our list is to finish breaking down this year's garden. All of the stakes and plant supports are out - it's time to mow down all the growth and cover it with tarps so the carbon can get absorbed back into the ground for next year's garden. We're going all-in on a production cut flower system to go with the produce and honey on the farm, so we'll spend the winter planning out the expansion and all the infrastructure that will come along.

The season's change is encouraging. We've worked hard and taken advantage of our growing season and now, with the main part behind us, we can enjoy a few more chores knowing that we did good work and can take a rest.

Put the coffee back on and grab a sweater because it's time to finally slow down a little.

We had our first rainy day in several weeks today. As such, our kids were a little on the bored side and needed some help from me on what they could do.

Some of my ideas were:

• Get out the paint sets
• Read a book
• Read a book to your younger sister/brother
• Do a puzzle
• Play with legos
• Sit outside and listen to the rain.
• Sit outside and listen to the sounds of the insects.
• Watch the dog try to scratch her ear, but not be quite able to reach just the right spot and then deal with the frustration of not being able to scratch her ear.
• Scratch the dog's ear when she comes over to you looking for relief from the agony.
• Listen to the sound of your hair growing slowly out of your head, marvelling at the machinery of the human body which produces and folds proteins to make hair in the first place.
• Consider the rain falling off the roof, pulled inexorably by gravity from the clouds down, down, down in the ground; flowing always down into the deep, where it will eventually gather with the other billions of drops into deep, dark wells to be drawn out again someday.
• Consider the twitching of the leaves on the trees, hanging on by the end of the summer sunlight but becoming more frail as the light wanes and the darkness returns, their strength tapped by a season of growth standing up to the start of the autumn wet season before falling and joining the stuff of the earth yet again, carbon returned to the ground.

They ended up jumping on the trampoline in the rain.

August was the final month of summer break, so I managed to sneak a couple books in before school started up.

North! Or Be Eaten - Andrew Peterson

Book two in the Wingfeather Saga, I read this aloud over several weeks to the middle girls before bed. The Wingfeather family is on the run from the Fangs and have to make their way through Dugtown, which is full of more danger than just Fangs. This is a more bleak novel, but has glimmers of hope shining light into the darkness. It's a great read for all levels.

The Dispossessed - Ursula K. Le Guin

A story contrasting two opposing societies separated by space and ideology. Shevek is caught in the middle, trying to sort out how the two can reconcile. There is a hint of advanced technology in the book, which is why I picked it up, but the theory behind the technology plays a bigger role than the device itself.

World War Z - Max Brooks

I'm not a fan of zombie culture at all. I find that I get really depressed (mostly because the content is depressing) and the lack of hope is more of a distraction than a plot point characters have to overcome. Brooks does a good job of balancing the crisis moments with glimpses of hope. Rather than focusing on the pandemic, the book does a good job of blending government, media, and societal conflict into the narrative giving a global perspective of the human species and not just a core group of survivors like most others in the genre. Because the book is an "oral history," there isn't a real protagonist to follow. There are a lot of different locations and names, some of which return at different points, but you don't notice right away because of how much it jumps around.

This is my second time through this book and I picked it up mainly because I caught the tail end of the movie on TV one night. (The movie was not good.)

Devolution: A Firsthand Account of the Mount Rainier Sasquatch Massacre - Max Brooks

I picked this up after a re-read of World War Z on a whim. The reporting/oral history was done well in WWZ, but this was a little too hard of a try. The detail in the main character's journal was way too high and far too specific to be absorbed. Brooks still weaved in research and other commentary through character interviews, but I think it would have been a more enjoyable read for me if it had just been in a novel format. There wasn't quite enough development for several characters and they ended up just being bodies for the climax.

This year, I started a new web programming course for high school students. We're focusing on the web because it's where my experience is and because we can do most of it on Chromebooks, which is what students are already eqipped with.

I had high hopes of spending two weeks (ha!) on the basics of the technology of the Internet. We started with vocab like "protocol," "client," and "server" before have some brief discussions about headers in requests and responses. I'm not doing any server-side work in this course, so we're not diving too deep into that protocol other than that there is a protocol dictating these interactions.

We moved into HTML pretty quickly and I'm starting to develop some protocols for distributing and collecting source code. I haven't introduced any version control, so I needed a way to have students download all source files effeciently. I ended up creating a repo with the following structure:

text . └── web-programming/ ├── html/ │ ├── exam/ │ │ ├── requirements.md │ │ └── index.html │ ├── ex01/ │ │ ├── introduction.md │ │ └── template.html │ ├── ex02 │ └── ... └── css/ ├── exam ├── ex01 └── ...

Each exercise is built to focus on a core concept. I have a markdown document with some reading and then the scope and instructions for the assignment. Sometimes, the assignment template has some of the HTML (or whatever) already written and students are editing. Other times, it is just blank boilerplate for an html document that they begin on their own.

I end up creating a .zip archive of each exercise that the students download through Google Classroom. Students complete the exercise and then submit their finished HTML to the Google Classroom assignment.

I looked into using Github Classroom to assign templates for students, but the template repos have to be standalone. In other words, I can't assign a single directory out of the web-programming root directory - I can only assign html/ex01 if it is its own repo. That means students would have dozens of template repos to manage by the end of the year and I'm not sure I want to do that. I'm also not sure I want to continue uploading and downloading template zips.

We've also downloaded the VS Code PWA to use as a text editor. I'm teaching some productivity tips along the way and I want them in the habit of working with the tools. I'll keep introducing helpful tools alongside the exercises so they've got context for why you'd want to use an editor in the first place. There was a lot of frustration in one of the first assignments (manually typing HTML tags around content) when I showed them the wrap with abbreviation shortcut. We'll continue identifying tasks we do frequently and looking up faster way to accomplish those tasks.

In the long run, I'm hitting a groove. This is a new class for me and for the school, so there is no expectation for what a "successful" sequence looks like. I think I'm going to continue refining the code distribution workflow to make life easier on myself while I prep activities and templates. I think as we build technical skill, we'll move to something a little more automated.

I came across a post from Kev Quirk this morning about Mastodon potentially removing the local timeline which linked to a different post by R Scott Jones, who wishes you could post to your local timeline only.

First, I never look at the global timeline. I'm surprised that there is debate about whether or not to include the local timeline in official apps. The entire point of decentralized servers is that you can join communities of interest and not have to see the main feed. If the core Mastodon project got rid of local timelines, I would have to make a hard choice about to interact moving forward.

That said, I hadn't considered local timelines only. I look at the local timeline a lot and generally don't follow people from Fosstodon on my account precisely because of this. I like the idea of being able to post to my local network exclusively and it made me wonder if I'm really in the best instance. I do work with open source projects and I have some toy stuff written of my own, but I'm not so into the nitty gritty that I can even follow a lot of what others on the instance talk about. It doesn't mean I can't learn, but it's definitely not my wheelhouse.

Is it better to silo off those interests? Or are small generalist instances the better approach? My guess is that it's "both/and" rather than "either/or," but it's made me think more about the ways in which we interact in these spaces moving forward.

And please don't nuke the local timeline.

I grew up visiting the central Adirondak Mountains with my family. A family friend had a cabin that we would visit at least once each year for a vacation. We didn't have much money and this was an affordable way to get out of our house on a trip.

My last visit was more than 15 years ago. My wife (before we were married) made a 12 hour Amtrak trip from Indiana to Utica, NY where we picked her up and then drove the last hour and a half to the house. Since then, we moved overseas and back, bought a house, had kids, built a house, and settled into midwest life. This year, my brother took the initiative get our schedules worked out to make a trip back to the house together.

If you've never been to the region, it's the largest publicly protected area in the lower 48, but it is neither a national or a state park. There is private and public land intermixed which means there is a lot of space to both stay and explore.

The house is just past Long Lake, the nearest town. Long Lake itself is unique because...well...it's really long. It's the closest town to the house and, as a kid, was the last landmark before we made it to "The Mountains." We didn't spend much time there on this trip but I enjoyed driving through with our kids and then making one grocery run back to the small store right on the shore. Most towns along the way are small, but they maintain their own distinctive vibe. I'm a particular fan of Long Lake's because they have great mugs and an even better logo.

The house is on a smaller lake just up the road: Lake Eaton. We spent time in the canoe and on the paddle boat, enjoying the silky smooth water and listening to loon calls echoing off of Owl's Head Mountain to the southeast. We took several hikes up local mountains and even completed the Tupper Lake Hiking Triad with the older girls. It was a proud dad moment when we made it to the summit of that last peak.

This house has a very special place in my heart. This trip was punctuated by the probabilty that it was our last trip to this particular house. We're not in close contact with the owners any more...this trip worked out because of a funeral gathering back in New York earlier in the year and my brother floated the idea. While I love this house and the Adirondacks in general, it helped my wife and I solidify our resolve to take our kids to new places as much as we can. We took our first family camping trip back in 2017 to Wilderness State Park and then a big adventure to Cumberland Island National Seashore in 2023. We're looking forward to our next adventures.

More books read this month, which felt good. I'm a little bit closer to being back on track to finishing my goal of 40 this year.

Dune: Messiah - Frank Herbert

This was a difficult book. Much more of the story was internal - characters thinking about time and its effects on their own particular plot. I felt confused frequently and wondered how everything came together. The end was satisfying with the resolution making sense, though a lot was relegated to characters just talking about what happened to others who were mostly absent for the last third of the book.

Working in Public: The Making and Maintenance of Open Source Software - Nadia Eghbal

This was a great look at open source from a philosophical and practical perspective. I appreciated the distinctions made between the product - the code - and the people behind the code. I got it thinking that it would be a book I could use in a new course I'm teaching this year, but I don't think it really applies. Maybe some snippets here and there, but this is much more focused on libraries rather than products.

The Handmaid's Tale - Margaret Atwood

I picked this up not really knowing what to expect. This was an incredibly dark and horrifying look at the extreme ends of patterns which are clearly visible today.

As always, I log books as I finish on LibraryThing.

We're about halfway through 2024 and I haven't blogged in a while, so here's a simple check in on the goals I set at the start of the year, particularly the ones that are still in progress:

• Read 40 books: I've officially finished 16 books so far this year. I'm behind schedule, so there's still a chance to get to 40, but I need to make more time to read. My progress is on LibraryThing as well as on monthly posts here.
• Add blog comments: I did this back in January. Say hi!
• Cut phone use: Frankly, I'm failing miserably at this one. I'm setting more physical boundaries for myself. I'm also going to be asking my wife to help out by putting my phone away while we're at home and there are things to be done. Hopefully the barrier of having to ask for it will help me not reach for it.
• Ride my bike 150 miles: This is probably what I'm most proud of - I've ridden well over the 150 mile goal and I'm not slowing down. I've ridden 191 miles so far this year and I'm making progress in both length and pace of my rides. I've moved from OpenTracks to Strava, so feel free to connect with me there.
• Get two new courses approved: Both were approved this spring and both are full for next semester! I'll be teaching an advanced chemistry class as well as a web programming class for the first time. I've started some basic outlines, but I need to buckle down before the start of school to make sure I start strong in both.

Halfway through and I'm feeling pretty good.

I actually read some books this month. School finished a couple of weeks ago and I was able to devote more leisure time to finishing some books. All three were repeats this month, but they're some old favorites.

Dune - Frank Herbert

I went to see Dune Part 2 in May and that prompted me to re-read the book. It's not my favorite brand of science fiction, particularly the prescience stuff that really ramps up at the end. I found it hard to understand some of the prose describing Paul's spice dreams. The ending was also much more abrupt than I remember it being. I started Dune: Messiah right after finishing and I'm curious to see if a part three of the movie series gets made and how they tie the stories togther.

Out of the Silent Planet - C.S. Lewis

This is an old favorite and either my second or third time through the book in the last ten years. This time I listened to it while we drove from Michigan to New York. The audiobook is only a few hours long, so it's very accessible. The imagery of exploring another planet is fascinating and the interactions between the human characters, the Malachandrans, and the Eldils are always thought-provoking.

On the Edge of the Dark Sea of Darkness - Andrew Peterson

This is also my second time through this book, but this time it's as a read-aloud with my third daughter. She is generally aware of the story, but asked me to read it out loud each night before bed. This is another wonderful adventure and redemption story (over the course of four books) that challenges some of the traditional strutures of fantasy stories.

I didn't finish any books in May. Shame on me.

I'm in the middle of a couple of books, but reading is slow, mainly because we're up later during the long days and I go to bed that much more tired in the evenings. School ends tomorrow so my reading time will expand significantly and I can make more progress toward my reading goal.

In the past, I had written notes of encouragement to each student. They'd taken different forms from handwritten to printed slips to small conversations. This year, I decided to decide on a theme that would apply to my classes. This year's recommendation:

Set boundaries for yourself.

Frankly it stems from phone use, but it goes into many more aspects. There is value in hard work, and learning is hard work. There is dignity in working at things that are difficult instead of trying to take an easy road out. There is growth that can only happen when you work through a situation or problem.

I want to encourage my students to set boundaries for next year - limits they won't cross while they're in school. For some, it might be putting a phone in a backpack or locker. For others, it may be not opening an AI tool to get a quick answer. Or it's choosing not to engage in conflict.

Whatever the situation, having a boundary or a commitment to act in a particular way is an asset. Hopefully, some of them will put that to practice next year.