Karumi Mobile Architecture Open Training
It's time to face new challenges, exploring new techniques to improve as software engineers. Practice makes perfection and it's time to improve our development skills using real world scenarios.
Would you like to improve the quality of your apps by improving your engineering skills? To learn how to design software you can truly feel proud of. How to design structured software easy to scale up, evolve, maintain and test?. If you would like to create a robust architecture based on the most important patterns and principles of the software design, then this is your event :)
Today the Karumi Team introduces to you our first Karumi Mobile Architecture Open Training! We have designed a training based on years of experience building great apps for Android and iOS. 4 training sessions of 4 hours each one to improve our software engineers skills in terms of architecture, software design patterns, and principles.
This course covers the following topics during the 16 hours of training.
- Coupling vs Cohesion.
- Single responsibility principle.
- Open close principle.
- Liskov substitution principle.
- Interface segregation principle.
- Dependency inversion principle.
- Software design patterns for mobile.
- User interface patterns: MVP vs MVVM vs MVC.
- Clean architecture.
- Unit testing.
We couldn't configure Eventbrite to use different dates so don't pay attention to the Eventbrite date. The training dates are:
10/3/2017 from 15:00 to 19:00.
11/3/2017 from 15:00 to 19:00.
17/3/2017 from 15:00 to 19:00.
18/3/2017 from 15:00 to 19:00.
Prerequisites & requirements
Pick any language used for mobile development such as Swift or Java, laptop and you're all set. A basic knowledge of OOP is desirable.
The minimum number of attendants are 6. If there are no 6 attendants the event will be canceled and the ticket refunded.
The maximum number of attendants are 18. This guarantees the quality of the lessons.
If you have any doubt about the training or the training outline send us an email email@example.com