The A in AI stands for anchovies?

In which we merge two controversial topics: Generative AI and…anchovies on pizza??

I’m about to write probably the most controversial sentence I think on this blog in its decade-plus long history:

I like anchovies on pizza.

No, seriously, I do! But according to a 2023 YouGov survey, nearly 3 in 10 Americans definitively say that anchovies are their least favorite pizza topping. (The same survey said that only 2% of Americans preferred New Haven style apizza, which is clearly another conversation for another time!)

Lest you think I’ve departed from writing on tech matters and going full foodie on you, there is an actual tech angle to this. Presumably because anchovies on pizza is such a controversial thing, the number of pizzerias in the Twin Cities that offer this is not a lot. I’ve found a couple of places, but I’m still searching. I found a pizzeria in a grocery store – Pizzeria Pezzo in Kowalski’s Market in suburban Woodbury (and before you send me your letters, I wasn’t compensated for this pizza or paid to say this) – that had anchovies on their toppings list. Of course, a field trip had to be on the menu.

(To my readers back in Phoenix: Actual restaurants in grocery stores is quite a thing up here. And they aren’t fast-food burgers or sandwich shops — they’re proper standalone restaurants that happen to share a building with a grocery store! Also, Kowalski’s Market would be similar to AJ’s Fine Foods.)

My usual thought process is to have capers on this pizza, but those weren’t on the toppings list at this place. That led to a spot of inspiration: See what ChatGPT recommends. Maybe it might be spot-on; maybe it could be way out of its depth. But it was worth a go at least for some ideas, right?

I scanned the toppings list to my iPhone and copied the text into ChatGPT. I gave it the prompt: “Propose a pizza with 3-4 toppings from this list below. Anchovies have to be one of the toppings.” The toppings list was below my prompt sentence. Almost immediately, it responded:

I would recommend a pizza with the following toppings:

  1. Anchovies (required)
  2. Roasted red pepper
  3. Caramelized onion
  4. Fresh mozzarella

This combination of toppings will give your pizza a delicious blend of flavors, with the unique taste of anchovies complemented by the sweetness of caramelized onions and the smokiness of roasted red peppers. The creamy fresh mozzarella will provide a delightful contrast in texture. Enjoy your pizza!

So ladies and, in a broader sense, gentlemen: I present to you a pizza whose toppings were suggested by ChatGPT:

A pizza with anchovies on it
An anchovy pizza with other things. Rather tasty!

It was spot-on. And probably one of the 10 best pizzas I’ve had? (And also deserved a visit from the pizzeria manager, who said he appreciates someone who does anchovies on pizza.)

This is what I say when I talk about “doing more with more” – here’s a system that we can use to comb through different combinations and permutations of everything, and recommend something that makes sense. I gave it a baseline, and it went to work. What surprise and delight.

Doing more with more?

IT leaders and practitioners are often compelled to do more with less. But what if we leveraged tools to help us do more…with more?

A couple of weeks ago, I wrote on my LinkedIn about unashamedly using tools like ChatGPT to help out with tasks.

It’s something that I’ve been thinking of a lot lately, if I’m honest. In the IT world–and especially in the nonprofit IT world, the phrase “doing more with less” has become a mantra, as we are all constantly challenged to achieve greater outcomes with limited resources (whether real or artificial).

Seeing tools like ChatGPT come around, and the attendant press that’s come with it, makes me feel like we’re standing at the precipice of a major paradigm shift. These tools aren’t limiting us; rather, they can make us do more. In other words, we can do more with more.

By leveraging these tools, perhaps IT practitioners (nonprofit or otherwise) can focus on the creative aspects of our work, leaving the machines to do the mundane. And let’s be honest: Computers love mundane tasks.

So over the next few weeks, I’ll be writing some thoughts on this matter. Join me, won’t you, as we do more…with more?

Whither Microsoft Planner

Microsoft Planner can be so perfect if it had a few extra things. But for now, there’s PowerShell

I want to love Microsoft Planner. But there are some things it has in it that just confound me. Rather, I should say it has omissions that confound me and make me question its usability.

For the uninitiated, Planner is a user-friendly project management tool designed for teams to collaborate and stay organized. Planner helps users create tasks, assign them to team members, set due dates, and track progress visually on customizable boards. It’s not a full and formal project management software, like its older sibling Microsoft Project, which is way more robust and suitable for complex projects with intricate timelines and resource management. Planner is more accessible; Project is more involved. Still, Planner excels at promoting collaboration, task management, and maintaining an overview of project activities, making it ideal for smaller teams and less complex projects.

Here’s a perfect example for Planner that we’ve rolled out at my company: organizing all of the activities and tasks around what it takes to bring a new employee onboard and for their first few months on the job. It’s a perfect solution for that, because there are different buckets of tasks, a deadline for those tasks to take place, and different people responsible for those tasks (be it IT, HR, or the new employee’s manager). Instead of having these tasks live in a spreadsheet on someone’s desktop, they can now live in a collaborative environment.

