This is a short introduction into Dependency Injection for those who are new to dotnet core and C#, with an attempt to explain what it is, and how it works.
Applications feel more optimised when their binaries, or set of binaries are small. With dotnet core 3.0 there are some features built in that help facilitate this.
Something that annoyingly does not come as standard in the dotnet core console application template, and, it is not documented anywhere with Microsoft is: appsettings.json.
This comes as standard with ASP.NET Core applications, but no other applications, and the thing is, it is very simple to add to any dotnet core application.
Everybody has heard of the term “microservice”, but not many people know what they are, how they work, or how to implement one.
Many people think they are a complex system that needs a lot of complex setup and management. In fact, they are a very easy way
to remove heavy lifting from your web frontend to a more appropriate place.
Something that we all know is that there is a blame culture in business.
Something that not many people know is that we don’t need a blame culture in business.
For many developers, the normal 9 - 5 shift does not really apply.
Development is a creative job, and you cannot force more creativity from more hours.
When developing applications for Windows, even Windows 10 or some flavour of Linux or BSD, you pretty much have free reign over what you want to do. When it comes to Android, iOS and Mac OSX, it is a different story.
I have just spent the last 3 hours trying to figure out why only ever 3rd file would upload (and then files would only randomly upload) and i continued to get UPLOAD_ERR_PARTIAL. It turns out UPLOAD_ERR_PARTIAL can be caused by the header Connection: Keep-Alive.