> For the complete documentation index, see [llms.txt](https://docs.shiftiq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shiftiq.com/contributors/conventions/video-recommendations.md). # Video recommendations ## Dependency injection: the best pattern Dependency injection allows code to receive its dependencies from the outside rather than constructing them internally. It is a simple pattern that enables highly configurable and testable software. Recommendations include: * Inject service-specific implementations behind common interfaces to simplify configuration and reduce branching logic. * Use factories to construct dependencies based on runtime context; avoid complex conditionals in core request handling code. * Design systems for testability by injecting mocks and fakes during testing; allow parts of the system to be validated in isolation or in integration. {% embed url="" %} *** ## Why I don't use the "else" keyword in my code Nick explains why he intentionally avoids using the `else` keyword for control flow, because the result is cleaner, more maintainable, and better-structured code. He recommends: * Eliminate unnecessary nesting by returning early from functions. * Prefer switch statements and method extraction to clarify control flow. * Refactor code toward single-responsibility and open/closed design to make additions easier and safer. {% embed url="" %} *** ## Clean code with horrible performance Many "clean code" practices, often recommended for maintainability and readability, can drastically harm runtime performance — in some cases by factors of 10x to 20x. Muratori concludes that while maintainability is important, performance should not be sacrificed for dogmatic adherence to clean code rules. He recommends: * Avoid polymorphism when performance matters. * Prefer explicit knowledge of data internals when appropriate. * Be critical of abstract "clean code" prescriptions unless performance trade-offs are clearly understood. {% embed url="" %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.shiftiq.com/contributors/conventions/video-recommendations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.