It’s time to begin the development phase of a project. The needs have been identified, and the workflow design is complete. Now it’s time to create the initial set of stories for your backlog. Where do you start? How do you write individual stories? How do you even decide what those stories should be?
Much of TypeScript’s flexibility comes from its support for generics. They’re great for building up reusable abstractions so that you can share the “how” across your codebase even as the “what” varies significantly. In this post, I’ll describe a limitation that recently got in my way, and how I worked around it.
There are hundreds of methods for planning workshop activities. In fact, one of my favorite resources is Vijay Kumar’s 101 Design Methods. By combining these methods, designers can create engaging workshops that bring people together to solve problems in just a couple of hours or over a few days. Regardless of how long the workshop […]
When I came to Atomic nearly five years ago, I joined the largest development team I had ever known. We had four developers from Atomic and two from the client working directly with us, as well as the client’s QA staff, an operations engineer assigned to our team, and the client’s software architect checking in.