Pinned Loading
-
Caching as an After-Thought
Caching as an After-Thought 1# Caching as an After-Thought23What happens when the speed of data access code and requests to the data store puts a cap on the total number of requests our apps can
4handle? We have a bunch of options of course, but they are costly and intrusive. Partitioning the data store is a delicate operation
5and requires a skilled DBA. Memory caching using local or distributed caching stores is awesome, of course, but can be time consuming.
-
ifs-and-buts.md
ifs-and-buts.md 1## Are IFs Bad For You?23No, they're not bad per se. However, in a world where the monolithic codebases of old have [increased to massive size](http://www.informationisbeautiful.net/visualizations/million-lines-of-code/), calculating [McCabe scores](https://en.wikipedia.org/wiki/Cyclomatic_complexity) shows us that as code ages nesting depth increases. Why is this? Well, what started as one little ```if```, or just a minor ```switch```, can quickly grow to become an unwieldy monster to maintain. Let's take the following piece of code as an example:
45```csharp
-
-
-
skiss-project/framework
skiss-project/framework PublicA .NET framework for simple, kind of interactive, system specifications.
C#
-
guard-statements
guard-statements PublicStuff you would normally put in a "Validation" assembly.
C#
Something went wrong, please refresh the page to try again.
If the problem persists, check the GitHub status page or contact support.
If the problem persists, check the GitHub status page or contact support.

