When building APIs, you'll often want to create and store a collection of endpoints and requests in order to test quickly and effectively. There are a number of tools to help with this, but the one I use most often is Postman.

It's hard to remember how things used to be prior to all the big tech companies. They went from making great products to stealing our information and showering us with adds, so I've started looking for alternatives.

When doing full-stack development, most times you'll be working with a front end client and some sort of API that the client will consume. For web development, this usually isn't a problem since your API runs on one port and the client is on another - everything can still talk.

For most apps, I tend to use Microsoft SQL or Postgres for data storage and persistence, but occasionally it may also make sense to use a document database. I wanted to see how it was working with Cosmos DB in a .Net application.

This is the fourth article in a 10 article series: Blazor vs Flutter. This post focuses on components and pages.

Lately, I've been looking at a few different options for a CMS platform. Of the ones that I've looked at, I think Umbraco makes the most sense, considering that most of my work uses C# & .Net, it has online hosting for ~$35/month, and it's been the easiest for me to understand.

Sometimes it can be useful to share your code between projects or with other individuals. One easy way to do this is through the creation of a NuGet package.

Over the past few months, I've dedicated a fair amount of time to two different activities: experimenting with indoor farming and building an open source farm management platform