Decided to use some spare time to revisit Blazor, particularly getting it to work with OData. Taking my inspiration from Hassan Habib and his Enabling Pagination in OData post I wanted to build upon that and modernise the approach slightly by implementing client side Blazor and bringing some of the goodies from NET5 by using a code behind approach for example.
There seems to be a lot of crappy internet adverts about these days. Normally I scroll through them and they don’t register but recently they seem to be incredibly cheesey and a little sinister. It’s almost like having an advert of someone with a passport or driving licence is supposed to make it more trustworthy or something. Here’s a delightful section I clumped together for your enjoyment. Note that the adverts are screenshots and I’m not affiliated with any of these!
This article describes out to resolve the problem where you’re unable to place the tracy back into the De’Longhi coffee machine.
A few weeks back I noticed that a part of the code that I’d been working on for over a year seemed to be growing in size and needed to be addressed in order to avoid future headaches and pain. The code is by no means monolithic but of a significant size to be a thing in it’s own right and not a quick 15 minute fix. I could see that action was needed in order to support future maintainability and scalability. Here’s 7 tips for refactoring…