Continue reading “Whither Microsoft Planner”

Sometimes we get it wrong

Stories from misadventures in rolling out a new printing system, or: Sometimes we get it wrong

Back in January, we started down the path of migrating from PaperCut’s on-premises solution to their fully cloudy PaperCut Hive. Whilst I was initially skeptical about it at first, it seemed like it had enjoyed success in larger organizations, so certainly it should work for a small nonprofit of ~30 people?

Oops. Also, [expletive deleted].

Sometimes we get it wrong. The rollout went about as well as it could go. I’m still frustrated by the fact I had to manually deploy the print client to our users and that the software wasn’t any sort of identity- or directory-aware. Getting a executable file that’s coded in the installer for each user? That’s not nice. Requiring administrative permissions to install that? Go away or I shall replace you with a very small shell script.

What ultimately doomed the rollout for me was that we had users who had sporadic and random issues. There were no common threads among those who had printing errors (other than, presumably, they were trying to print and the day ended in y), so troubleshooting was next to impossible.

Since printing’s kind of a mission-critical task where I am, we made the decision to abandon Hive and go back to MF. And I’m fortunate that I have supportive management and colleagues who understand that sometimes, you get it wrong.

Five Things for PaperCut Hive

A return of the Friday Five and some of my observations on PaperCut Hive, a software stack I’m currently deploying

Where I work, we’re almost complete with a migration from PaperCut MF on-premises to the fully cloud PaperCut Hive product. For the most part, I’m pretty pleased with how it’s gone and how it supports some of our organization’s transition goals to less on-premises. But there are some things that have been some definite head-scratchers in the process.

1. There’s no migration. That’s right: there’s no migration. Any data or user provisioning settings in MF don’t transfer over. You’re starting from scratch. Do you have RFID badges for your employees that they use to authenticate to the copier or MFP? Gone. Custom scan locations? Gone. While I’m thankful that I have a small number of colleagues and they have been more patient with me than I deserve, imagine if you have to have hundreds or thousands of employees re-authenticate on the new system. At least it’s a one-time only process.

2. There’s an app, but you don’t need it. PaperCut makes a big push to have users download their app for print management. I have issues with making people download company software to their own personal smartphones. Thankfully, even though PaperCut makes this push, you can ignore them.

3. Communicate early, often, and concisely. One of the questions I received a lot was about why we were doing this and how this would affect them. Fortunately, by planning the deployment, I was able to say that except for two initial tasks, everything would remain the same. And I told them why this change was being made, which was to support our organization’s future technology stack.

4. If you have multiple copiers/printers/MFPs, don’t move everyone over all at once. Keep both printing systems running in parallel so that you don’t have to sweat it having some users unable to use the printers and you have to rush the migration. By having some machines on the new system and some on the old system, you don’t have to be so aggressive in moving everyone over.

5. What automation? What year is it again? There is no way to use automated tooling to deploy PaperCut Hive software to our colleagues’ computers. To install the software, I had to go to each machine, download the unique software that PaperCut generates for each user, install it using my administrative credentials, and go on. That worries me, because that means the software is not directory aware and also means that I can’t include it in a base deployment configuration. While I’ve heard that this may change in the future, had I known this limitation, I would have postponed our deployment until later.

Those are some of my observations about this. It’s been received well by my colleagues, but some of the initial challenges made for a fun week.

A blogging renaissance?

Are we standing at the front door to a blogging renaissance?

Back in October, I put some thoughts out on LinkedIn about the future of social media and if we’re headed toward a renaissance of the blog. Given the public agita about the current social media landscape and the associated issues regarding content moderation, ownership of those platforms, and bullying and minimization of minority communities.

Personally, while it had been festering for some time, I finally pulled the plug on my use of Twitter. While I had been using it for 15 years, it felt to me like it had run its course and was far more noise than signal. And, to be absolutely fair, the whiplash changes to that platform under its new ownership helped push me to making this decision. It doesn’t feel like a huge loss for me.

The heir apparent to Twitter seems to be Mastodon, but I’m not sure if I’ll go on that. Not because I have issues with that tech stack – it sounds fantastic and totally dismantles the so-called web3 notion that anything decentralized has to have blockchain technology and some sort of transactional monetization to work – but because I’m not sure if I need to be on that. You might recall my essay on Five for the New Year 2023, in which I said one of the things I’m going to work on in 2023 is limiting digital distractions. It’s also why I want to spend my time in this world, and not some digital “metaverse” world that is definitely totally happening* at some point in the future.

