Author: David Harrison
-
Attempting to address memory fragmentation in node.js with jemalloc
Continuing our investigations into our memory problems with our node.js servers, we found several references that indicated some people had had success solving random memory leak problems with jemalloc, a replacement for the default glibc memory allocator. This seemed like a fairly easy and low risk change so we thought we’d give it a go…
-
Shape Up – What does ‘get one piece done’ really mean?
We’re now about six months and ten projects into developing products using Shape Up as a primary framework. One of the chapters in the book is titled Get One Piece Done. We’ve tweaked our own internal process for getting one piece done throughout the projects we’ve completed. Some ideas went well, others not so much.…
-
Adding ‘One Key Thing’ to Shape Up Pitches
We’ve just wrapped up our second cycle of Shape Up. This cycle we moved from teams of three developers to teams of two. This change resulted in more parallel projects, naturally reducing the time that a PM could spend with engineers. Knowing this, and wanting to stay true to the goal of ‘Handing over Responsibility’…
-
Investigating node.js memory leaks
For a while now, we’ve been battling some performance problems with our node.js backend. We’d see some parts of our application start slowing down, and we’d get reports from internal users that everything was taking longer and longer. It was frustrating as when we attempted to replicate it, we often couldn’t see it – most…
-
Adopting Shape Up
Our development and product team are now in our first cool down period after one successful cycle of Shape Up. Not wanting to count chickens too early, we learned a lot in implementation. I wanted to share the practical reality of transitioning our team to Shape Up. I will be candid where needed in the…