Posts on LINQ to Fail

Back in 2021 I switched to using a split keyboard, the ZSA Moonlander, and I wrote about my experience after the first month.

The last post got the Tessel 2 from the factory-era image to LEDE 17.01.

The last post we went through the first attempt at getting a modern OpenWrt on the boards using a one-shot upgrade from the factory image, and it failed.

At the end of the last post I decided that upgrading OpenWrt was worth the risk.

The last post left me with a working Windows path for deploying code to a factory-standard Tessel 2.

At the end of the last post I said the next question was whether I could talk to these boards at all.

Last time I said these boards run Linux, and that I didn’t know that when I started.

When I first joined Microsoft, I was doing a lot with JavaScript and hacking around a bit with IoT.

Recently I had to fix something that had become a bit too easy to ignore in the Aspire Community Toolkit: our NuGet publishing in CI had started failing, and the fix I wanted wasn’t “rotate the key and hope for the best.”

The Aspire Community Toolkit has grown into a comprehensive collection of integrations to expand how developers can build and orchestrate distributed applications with Aspire.

One of the things that comes with maintaining the Awesome Copilot repo is that people want to contribute to it.

I spend a lot of time hopping around folders in Explorer, especially when I’m bouncing between demos, samples, blog code, and whatever random side quest has captured my attention that day.

Well, I missed my usual January post, and given that I hardly wrote anything in 2025 anyway, I don’t think it was much of a surprise.

In the middle of November Aspire 13 was released and with that came quite a few large changes that we would need to tackle in the Aspire Community Toolkit.

What’s this, a blog post after not having written one all year?

With 2024 coming to a close I managed to just scrape through with my yearly goal of 1500km, having to go out on NYE for one last run (I had 7km to go, so I ran 10km just to be safe).

Would you look at that, I’m even early this year compared to my 2023 post which was earlier than 2022!

In the 2024.4 release of Home Assistant, the Labels feature was introduced.

Like many people, I’ve been diving into Generative AI (GenAI) over the past 12 or so months and looking at how to use it in the sorts of solutions we can build.

I’m currently working on a project in which we are using Entra ID rather than a traditional Postgre username and password.

I’ve been exploring .NET Aspire as a pattern for how to build .NET apps, and when checking the features of the Preview 3 release I noticed something interesting, a new service connector for using OpenAI/Azure OpenAI.

This post is written against the .NET Aspire Preview 2 release, so it may change when the final version is released.

Would you look at that, I’m early this year (well, compared to my 2022 post)!

Well, it was a goal of 1500km, just like in 2022 but again I’m gone and exceeded my plan.

For the last six months I’ve been adding to my smart home the thing that makes it feel really futuristic, lights that turn on as you enter a room and then off when you leave.

When we explored Chat Completions in Part 3 we used the asynchronous API to call our model, but it’s still somewhat a blocking call in that we wait for the model to generate a response before sending to the client.

After text generation the most common thing you’re likely wanting to generate with an LLM is going to be images.

A little over a year ago I wrote about dissecting some phishing attempts and while I still got the odd one here and there, nothing really was slipping through the M365 spam filters.

If you followed the code sample in the last post you’ll have a console application that can generate chat completions, but what I didn’t do was explain what chat completions are or why we’d use them; that’s the purpose of this post.

It’s time to have a look at how we can build the basics of an application using Azure OpenAI Services and the .NET SDK.

I’ve missed a lot of the recent hype trains, I skipped over blockchain, I avoided web3, and I’m not dumb enough to have believed NFT’s were anything but a scam, but I’m not going to miss out on the AI hype train!

I finally took the plunge and did the thing I’d been wanting to do for a while now.

It’s just over 12 months since we moved into our house and I started properly running Home Assistant and designing our smart home.

When designing a smart home I’ve reiterated many times that the goal was to make it work regardless of who was there and that existing expectations of how things like switches work are maintained.

This is the last in the three part sub-series looking at the newly launched Data API builder for Azure Databases (DAB) and while last time we looked at creating a React application, this time I wanted to look at how to do the same thing but in .NET using…

In the last post I introduced you to a new project we’ve been working on, Data API builder for Azure Databases (DAB) and in this post I want to look at how we can use it in Azure, and that will be through one of my favourite Azure services, Azure Static W…

I’m really excited because today we launched the first public preview of Data API builder for Azure Databases or DAB for short (the official name is a bit of a mouthful 😅).

When you get down to it, a smart home is partially a software solution, and like any good software solution there are bugs.

I really like the idea of having a smart door lock on our front door, something about the peace of mind that I can know if they door is locked or not, control access and all those things, so getting a “smart” lock was something I started researching long…

We’ve got a lot of windows in our new house, for example the main bedroom has four windows.

In building our new house we decided to add a motorised gate across our driveway.

As much as I love using devcontainers for all my local development (see here) there’s often repeatable things that I want to do in them which means I go back and copy RUN steps from previous Dockerfiles that I’ve created.

Would you look at that, 1 year to the day since I did my 2021 post so I’m consistently late, woo!

When we got our new house built, we decided to hold off putting in feature lights because we wanted to see the space first and then decide what we wanted in each of the areas as features.

To say that 2022 was a tough year is probably an oversimplification of things, but yeah, 2022 was tough.

Well, 1,565km’s to be exact, but who’s really counting (oh right, me, that’s the point of this post!).

Where I live, we have three bins that we can put out, depending on the week, red for household rubbish, yellow for mixed recycling and green for garden waste.

When we designed our new home, we decided to add ceiling fans to each of the bedrooms, mostly because, while we have a HVAC system in place that is ducted throughout the house, sometimes you just want some basic air movement in a room, especially when it’s

Next.js is one of the most popular JavaScript frameworks for building complex, server-driven React applications, combining the features that make React a useful UI library with server-side rendering, built-in API support and SEO optimizations.

In the previous post in this series we added a new “virtual” field to our GraphQL schema for Post, related: 1 2 3 4 5 6 7 8 9 10 type Post { id: ID!