Udemyallpt

Princípios S.O.L.I.D aplicados no Swift

Swift SOLID principles course. Learn object-oriented design for robust & maintainable Swift code. Improve your app development skills!

4.6(280)
2,369students
30m
Bruno Faganello
Bruno FaganelloiOS Developer

Course Content

Princípios S.O.L.I.D aplicados no Swift is an all-levels Udemy course taught by Bruno Faganello. It runs 30m and is taught in Portuguese. Learners rate it 4.6 out of 5 from 280 reviews, with 2,369 students enrolled. It is free to enroll, first published March 2020.

SOLID: Master Clean Code with These 5 Principles

SOLID is an acronym coined by Michael Feathers. It's a powerful tool for developers aiming to write better, more maintainable code. The acronym represents five key principles of object-oriented programming (OOP) and code design, originally articulated by Robert C. Martin, also known as Uncle Bob, in his influential article, "The Principles of OOD."

Understanding and applying SOLID principles can significantly improve your software development process. These principles guide you in creating code that is:

  • More Readable: Easier to understand and work with.
  • More Maintainable: Simpler to modify and update over time.
  • More Flexible: Adaptable to changing requirements.
  • More Reusable: Components can be used in different parts of the application or in other projects.

Here's a breakdown of the five SOLID principles:

  • S - Single Responsibility Principle: A class should have only one reason to change. This promotes focused functionality and reduces the risk of unintended side effects.
  • O - Open/Closed Principle: Software entities (classes, modules, functions, etc.) should be open for extension but closed for modification. This means you should be able to add new features without changing existing code.
  • L - Liskov Substitution Principle: Subtypes should be substitutable for their base types without altering the correctness of the program. This ensures that inheritance is used correctly.
  • I - Interface Segregation Principle: Clients should not be forced to depend on methods they do not use. Favor multiple specific interfaces over a single general-purpose interface.
  • D - Dependency Inversion Principle: High-level modules should not depend on low-level modules. Both should depend on abstractions. Abstractions should not depend on details. Details should depend on abstractions. This reduces coupling and improves testability.

By embracing SOLID principles, you'll write code that is more robust, easier to test, and ultimately, more valuable in the long run. SOLID is a cornerstone of good software design and a crucial skill for any aspiring or experienced programmer.

$ whoami — the devs behind tutorialsearch.io

Need a web app built? Hire the team behind TutorialSearch.io

We ship fast, production-grade full-stack apps (Next.js, React, edge infra) — the same stack that powers this site.

5.0(3,882)
47h 38m
intermediate
4.9(399)
17h 47m
intermediate
4.9(2,275)
41h 42m
intermediate

Solid Works para Iniciantes

by Gustavo Bissi Pimentel

4.9(34)
7h 37m
all