As a developer you probably know the DRY abbreviation already: Dont Repeat Yourself.
This is one of the better known principles, and it’s fairly easy to comprehend too: Don’t implement the same logic twice.
However one place where most people slip with DRY, is the switch statement.
Our content server occasionally responds 503 Server Fault on all requests for about a minute or so.
This seem to occur at random intervals for no apparent reason.
After countless hours we finally found the solution…
This is the second of a five part series, where I go over the 5 principles which make up the SOLID principles by Robert C. Martin.
The second one is O: Open/Closed Principle (OCP)
This principle states that classes should be open to extension, but closed to modification.
This is the first of a five part series, where I go over the 5 principles which make up the SOLID principles by Robert C. Martin.
The first one is S: Single Responsibility Principle (SRP)
This principle states that a class should only one have responsibility, which is usually interpreted as having a single “reason to change”.
I recently had an issue with a website timing out a ton of stored procedures because of deadlocks.
Looking back in the error log, I could see it all began when it failed inside the given SP with an arithmetic overflow.
This would normally be no big deal – however this time, it occurred inside an explicit transaction…
When using multiple threads in an application, you often want to be able to signal threads, to ensure a high level of responsiveness.
There are multiple ways to do this, but here’s what I feel is the best solution.
I often come across some good articles, so I decided to start sharing them.
This time I’ve got a great article about ASP.Net Webforms Viewstate, and a thorough article about dot.net 4.0 Code Contracts.
Most databases will eventually make use of stored procedures.
However out-of-the-box there’s no “execute SP” role to assign your SQL user.
Here’s how to create the role and grant it the proper access.
DaLi is an ORM (Object-Relational Mapping) based around dot.net Reflection.
Whilst Reflection is inherently slow, I make use of quite a bit of caching to avoid any severe overhead. In fact DaLi performs at around 97 % of hand written ORM code.
One of our servers started showing this error: “Event log service is unavailable. Verify that the service is running.”
Fixing it proved quite simple, after a lot of searching on google…