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

The Power of Plain Text Keep knowledge in plain text. All software becomes legacy as soon as it is written. Mind the difference between human readable and human understandable. Shell Games...

The Essence of Good Design Good design is easier to change (ETC) than bad design. ETC is a value, not a rule. Always ask yourself: is it ETC? DRY - Don’t Repeat Yourself - The Evils of Dup...

1. It’s Your Life: You have agency. Do it!!! Think beyond the problem. Consider the bigger picture. Take responsibility of the code. 2. The Cat Ate My Source Code The greatest of all w...

User Directory - Design Document v1.0 Domain Description Employee directory system demonstrating database indexing optimization through a relatable, intuitive interface that users expect to be fa...

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