Stop building websites with infinite scroll! 

Summary

It’s pretty easy to differentiate use cases for Result and exceptions. Whenever the failure is something you expect and know how to deal with – catch it at the lowest level possible and convert into a Result instance. If you don’t know how to deal with it – let it propagate and interrupt the current business operation. Don’t catch exceptions you don’t know what to do about. 

Recently I started using Vue and I don’t think I ever want to go back

Adaptation of Design Patterns for Humans to C#  

• Microservices Allow Skill Set Flexibility
  
• Microservices Help Developers with Efficiency
  
• Easy, Less Risky Deployments
  
• Runtime Resiliency
  
• Application Life cycle Flexibility

Let's Build a Simple Database
Writing a sqlite clone from scratch in C 

Design Patterns: Singleton 

This is the first of an eight part series where I am joined by Phil Japikse to discuss design patterns. A design pattern is a best practice you can use in your code to solve a common problem.  In this episode, Phil demonstrates the Command and Memento patterns. 

Episodes in this series:

• Command/Memento patterns (this episode)
• Strategy pattern
• Template Method pattern (to be published 7/20)
• Observer/Publish-Subscribe patterns (to be published 7/25)
• Singleton pattern (to be published 8/8)
• Factory patterns (to be published 8/10)
• Adapter/Facade patterns (to be published 8/15)
• Decorator pattern (to be published 8/17)