I’m therefore led to make the following bold proposition: One of the major moments in the changing of the internet from independent communities to being controlled by a handful of social media companies was when Google killed Google Reader ten years ago. Instead of a choose-your-own Internet that was based on what you wanted to read from the sites and sources you chose, social media companies sucked us in to their sites and subjected us to their algorithms and rage. If you wanted the latest news from major news organizations, you are left to the whims of the social media networks whether they’d even allow it, or if the platforms were even telling publishers the truth. And that all led to the advertising dollars going to the websites that got the most views, which were not the traditional journalism outlets and newspapers, but rather internet content farms.

I digress. This isn’t about my views on the internet, but on blogging specifically and my proposition that blogging will see a renaissance in 2023. I realize my blog is a special case, because this is not a revenue-generating operation for me. With platforms like WordPress still out there, and even with some free or relatively inexpensive, there’s no barrier to entry.

I’ve been at this for well over a decade now, and I think I quite like it. In 2023, it takes a renewed interest with more frequent essays and columns, and frequent photography. The best part? It’s mine. Not Meta’s or Twitter’s.

Mine.

blog image derived from a photo by 4motions Werbeagentur on Unsplash

Behind the Weather Dashboard

Editor’s note: Due to ongoing systems and networking upgrades, the weather dashboard is temporarily offline.

The second COVID-19 vaccine knocked me out for a couple of days, so while I was recuperating from that, I created a Grafana dashboard with data from my weather station. The station is perched atop a building in midtown Phoenix. The dashboard is still quite a work in progress, but I’m pleased thus far with how it’s coming along.

For those who aren’t in the IT world, Grafana is a software platform that creates visual dashboards from various sources, including time series databases (TSDBs). TSDBs work by collating discrete metrics over time, and they’re usually found in the world of information technology. Instead of network I/O or CPU usage, the principle works for weather statistics: At this time, it was this temperature or the wind speed was that.

Continue reading “Behind the Weather Dashboard”

The Home Server

The past year has brought upheaval, but it’s given me a good space to rethink my computing portfolio. Join me on Fridays as I share discoveries and new things

Over this past year of COVID-19 lockdowns, I’ve taken the opportunity to re-conceptualize my personal (and business) IT portfolio. Prior to the pandemic, I was rather haphazard about things. Even though I espoused the benefits of having a master plan and having things fit into that plan, in practice for my personal IT estate at least, it was a different story. I focused on getting things stood up quickly rather than robustly. It worked, but it sometimes incurred a price.

Continue reading “The Home Server”

The Friday Five: Improving Your Video Calls

As video calls have taken a bigger spot in our lives in the past few weeks, here are some cheap and easy ways to up your video call game.

What a weird few weeks it’s been. I hope everyone has been safe and healthy during these interesting times. For those who have been working from home, I’m sure video calls have been a part of your life. They certainly have for me!

Since I’ve been doing this for a bit, and since I also have some things to bring from dabbling in the photographic arts, I thought I’d share some easy things you can do to help improve your video conference setup. Each one of these ideas can be done independently of each other, so as to be flexible for limited budgets, but the total cost of all five of these different interventions shouldn’t exceed $100. With a couple exceptions, you probably have the kit around your home already! Continue reading “The Friday Five: Improving Your Video Calls”

Pixel 3 exFAT camera importing update

Good news! An update on the exFAT-on-Pixel 3 adventures I chronicled from earlier this week. It only requires the purchase of an app.

Back at the start of this week, I wrote about my issues with not being able to import photos from my standalone Canon DSLR camera to my new Google Pixel 3 XL because the Pixel doesn’t support the exFAT file system natively. I’m happy to say that I have good news and I’ve found a workaround that only requires the purchase of an app.

Before I get into this, I’m just going to write here that your results may vary and that I’m not responsible for any loss of data you may have as a result of this. Be sure to practice good data hygiene and backup responsibly.

My solution hinges on the “Microsoft exFAT/NTFS for USB by Paragon Software” app available on Google Play. Whilst the app is free to download, exFAT support requires a $5.99 in-app purchase. This app is unique in that it’s not a standalone file explorer, it’s an interface mechanism between the USB SD card reader and some other apps, including the default Files app on the Pixel. Here’s how it works:

If the captions aren’t viewable, the steps are as follows:

  • Step 1: After connecting your SD card reader to the USB-C port, launch the Microsoft exFAT/NTFS (etc.) app. Tap on MOUNT. (The UNMOUNT button is shown after the device has been mounted.)
  • Step 2: In the Files app, you’ll see that a new option is there: the Paragon File System. That’s your SD card.
  • Step 3: You can now browse your SD card and copy/move/whatever files from the card to local storage or cloud storage.
  • Step 4: When finished, go back into the Paragon app to UNMOUNT the device. Unplug the SD card reader and you’ll be good to go!

My explorations are still continuing because although I can easily copy-and-paste the SD card files, there is no mechanism that I have discovered so far that won’t copy duplicate files. By default, if you ask the Pixel to copy a file, if it’s a duplicate file name, it will just append a (1) next to the file name before the file extension.

Explorations are continuing! Isn’t that the great part about learning about new technology?