just hold data. Data classes Function Price Getters and Setters 0 Lei equals() & hashCode() 0 Lei toString() 0 Lei componentN() 0 Lei copy() 0 Lei TOTAL FREE!
= actor.firstName.length(); int lastNameLength = actor.lastName.length(); int fullNameLength = firstNameLength + lastNameLength; sout("The total length of the full name is " + fullNameLength);
For a nicer impact make a function not bigger than 4 lines of code. • The indent level of a function should not be greater than one or two. • The blocks within if, else and while should be one line long. • A long descriptive name is better than a short enigmatic name. About Functions
(monadic) ◦ A good number of arguments • Two (dyadic) ◦ A good number of arguments • Three (triadic) ◦ Should be avoided where possible. • More than three (polyadic) ◦ Maybe we should wrap the arguments in a new type Function arguments
leaks with backwards-compatibility baked in. No boilerplate code You can focus on what makes your app great. Reduce fragmentation Reduce complexity with libraries that work consistently across Android versions and devices.
Question or Request I observed this function has 60 lines. This makes it difficult for me to understand the logic. I suggest extracting a part of the code into other functions and give them relevant names. * Defined by Lara Hogan
(technical or work habits) Threats Impediments at work, changes, weaknesses lead to threats Strengths Advantages like: skills, achievements, certifications, education, connections Opportunities Events, conferences, new role/project, industry growing
weekly review Quantity Goal Quality Goal Result 1 Kotlin Koan per week Learn specific features of the language => 1 feature / week Exercise often and on a set of Koans proposed by JetBrains Write one detailed article about a specific topic per month Improve my writing skills and learn by teaching to others Learn new things, help the community and get feedback 3 code samples runned per week Get a repo with samples that I can re-check (use ktlint) Gain real experience in programming using Kotlin
=> what contributed to my success? ◦ NO => what obstacles did I encounter? • If I were to rewrite a goal achieved in full, what would I change? • What have I learned that might alter my approach to the next cycle’s OKRs? • Understand what is your WHY • Repeat the process Retrospective
your learning style • Focus on your strengths • Search for resources and organise them in a plan • Start learning and track your progress • Focus to understand how the things are working • If it is difficult, take a break, and start over My summary in 7 steps