How I Write Posts

This is a non-technical post, I wanted to explain a few things about my blogging.

First, I usually write in British English. This is essentially because I work (and have worked in the past) for British companies, so this is the variant of English that I use daily. This has no other meaning than this.

Second, I usually prepare my posts for a long time before they are actually published, but, still, things happen and I sometimes get things wrong, or wish to add/clarify something. So, I frequently make amends to posts, and sometimes I even signal them.

My interests include .NET and ASP.NET Core, databases (SQL Server, Elasticsearch), JavaScript, and web/distributed development in general. I probably won't write about Java, Go, or Python.

I tend to avoid what I feel is unnecessary details, such as using directives, and the likes, and also generally keep error handling to the minimum. This doesn't mean that I don't care about it, it's just that it's usually not the point of the post.

Sometimes I create series of posts on some topic, such as pitfalls, architecture, and so on. I usually (on the old blog) create a page to list them all together and keep updating it as the list grows.

I don't have the time, the skills, or the patience, to create videos, and I am really not good with images, but sometimes I include them. Whenever they weren't produced by me, I indicate the source.

I try to tag all posts with as many tags as I find appropriate, I really like to be able to find things through tags.

I always strive to include useful links to reference documentation from authoritative, usually from Microsoft, Mozilla, or Wikipedia (yes, I do find Wikipedia reliable, at least, for the references I'm interested in), or to other posts of mine.

Some of my posts have related code either in GitHub or Nuget, or both. I always mention the links at the end.

When a post is finished, I post the link on LinkedIn, X (I know, I know...), and BlueSky. This one won't be, as it is not really that important, it's more for followers of my blogs.

Always allow comments, but I do review them, as I get a lot of spam.

And this is basically it. Always happy to discuss these or any other topics, so feel free to drop me a line!

Comments

Post a Comment

Popular posts from this blog

ASP.NET Core Middleware

Image
Introduction This post is another of those "back to basics", still, there was one thing or two that I feel were not properly discussed elsewhere, hence this post. The ASP.NET Core Pipeline and Middleware You may know that ASP.NET Core defines a pipeline. This is where the incoming requests are processed and the response submitted. Each component in the pipeline - a middleware - can do things with the message (the request), such as check if it is authenticated and have rights to access the requested resource, turn the request into an MVC-style controller and action invocation, log it, and what not. You can read more about it here . The ASP.NET Core pipeline, from Microsoft The order by which the middleware is added to the pipeline matters. For example, the authorisation middleware must come after the authentication one, static files must come before routing, and exception handling must come before everything. The middleware order, from Microsoft A middleware is just a piece of...
Read more

.NET Cancellation Tokens

Introduction Cancellation tokens in .NET were introduced as part of the  .NET 4 Cancellation Framework . Essentially, it is a standard, cooperative, way to request for the cancellation of the execution of an operation. By cooperative it means that the code that uses it must abide to some rules, as opposed to the cancellation just stopping (killing) the execution. One example of cancellation is, on a web app, when the client closes the connection while the server is performing some long operation. In cases such as this, we may want to abort the operation, as we are not sending the results anywhere (or not, as we shall see). Because of this, ASP.NET Core allows us to add a parameter of type  CancellationToken  to our asynchronous actions, it is automatically associated with the client and is therefore signalled when the client connection is closed. A  CancellationToken  is, essentially, behind the scenes, a ManualResetEvent . Throughout this article I will either ...
Read more

Audit Trails in EF Core

Introduction Audit trails is a common feature in database systems. Essentially, it's about knowing, for every table (or some selected ones), who created/updated each record, and when the creates/updates happened. It can also be useful to store the previous values too. Some regulations, such as SOX , require this for compliance. There are some libraries that can do this automatically in EF Core , and there's also the Change Data Capture in SQL Server (and possibly other databases too), of which I wrote about some time ago, but, hey, I wanted to write my own, so here is EFAuditable , my library for doing audit trails in EF Core. This one is designed with some extensibility in mind, so, please, read on. Scenarios EFAuditable  allows the following scenarios: Entities marked for auditing will have the audit columns added and persisted automatically to the database, on the same table Entities marked for history keeping will have their old values (in the case of updates or deletes) ...
Read more