Endjin - Home


Explicit interface implementation

by Ed Freeman

Two of the main use-cases for explicit interface implementation are: 1. to hide members of the interface in a class which inherits from that interface, and 2. to work around the scenario when a class is inheriting from two interfaces which share a member of the same name. Take a look at this blog to go into more depth about each of those scenarios.

A good test suite should validate behaviour across your code base, testing as many edge cases as reasonably possible. A common “edge case”, is passing a null value when a value isn’t expected to be null. In Specflow, all values used in scenario examples are treated as strings, so it isn’t possible (by default) to pass in a null value. However, using “Step Argument Transformations”, we can achieve the desired behaviour. Read this blog to learn how this can be implemented.

My first month as an apprentice at endjin

by Ed Freeman

Structured apprenticeships provide a great way to build skills whilst getting real-life experience. Endjin’s apprenticeship scheme has been refined over years, with an optimal mixture of training, project work, and exposure to commercial processes – a scheme which is designed to build strong foundations for a well-rounded Software Engineering consultant. This post explains the transition from university to an apprenticeship at endjin, including the types of work an apprentice could end up doing, and some examples of real-life learnings from a real-life apprentice.

In this post, Mike Larah discusses how to ensure your C# collections are thread-safe, only run-once, and are lazy-loaded.