Microservices and the N+1 Problem One of the big tenants of microservices is that a service owns its data and the only way to access that data is through the service interface. Because of this, one of the first hurdles that any serious system needs to deal with is how to combine data across two [...]
Why Do You Fizz Buzz? Almost every developer has heard of or been asked to implement Fizz Buzz – either in an introductory computer science class or perhaps part of an interview. It’s very basic: you take an integer input, and if that number is evenly divisible by 3, you output “Fizz”, if it is [...]
Understanding Recursion by Understanding Recursion As I was coming up as a developer, I liked to try my hand at short technical challenges to develop my technical and problem-solving skill. These may have been implementations of classic computer science problems like Knight’s Tour or Towers of Hanoi or challenges that I had come across during [...]
A Generic Client for RESTful APIs This morning, our accounting team was doing some regular weekly work bringing in time tracking data from our time tracking tool (we use Toggl) into our back office and invoice systems. As I was passing by, I thought, “This sure would be easy to do if Toggl has an [...]
Software development is hard. Understanding requirements, keeping up with evolving scope, and getting everyone on the same page is difficult enough without developers adding self-inflicted wounds.
SharpEcho is proud to be recognized as a 2018 Cougar 100 company by the University of Houston Alumni Association. The Cougar 100 identifies the world’s top 100 fastest growing companies owned or led by University of Houston alumni.
We’ve leveraged a number of patterns that can help get to that initial release product quickly but doesn’t box us into a design that has to be scrapped when volume exceeds expectation.
Seems like everyone is writing microservices these days and that might be a good thing, if they solve the problems they are intended to solve.
A problem that I’ve noticed with us developers is that sometimes we hear some techie and cool sounding trivia – you know, like “the rain in Spain stays mainly in the plain,” take it as fact, and integrate that fact into our daily dev lives.
Times may have changed since your last hiring spree, and even if they haven’t, when was the last time you examined how successful your process really is for identifying the right kind of developer while weeding out the wrong kind?