Gabriel's Blog
Software-Architecture
-
Explain REST using Trello
Software-Architecture ·The goal of this article is to analyze a real world RESTful application and explain how it adheres to the 5 REST restraints.
-
Product Lines and Product Families
Software-Architecture ·Producing software has costs that can be reduced with code reusability. Lets talk about how the creation of “Product Lines” can help you achieve this.
-
Conway's law - How Organization Structure affects Software Architecture
Software-Architecture ·Lets understand how the organization structure can affect the way the system is developed.
-
Using ATAM to Analyze and Evaluate Architecture
Software-Architecture ·Software development is becoming more complex over the years. Let’s talk about how the Architecture Trade-offs Analysis Method can help to validate the architecture and and expose hidden risks to the Stakeholders.
-
Software Architecture Quality Attributes
Software-Architecture ·When we are talking about evaluate the quality of a Software Architecture, there are some questions that cannot be answered by Design Patterns and Principles or how the elements in the architecture interact each other.
-
Software Architectural Styles
Software-Architecture ·A brief overview about the main software architectural styles and why and when we use them.
-
Kruchten's 4 + 1
Software-Architecture ·The Kruchten’s 4 + 1 technique consists to represent how a system should be implemented by dividing it in 4 different views that are discovered through some business Scenarios or “Stories”.
-
The 23 Design Patterns you must know
Software-Architecture, Design-patterns ·Based on a famous book I will try to simplify and give examples of the 23 famous design patterns that can help your daily work as developer.
-
A brief overview about Software Design and Software architecture
Software-Architecture ·What is Software Design and Architecture? How they relate and differ each other?
-
Model Checking, What it is and why to use it
Software-Architecture ·After finish the implementation of the so (or sometimes not) desired system, how do you know that it is (and behave) exactly as expected? Requirements change, people can forget, communications problems occur even in the best companies.
-
Software Architecture Design Principles
Software-Architecture ·There are 4 important Design Principles to guide architects when modeling software. They are the CoSICi principles. I have invented this word to help me out memorize them! So far it is working and I would like to share it!
-
Object Modeling Principles
Software-Architecture ·There are 4 important Principles when modeling objects! They are the ADEG. Yes, as always I have invented a word to memorize them! Lets talk about them.
Android
-
Emulate Android on Android Studio 3 using Mac OSX El Captain 10.11.6
Android, MacOs ·If you are having problems to emulate Android using Mac OSX El Captain 10.11.6, may this can help you.
MacOs
-
Emulate Android on Android Studio 3 using Mac OSX El Captain 10.11.6
Android, MacOs ·If you are having problems to emulate Android using Mac OSX El Captain 10.11.6, may this can help you.
Design-patterns
-
The 23 Design Patterns you must know
Software-Architecture, Design-patterns ·Based on a famous book I will try to simplify and give examples of the 23 famous design patterns that can help your daily work as developer.
Design-Principles
-
Liskov Substitution Principle - LSP
Design-Principles, SOLID ·Lets talk about Liskov Substitution Principle and how inheritance should be implemented. Yes, we are talking about the “L” from SOLID Design Principles.
-
Open / Closed Principle - OCP
Design-Principles, SOLID ·The Open/Close Principle says that a class must be open for extension, but closed to change. Let’s take a look on it.
-
Interface Segregation Principle - ISP
Design-Principles, SOLID ·A class should not be forced to do what it does not do. What? Yes, the way you built interfaces can cause this side effect.
-
Dependency Inversion Principle - DIP
Design-Principles, SOLID ·Avoid making classes depending on concrete class to reduce coupling. Reduce the maintenance effort and risk of your system.
-
Law of Demeter - Least Knowledge Principle
Design-Principles ·A class should know as less as possible about other classes implementation. There is a law for it!
-
Code Smells & Anti-patterns
Design-Principles ·Here a brief list of some code smells and what to do to get ride from them.
SOLID
-
Liskov Substitution Principle - LSP
Design-Principles, SOLID ·Lets talk about Liskov Substitution Principle and how inheritance should be implemented. Yes, we are talking about the “L” from SOLID Design Principles.
-
Open / Closed Principle - OCP
Design-Principles, SOLID ·The Open/Close Principle says that a class must be open for extension, but closed to change. Let’s take a look on it.
-
Interface Segregation Principle - ISP
Design-Principles, SOLID ·A class should not be forced to do what it does not do. What? Yes, the way you built interfaces can cause this side effect.
-
Dependency Inversion Principle - DIP
Design-Principles, SOLID ·Avoid making classes depending on concrete class to reduce coupling. Reduce the maintenance effort and risk of your system.