Introduction Before talking about software development, let’s shift our domain a little. Imagine a small farm with a single piece of land used by two farmers to grow tomatoes for sale. Two custome...

Overview Flash sale bookstore system demonstrating database race conditions. A single purchase action creates duplicate orders when concurrent requests check inventory simultaneously before either...

The Problem As the Lazy Bird project grew to include three different broken systems (Content Delivery, Product Catalog, and Employee Directory), each system implemented its own version of common U...

Here’s an updated list of broken systems that we can implement on this project. The update is related to the categories. First, we defined it as categories related to domains. Now, they are related...

Domain Description E-commerce product page system demonstrating API call optimization through sequential vs parallel request patterns. This serves as the second broken system in the Lazy Bird Proj...

The first broken system is finally complete. It took slightly longer than expected because I wanted to build a solid foundation for future systems. There was also a lot to learn and adapt along the...

Pragmatic Teams Pragmatic team: Under 10 members. Members come and go rarely. Everyone knows everyone well. Everyone trusts and depends on each other. Qual...

The Requirements Pit No one knows exactly what they want. Our job is to help people understand what they want. Requirements are learned in a feedback loop. Prefer short iterations: one tha...

Listen to your inner lizard. Prototype when stucked. Avoid programming by coincidence. Don’t assume it, prove it (again)! Algorithm Speed Estimate the order of your algorithm. Test yo...

Project Overview The Lazy Bird Project is a repository of intentionally broken but complete systems designed for educational purposes and hiring assessments. Rather than studying problems in isola...