FAESEL.COM

The context wall nobody warns you about Here's something that took me longer to learn than I'd like to admit: Copilot CLI has varied context window caps depending on the model your using, and you start paying for it long before you ever type a prompt.

It started with curiosity, now I can't live without it A few months back I wrote about building GridWatch — a desktop dashboard for GitHub Copilot CLI sessions.

Introduction If you've been using GitHub Copilot CLI, you'll know it stores a surprising amount of data locally — session metadata, conversation history, token usage, tool calls, checkpoint snapshots.

Introduction Recently, I’ve been using the Nx monorepo framework quite extensively—but purely for frontend React projects.

Introduction Recently I encountered a scenario where I needed to integrate New Relic into my Electron application.

As a engineer learning new languages, tools frameworks etc is just part and parcel of the job.

I've been using C# for about a decade now, and every now and again I discover something that surprises me.

Starting my journey with GraphQL Up till now, I've always heavily relied on RESTfull services to power API's, this recently got widened with GRPC which you can read about in my article .NET & GRPC What they forgot to tell you.

Recently I started working on a project that was created from the ASP.NET SPA template for react.

Why I started building a CLI As a .NET engineer, I work with Azure storage a lot, its versatility, ease of use, as well as cost makes it a common staple amongst developers.

As an engineer, I have always had a heavy reliance on REST'ful API's for passing information between applications.

As a windows user the terminal experience has always been lacking, up till the new windows terminal was released.

I recently recreated my blog in GatsbyJs, you can download a template of it here gatsby-techblog-starter.

I'm someone who's always had my own tech blog, I've gone through two revisions already with the last revision updating out of a 1997 style book.

I'm currently working at a place were we are using queue triggered Webjobs to handle the sending of messages like email and SMS (using Send Grid and Twilio).

Having looked at a number of projects in my lifetime, I always come across classes named something like "CustomerService" with similar variations (usually in the same project calling each other) ranging from "CustomerProvider / Helper /Manager / Store / e…

This is a quick guide on how to split unit tests into different categories to decrease the time it takes for your CI build to run.