One of our design philosophies at Blueprint Power is that you don’t spend too much time optimising code early on but instead focus on writing maintainable code with maintainable languages. More often than not, I have watched teams concentrate on picking the fastest language or improving the processing by some percentage instead of defining a solid data model and design pattern for the code. This hunch has served me well throughout the years. More often than not, by the time the performance ...
