Tuesday, November 17, 2026

Moving the Blog

 

The time has finally come to say good bye to my blogspot blog. I've been threatening to do it for years now and finally it's time. I'm trying to degoogle my life and I'm trying to own my own infrastructure as much as I can, or at least have everything in Canada and make sure that I'm the client and not the product.[1]

I guess we'll call this Project 24 and it's going to be in three parts — like how a John Green video comes with the part before he tells you how many parts its, the part where he tells you how many parts it is, and then the part where tells you all the parts.

  • Part 1 — Figuring out Hugo and getting it set up on my new Canadian host.
  • Part 2 — Getting a blog set up and styled in Hugo
  • Part 3 — Exporting everything from blogger and reuploading the good bits to the new blog.

I'm going with Hugo because at the moment it suits me. I'm excited about static sites and I'm very fond of template based generators. It seems like about the right amount of weight for what I want to do and the right amount of manual for me to learn something.

And yeah, I might be blogging a bit more again.


  1. Although I've been using Site5 as a host for several years now and they've been really good. I just need less stuff than I'm buying and I'd like my money where my mouth is when it comes to ↩︎

Friday, January 09, 2026

A Commitment to Creativity and Genuine Human Expression

 My work requires me to some extent to deal with artificial intelligence and as a person who spent years doing research in AI (or knowledge-based search and multi-agent systems) I often end up engaged with AI to some extent. Between these, and needing to build up my knowledge and skills, so I can support people making good choices about AI, I'm starting to write a lot more about AI (and other stuff) on my Learning and Technology blog.

 

There's a lot going on with AI and generative AI. A lot of the uses of AI are tied up in a lot of dark patterns, dishonesty and anti-humanistic thought. So while I need to be more engaged with AI this year, I want to make a commitment:

 

I think human minds and spirits are the most important and all that we do as species and society should be in an effort to support people. 

 

Making things is really important and the effort people go to to make things by hand is really cool and needs to be supported. In whatever comes, I am excited to see the things people make and the things people make with their own hands and minds are the most important things to me.

 

I want to do my best to be a genuine human and I'm excited by the things people do being genuine humans.

 

I'm not sure that all makes sense, but I wanted a starting point as I go on the jouney I need to take this year.

 

Make cool things! 

 

 

Monday, November 24, 2025

Two Things I Ran Across Trying to Learn about Spring Boot

For some of the projects I've been working on I've wanted to set up an easy web interface based in Java. After looking at a bunch of options to learn, I chose Spring Boot which seemed like the most straight forward and possibly useful choice.

I ran into some issues getting started, so I thought I'd write them down in case it helps anyone else. I'm sure that mostly I'm confused and not reading the documentation carefully, but writing is a good way to learn.

For context, I'm working from what looked like a good tutorial on Spring Boot (https://spring.io/guides/gs/spring-boot) and started working through it. The tutorial points you at the helpful Spring Initalizr (https://start.spring.io/) which helpfully (helpfully?) generates everything you need to get started on a Spring Boot project.

Gradlew Version (Which looks like Unsupported class file major version)

The first big thing I ran across was an error from Gradle saying:

BUG! exception in phase 'semantic analysis' in source unit '_BuildScript_' Unsupported class file major version 69 Unsupported class file major version 69

This was surprising but not super unexpected, for most of the projects I regularly worked in Java in I locked to a version and tended to build most things from scratch (Also updates to the Java version were way less frequent). So I almost never ended up with classes compiled in different versions of Java in the same place. I poked this for a while, but it seemed wrong to get this in a clean install of a Spring Boot application, where I hadn't even edited anything yet.

I don't use Gradle for anything (that's why I'm learning right now) and certainly haven't updated my tech stack for a while, so I figured a good updating of everything would probably help. I fired up Homebrew and let it upgrade everything. This took a few hours — did I mention that I hadn't updated everything in while, but it was fun in the way installing software off of diskettes in the 90s was fun.

This certainly fixed a lot of things and ensured that I had the newest version of Gradle (9.2.0) and Java (25) in the path. Problem solved, I ran

./gradlew bootRun

aaand got the same error.

