Bismillah.

Let's go ahead and continue, I want to share with you guys, about the advanced swift topics.
I've got planning to go with these topics;

Introduction to OOP:
- Basics of OOP
- Pillars of OOP

Introduction to POP:
- Basics of POP

Software design principles:
- Composition Over Inheritance
- SOLID Principles
- Single Responsibility Principle
- Open/Closed Principle
- Liskov Substitution Principle
- Interface Segregation Principle
- Dependency Inversion Principle

Gang of Four Design Patterns:
- Creational Design Patterns
- Structural Design Patterns
- Behavioral Design Patterns

and much more.

Introduction to OOP:
- Basics of OOP
- Pillars of OOP

#swift #OOP

https://telegra.ph/INTRODUCTION-TO-OOP-01-14

Is POP Better Than OOP?

Protocol Oriented Programming
Introduction to POP.

https://telegra.ph/INTRODUCTION-TO-POP-01-21

I also want to share iOS interview questions and answers, stay tuned for more.

#QA
Does a protocol can be inherit from other protocol?
- Yes!, Protocol types can inherit from other protocols, but not from other named types.
named types: (Class, Struct, Enum, Protocol)

@software_efficiency

#QA
Does swift support multiple class inheritance?
- No. Class types can inherit from a single superclass and conform to any number of protocols.

@software_efficiency

#QA
What’s a Design Pattern?

- Design patterns are typical solutions to commonly occurring problems in software design. They are like pre-made blueprints that you can customize to solve a recurring design problem in your code.

You can’t just find a pattern and copy it into your program, the way you can with off-the-shelf functions or libraries. The pattern is not a specific piece of code, but a general concept for solving a particular problem. You can follow the pattern details and implement a solution that suits the realities of your own program.

A pattern is a more high-level denoscription of a solution. The code of the same pattern applied to two different programs may be different.

@software_efficiency

next blog posts will be on design patterns, until then I will try to give a brief intro with such #QAs

add your friends or share the post to your channel, stay tuned for more.

@software_efficiency

Program to an Interface, not an Implementation


https://telegra.ph/Program-to-an-Interface-not-an-Implementation-02-08

Hey, nice to see you again after Ramadan. are you here?)

Later == Never
😎☝️
we'll continue.

#advice
Don't try to remember stuff. Brain is bad at remembering. It's rather good at processing.

today I'll tell you the truth)

How I make all this content:

1. I learn something small and new
2. I write it down on paper
3. I organize the thought
4. I publish it
5. Repeat

Step 1 is huge.

When I'm learning, it's easy to make content, and repeat to myself dive in deeper.

Inputs == Outputs.

#advice
Comments are an apology, not a requirement. Good code mostly documents itself.

@software_efficiency

#advice
Functions should only do one thing - this is by far the most important rule in software engineering. When you can isolate a function to just one action, they can be refactored easily and your code will read much cleaner.

@software_efficiency

Understanding the SOLID Principles: Building Better Software Design

https://telegra.ph/SOLID-Principles-05-17

#QA
What is the difference between a class and an object ?
- A class is a blueprint or template that defines the properties and behaviors of an object. An object, on the other hand, is an instance of a class. You can create multiple objects based on a single class definition.

@software_efficiency