Find your internet twin!

Here I provide an example using intrusive lists as containers and where data chunks belong to two lists at the same time.

These hashes are usually stored in the database and used for user authentication.

First is what we usually want, second is what we doomed to deal with all the time.

When reading the object back from the Parcel, you do not get a new instance of the object, but rather a handle that operates on the exact same object…

For example lets have a directory called dir and we want to make an archive with its content.

I'm going to create a simplified database consisting of one table with million records with Entity Framework Code First.

It can be simplified if everything we want is just to report the errors instead of doing something about them after the failed call:

But following the reasoning that Robert C. Martin gave when explaining single responsibility principle (close cousin to principles of coupling, coh…

Unlike relational database, structure of documents in the collection does not have to be identical.