Introduction

Inspired by Doug Belshaw’s Weeknotes, I’m going to start the same here.

This does seem like the the sort of project that sounds exciting now, with weeknotes and excitement fading in a week or so. We’ll see how it goes…

In this first weeknote, I’ll ponder what might get written about, and what probably won’t. Mostly, I think I’ll write about progress on personal projects, links to interesting things that don’t deserve their own post, and other random things that happened during the week. I probably go light on the personal details. Goings on at my day job won’t be articulated here either.

By the way, this particular weeknote is being posted a week late as not to violate the long standing custom of not backdating blog posts.

This Week

Happy New Year! We continued our tradition of a New Year’s Eve meal of delicious appetizers. The chef flubbed the sourdough pizza dough and had to make another, last minute dough on the fly. On New Year’s Day, we went to a party and saw the cleanest workshop ever.

As I normally do on the 1st, I took a look at my goals (not resolutions) from last year and made some adjustments for 2024. I also caught up on my One a day photos, more thoughts on that here.

On Friday, we had our regular jam session. This week, we recorded it! I spent a little time playing around in Reaper doing the mixdown. Mostly I just cut out the witty banter and added EQ and compression to some of the tracks. I think we sounded okay. It will be good to compare where we’re at in a month or two.

I went down to the club for the first time in a while. I handed over the bookkeeping duties I had been doing over the last couple years. The boat had some water in it, although not up to the floorboards, so I pumped it out. Then it was off to Old Town to catch up with friends.

Saturday was the 3rd anniversary of the attempted insurrection. Let’s hope that never gets turned into a national holiday.

Jon Udell’s 7 Guiding Principles for Working with LLMs has some really solid advice on using Large Language Models. His usage is mostly around software development and writing. Two areas where these LLMs can really shine.

By the way, Jon’s Seven ways to think like the web is still as relevant today as it was in 2011.

I’ve only dipped my toe into the LLM pool thus far. As I embark on a personal project, I’ll follow these principals while I lean on LLMs to make up for my lack of recent knowledge and experience in developing tech. I find them to be especially helpful with the syntax and best practices type questions I would have been scouring in Stackoverflow for in the past.

Regular expressions seem like a dark art to me. I use very simple ones frequently enough to remember a few things. Anything slightly more advanced probably involves web searching and copy/paste.

Regexer is a tool for learning and experimenting with regular expressions. It does a great job of breaking down the expressions and showing how each element works. There’s also an extensive library of community patterns to choose from.

via Flowingdata

TL;DR Intuit uses their customers’ customers to drive adoption of their payments solution.

The screenshot below is where one is led after clicking the “view invoice” button. If the customer clicks the giant green button, an email is sent back to business (Intuit’s customer) indicating that “[customer name] wants to pay you and needs your help”. The email sent back to the business is really just a marketing piece prompting the business to sign up for Quickbooks payments.

What about the user trying to view their invoice? What benefit to they get for clicking that giant green button and unknowingly firing a marketing email to their vendor? They get some more copy to read, copy that doesn’t get them any closer to seeing that invoice. They still need to click on the small “view invoice…” link, which they missed on account of the giant green button.

It’s a terrible experience all around.

For those who might not know, Quickbooks is a popular bookkeeping system for small businesses. In my opinion, it makes bookkeeping quite straightforward. There is no freemium tier for Quickbooks (as far as I know), so everyone is paying for the service. Intuit includes a fair amount of marketing in the application for their additional services like payments and banking products. However, that marketing information rarely seems to get in the way of the core functionality.

This invoice email, on the other hand, really gets in the way. It is confusing for customers, and difficult for those using Quickbooks to turn off. A busy bookkeeper or business owner is unlikely to know this is happening until they start seeing those “…wants to pay you and needs your help.” emails. Businesses and especially their customers shouldn’t be punished because Quickbooks payments hasn’t been enabled. The invoice emails sent by Quickbooks to their customers’ customers should not be used to push additional services.

By the way, I called out Inuit almost ten years ago for some other nonsense: Dark Pattern: Turbotax Marketing Email Smells Phishy. Obviously, I caved and started using their projects since then. But this one really grinds my gears. Please stop doing this, Intuit.

The end of the year has proven to be a difficult time for me to take a picture a day, as evidenced by all of those footage not found squares on One a Day. I thought about declaring bankruptcy today since I had fallen so far behind and had little to post. Instead, I opted to forge ahead. As of today, I need less than 100 pictures to finish the project–I’ll try to finish strong.