Advanced iOS Engineering

This program aims to help Junior engineers to have the right Engineering mindset, so they are able to write great quality code both for the development team and also for their Engineering Career. Day 1 will focus on some Engineering best practices terms while Day 2 will focus on technical tools provided by Apple and Xcode.

Program Objective: 
* Participants have the right mindset in creating great quality Code
* Participants are able to create a list of recommendations for the next code improvement
* Participants able to improve and analyze their code readability
* Participants implement one of the SOLID Principle
* Participants able to write good quality and tested MVVM code
* Participants able to use multiple debugging tools
* Participants understand the importance of platform design in Engineering


Certificate of completion (supplied by PasarTrainer)

Training Material

* TDD Practices in order to achieve single responsibility of a Class, example will be used on ViewModel class
* Write and implement a unit test for the View Model
* Best Practices in debugging Using LLDB, Breakpoint, UI Debugger, CPU & Memory Graph, Conditional compilation
* Understand common Memory Issues in iOS Development
* Learn about ARC and development practices on how to prevent it
* Use memory instrument
* Use Zombie process Tracker


This module will talk about several approaches to improving code efficiency and reliability with debugging approach in Xcode, common issues in app development, and writing Test.

Module 5: Efficiency and Reliability in iOS Engineering

* Explain Individual Worksheet during the training. This worksheet will be used to get new knowledge from the participant and an action plan after the training. This document can be used by the senior engineer to be reviewed, so they can make appropriate action


Explain why it is important to write good quality code that is readable, maintainable, efficient, and reliable. Participant able to understand that writing code is not just making the feature work.

Module 1. Opening Module: Beyond Code Mindset

* The given codebase will raise these issues: Asset Memory issue (memory debugger), Too much print function (Use breakpoint / LLDB), Unlickable button (Use UI Debugger), and Leak issue (Instrument)
* After the test, participants will need to write a recommendation on their individual sheet



Participants will be asked to improve the issue in the given codebase.


Find the culprit

* Understanding of code readability in an engineering team which covers Fundamentals, Team & Individual Productivity and Easier Future Maintenance 
* Approach for better code readability through clear and fluent usage, Using well-known terminology, Maximizing self-explanatory Swift syntax, and Creating Xcode Markdown 


This module will talk about how to improve the code, so it will become more readable using several universal naming conventions, explore some Swift Feature that allows to do it, and create custom convention according to the current team needs.


Module 2: Improve Code Readability

* Understand the importance of platform design knowledge in engineering
* Participants will learn several design considerations and why it is important for engineers to have knowledge about iOS Components. Type of View Presentations and Touchscreen
* Gestures
* How to read the Human Interface Guidelines and How to get developer resources from them
* Using Xcode Accessibility Inspector




Understanding the importance of Human Interface Guidelines as an iOS Software Engineer.

Module 6: Design practices as Software Engineer

* Prepare to open their work repo
* Assign Peer
* Analyze
* Present in bullet point of recommendation
* Each person writes the result of these in their individual worksheet


In this activity, the participants will look through the code that their peer has made, and they will review it using the approach that have been mentioned previously. They need to present it individually to show their reasoning afterward.


Peer Feedback

* Understand the importance of maintainability in code for team and individual
* SOLID Principle Definition and why it matters
* Elaboration of Single Responsibility using MVVM UI Architecture to define every responsibility of UI
* Elaboration of Open/Closed Principle through Discussion that might need an extension in the future and Creating a Payment class that is able to extend 
* Elaboration of the Liskov substitution Principle (LSP) in the Common case of breaking LSP and Approach to not breaking LSP
* Elaboration Interface segregation with critical thinking when creating Protocol and its implementation
* Elaboration Dependency Inversion with Discussion to define some cases where this principle usually arises



This module will talk about the importance of SOLID principle in iOS Engineering and implement it using the MVVM Design pattern.


Module 3: Creating Maintainable Code

* Read the HIG and implement 1 area
* Present it
* After the presentation, participants will need to write a recommendation on their individual sheet 


Participants are able to implement best design practices in 1 Area from HIG.


Presentation: Design Practices Implementation

* Questions will be shown one by one
* Each principle explanation will be provided in the worksheet, so they will read through again and again in each question

A test where there will be several code snippets. Participants will be asked about what principles that code has broken and explain.


 5 Questions that asked for each principle understanding

* Group will be formed randomly or with the seniors' recommendations (2-3 people)
* Presentations: Recommendation and Why
* In each presentation, each person will be asked to take notes on some recommendation that they feel makes sense in their individual Worksheet


Analyze the current code base and give a recommendation using several principles that participants have learned.


Presentation

* What is MVVM trying to solve?
* What needs to be in the View Model
* Several ways to approach it using a delegate, combine, and RX
* Code example: From wireframe to create the whole MVVM


Understand the overview of the MVVM motive and write a good quality MVVM Pattern.

Module 4: MVVM In depth

* Consider using the Solid Principle in mind in terms of adding a new method / class when some functionality is needed in the View Model
* Participant will focus on using a delegate pattern


Participants will be given different kinds of screens with different features, and they need to code them. 
