I love Rails, but the recommended way to work with callbacks is a set of terrible practices for building a real app.
The best way to help someone come up to speed in skills and methodologies is to work directly with them, side-by-side. Pair programming is the perfect chance to nudge people into g
Great programmers are definitely as lazy as possible. From our high-level process to our low-level improvements, these practices help make us all as efficient as we can be.
We came up with a nice little Either pattern for returning success or errors. By using a simple isError helper, we can prove to Typescript what result we have and maintain type saf
At this year's Atomic Games, we built AIs to play our in-house RTS "Space Battle 2: Resource Collectors." We had so much fun, we decided to open source it.
A Queue isn't always what we want. So, how can we build our own primitives that are still nice and Thread safe? Mutex + ConditionVariable + data