SOLID Programming: Interface Segregation Principle in Unity

ofrecido por
En este proyecto guiado, tú:
1.5 hours
Principiante
No se necesita descarga
Video de pantalla dividida
Inglés (English)
Solo escritorio

Programming of any kind, including in game-development, can get complicated as the size and scope of a project increase. Investigating bugs and expanding the code with new functionality can be almost impossible if the code-structure is not well-thought-out. In this one-hour, project-based course, we will cover the fourth principle of "SOLID" programming: Interface Segregation Principle ("ISP") states that classes should not be required to implement methods or properties it doesn't use. This means a monolithic interface is usually inefficient and should be broken into its functional parts. In the project, we will create some "typical" code that is fairly common in game-development, and then restructure it to become compliant with ISP. This project is part four of a five-part series on SOLID Programming principles, which are: - Single Responsibility - Open-Closed - Liskov's Substitution - Interface Segregation (this guided project) - Dependency Inversion Each of these guided projects stands on its own, but for a full understanding of good coding practices, completing all five guided projects (in order) is recommended.

Habilidades que desarrollarás

  • Video-game Development

  • C sharp (C#) Programming Language

  • Unity 3D

  • Unity

  • Application development

Aprende paso a paso

En un video que se reproduce en una pantalla dividida con tu área de trabajo, tu instructor te guiará en cada paso:

Cómo funcionan los proyectos guiados

Tu espacio de trabajo es un escritorio virtual directamente en tu navegador, no requiere descarga.

En un video de pantalla dividida, tu instructor te guía paso a paso

Preguntas Frecuentes