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...

Here’s a list of broken systems that we can implement on this project. These are not backlog or roadmap, these are only ideas of broken systems that can be implemented or not. Each of broken system...

Concurrency: when the execution of 2 or more pieces of code act as if they run at the same time. -> Software layer Parallelism: when they do run at the same time. -> Hardware layer Breaki...

Decoupling Decoupled code is easy to change (ETC). Tell, don’t ask. Don’t chain method calls. Avoid global data. If it’s important enough to be global, wrap it in an API. Juggling The ...

You can’t write perfect software. Design By Contract (DBD) Check: Preconditions Postconditions Class Invariants If all prec...

🎯 Project Planning Session Overview We successfully planned the development of the Lazy Bird Broken System 1: Employee Directory - the first broken system in the educational project repository des...