1 min read

What happened to all the programming posts?

What happened to all the programming posts?

This blog has been lacking content for awhile. The main reason is that last October, I accepted a transfer and promotion within the state government to a new position. I am no longer working on ASP.NET Core or Blazor. I inherited maintenance on a legacy ASP.NET 4.8 Webforms website.

While it was a step backward in technology stack, it was like putting on an old pair of jeans. It just fits. So, while I won't be posting too much about the ever-changing world of Webforms, I will keep posting about my other interests. Perhaps the other authors on the site will step forward and start posting, as well.

Honestly, it feels really good to be developing code in Webforms again. It's super easy and it's well-known. Since it will be supported for quite some time, I'm not too worried about migrating just yet. I do have my eye on the industry so that I won't be caught off guard when Microsoft finally stops supporting .NET 4.8, but that isn't concerning me right now.

I enjoyed my time with Blazor, but I have to admit that it was very scary writing new code on such a new and unproven platform. It was hard to make software deliverable promises when you weren't even sure that the technology would be ready for production use.

Another benefit of the new position is that we're using SQL Server instead of Oracle. That's a much better environment for me as I enjoy using it much better. Oracle was a pain to use and program and had poor EF support. Though, I'm not currently using EF, yet, as the app I maintain was written to use ADO.NET Data Tables and stored procedures.

Like I said, it's a comfortable job and there are very few unknowns in my day. When my boss asks for a new feature, I let him know how long it will take me, head back to my desk, and knock it out in record time. It's nice.