This was particularly frustrating because a lot of the Stackoverflow and forum posts, tend to — slightly snarkilly — point to the Gradle compatibility matrix (https://docs.gradle.org/current/userguide/compatibility.html) which is slightly frustrating when you are clearly using not only a correct paring of Gradle and Java, but the latest paring of Gradle and Java.

After quite a bit of poking and reading things online, I eventually landed on something being weird with the Gradle Wrapper. I remain a little confused by the Gradle Wrapper, especially when you get the wrapper with a project you're starting on. The idea that it allows you to lock your Gradle version and settings makes sense, but a lot of the details feel fuzzy in the documentation I've read so far and I'm not sure what the difference is between the wrapper and just running Gradle with a specific version. Possibly it's more convenient.

Anyway, it took me a while, but I eventually realized that while I was running Gradle 9.2.0 the Gradle Wrapper in my project from Spring Initalizr was running 8.14.3.

After some more reading I eventually figured out that I had to upgrade the wrapper, with the command:

gradle wrapper --gradle-version 9.2.0

My Googling was sub-par, but I think the document I should have been looking at is this one: https://docs.gradle.org/current/userguide/upgrading_major_version_9.html. Although since I hadn't upgraded my version of Gradle (I just started the project), I felt a bit unsatisfied.

(On further reading (https://docs.gradle.org/current/userguide/command_line_interface.html#sec:environment_options) it seems that what that does create a new wrapper using the specified version, which I guess makes sense.)

Anyway that was the key to getting Spring Boot up and running.

Spring Boot Does Something Weird With Packages

With Spring Boot running, it started Tomcat correctly, but when I poked it using curl all I got was a 404. This was again a little frustrating because I was using the fresh zip file from Spring Initializr and the code from the tutorial.

The application was clearly running, as the code the tutorial includes to show all the beans was working and when I started the app, it gave me a long list of Beans, but when I sent a web request, I got nothing back.

The annotation Spring (Boot?Web?... still learning I guess) uses for establishing endpoints seems to be pretty clear @GetMapping("/") where whatever you put in for a path should be where your Controller gets served, but changing out the path didn't work.

Again my Googleing was a bit weak and I couldn't find anything that directly related to what I was seeing — which is why I thought it would be worth while to write it up here, even if my problems are mostly due to my lack of knowledge.

It seemed to me that the @GetMapping("/") assignment wasn't taking and especially since I'd had some issues with getting things from the Spring Initalizr I wondered if there was something funky in the naming of some of our files or paths.

As I was looking around, I noticed a note in the Spring HELP.md file:

The original package name 'com.example.spring-boot' is invalid and this project uses 'com.example.spring_boot' instead.

Which given my guess about why I was getting the 404 error, gave me a good place to look.

So I went and looked at the two files I'd added from the tutorial src/main/java/com/example/spring_boot/Application.java and src/main/java/com/example/spring_boot/HelloController.java. And as it turns out I did have the package names wrong, just ... not in the way Java would usually find them wrong...

In HelloController I discovered had the package name right, package com.example.spring_boot;, however I had the package name wrong in Application.java, where it was package com.example.springboot;. For the record I think this came from copying files out of the tutorial slightly incorrectly (it uses springboot without a space, which doesn't align with the Spring Initalizr settings they point to, but I didn't catch that).

Now the issue here, at least to my old-timey java mind is that. Application.java was working, the code added in the tutorial ran — it printed the list of beans, and later the message I replaced that list with — but that should have failed based on the package name.

Or I guess that being said, given that spring is very good about finding and plumbing things together, maybe the error shouldn't have happened at all? Or it could possibly have put a warning somewhere I noticed it. Once I got everybody on the same package name (spring_boot) then

Summing Up

As I noticed, I really only wrote this up because some of the things I found online didn't really answer the questions I had. Since I had to do a little learning to solve them, I figured I'd write it up for myself, and maybe it will help someone else at some point.

So,

  • Make sure you have Gradle and Java updated to the right — and compatible — versions.
    • Run gradle wrapper --gradle-version 9.2.0 to fix the gradle wrapper.
  • Make sure that you have the correct — and matching — package in your .java files
    • The tutorial as written and hooked up to Spring Initalizr don't quite align if you're not paying attention.

Friday, August 01, 2025

A Rest - The Blog 2025

So I've managed to post at least once a month since July of 2016, right up until April this year. Now I've been quiet for quite a few months.

I'll be honest I'm struggling with what's worth sharing. I think in the current world, the purpose and use of the internet has become a lot messier than it was in by-gone days and given the amounts of hate and misinformation, I don't know what to put into the world.

As I'm sure I've posted in these time after time, I hate it when projects go away without word, so I've keep these Blog-End-and-Start Days around as a way to give myself a natural point if the blog were to end...

Damn it, is this a quitting YouTube Video in text form?

It might be. Ah, well. Alas.

So, here's where I'm at. I don't know that I want to share a lot about my life. The easier and safer-feeling days of the Internet have faded and putting time and the energy into online spaces doesn't feel compelling. I'm still thinking projecty things, but, for my own mental health, I've manage to adjust my perception about how what I do relates to who I am, and so I'm  feeling less like the things I'm working on need to be shared and also feeling like I'm in a period where there's a lot of learning and work I want to do without an audience.

I've also discovered that journaling has been really beneficial for capturing my thoughts in a way I used to feel I needed an audience for. That has honestly been the best thing to support my mind through the end of Twitter and for my mental health over all. I started journaling after reading from somewhere (possibly in Twitter) that it was a good idea to have a record of your life that couldn't get destroyed or lost by a tech company, and a good hard-bound paper book has turned out to be a wonder in a lot of ways. 

Also it lets me buy stationary and that's always fun.

What's next? Well, a few things. 

I will still post here, but I think we can count all of the projects as "on hiatus" at least for now. That includes the blog-as-blog, although I may have bloggy things I want to post here too. I'm on Mastodon, at @tjkendon@mstdn.ca and @tjkendon@scholar.socal, I'm pretty quiet there too, but I may expand depending on what makes sense to do. I guess I'm also on BlueSky, but kind of quietly. Finally I've been thinking a lot about learning technologies and have some things I do want to share in my work context so I expect I'll be more present on "Teaching & Learning". 


It's also (really, seriously this time) time to move this blog off of Blogspot. I'm honestly baffled at this point that of all the Google products this is still here, but 1) It's been janky as hell since ... I started posting and 2) I think in this current world being intentional about ownership of your digital footprint is more critical than ever. So you can expect to see what ever I do in a new space, but we can hope that Feedburner will keep things moving along smoothly. I will leave lots of signage, blinkenlights and breadcrumbs.

So it's not good bye, but it is see you around.

Go make something, but mostly be good to each other.

TJ

White text block in the bottom right of a black square. Reminiscent of Cowboy Bebop



Moving the Blog

  The time has finally come to say good bye to my blogspot blog. I've been threatening to do it for years now and finally it's time....