finxter Book: Simplicity - The Finer Art of Creating Software of parts—aficult to 1. YouAin't Going to Need It 2. The Principe of Least Surprise 3. Don't Repeat Yourself 4a 5. Stand on the Shoulders of Giant 6. Use the Right Names 7. Single-Responsibilty Principle 8. Use Comments 9. Avoid Unnecessary Comments 10. Be Consistent i. Test 12. Thinkin Big Pictures 13. Only Talkto Your Friends 14. Refactor 15. Don't Overengineer 16. Don't Overuse indentation 17. Smallis Beautiful 18. Use Metres 19. Boy Scout Rule: Leave Camp CCleaner Than You Found it Algorithmic Theory Pareto Tips Mojoriy ofefecs come —2.-—_‘Figure out your big goalsin ie. from the minority of causes. 3. Look for ways to achieve the same on ‘things with fewer resources * 4. Reflect on your own successes ' oe 'S. Reflect on your own failures: 6. _ Read more books in your industry. teeeeeeeee 7. Spend much of your time i improving an tweaking exiting i! products, yy! 8 Smie. i : 9. _Don' do things that reduce value Stereeeded Maximize Success Meti: ‘Complexity appears in Project Lifecycle Project Lifecycle ee “A whole, made up Cade Development \ if ‘analyze, understand, Processes — = or explain". Social Networks \ d learning & Your Daylife S, Figure out your success metrics. Coe og ‘Simple's Better Than Complex ‘Make Each Program Do One Thing Well Build Prototype First Portability Over Efficiency Store Datain Flat Tex Files Use Software Leverage Avoid Captive User Interfaces is Worse is Better Clean > Clever Code ‘Make Your Code Robust Repair What You Can — But Fail Early and Noisily Write Programs to Write Programs How to Simplify Design? 1. Use whitespace ‘cyclomatic Complexity TRC LL Minimum Viable Product & iM “Merotive Feedback Oe Product (MVP) tcmmey | et 2 minimum vibe > yy sone 0 th Sa | Totworesemeiscode gO ge thats stripped from all features to focus on the core functionality eee aecad “Programmers woste enormous 2 ‘amounts of time thinking about [..) 3. the speed of noncritical part oftheir Programs. We should forget about 4. ‘small efficiencies, say about 97% of 5. the time: "=Donald Knuth 6, Performance Tuning 101 Runtime Complextiy Formulate hypothesis ‘Omit needless features Splittest to validate ‘each new feature Focus on product- market fit Seek high-value and low-cost features ‘Measure, then improve Focus on the slow 20% Algorithmic optimization All hall tothe cache Solve an easier problem version Know when to stop “ro the source code of ultimate human performance” — Kotler Flow Tips for Coders * 1. Always work on an explicit rm @ © © practal cade proiect, Work on fun projects that fulfil your purpose Perform fram your strengths Big chunks of caging time Reduce eistractions: [you can take raw resources and move them from a state of high entropy into a state of low entropy— using focused effort towards the loteainment ofa greater pion. “~~ 3-Step Approach of i Kameadetmsimanis || = peupbomasad 3. Remove features Howto Achieve Flow? JS «6. Sleep alot, eat healthily, A aston een srt Sua teed quay boos and font ype, color als a)nmediteeaback an) SPE UY ona = S__ 8 _ecomistentacossuls | (yGReESRRSRORTTER portage ut ne : eg Str * © Su 2. Apply focused effort ~ EEE tomakert real Seek feedbackfinxter Book: Simplicity - The Finer Art of Creating Software of parts—aficult to 1. YouAin't Going to Need It 2. The Principe of Least Surprise 3. Don't Repeat Yourself 4a 5. Stand on the Shoulders of Giant 6. Use the Right Names 7. Single-Responsibilty Principle 8. Use Comments 9. Avoid Unnecessary Comments 10. Be Consistent i. Test 12. Thinkin Big Pictures 13. Only Talkto Your Friends 14. Refactor 15. Don't Overengineer 16. Don't Overuse indentation 17. Smallis Beautiful 18. Use Metres 19. Boy Scout Rule: Leave Camp CCleaner Than You Found it Algorithmic Theory Pareto Tips Mojoriy ofefecs come —2.-—_‘Figure out your big goalsin ie. from the minority of causes. 3. Look for ways to achieve the same on ‘things with fewer resources * 4. Reflect on your own successes ' oe 'S. Reflect on your own failures: 6. _ Read more books in your industry. teeeeeeeee 7. Spend much of your time i improving an tweaking exiting i! products, yy! 8 Smie. i : 9. _Don' do things that reduce value Stereeeded Maximize Success Meti: ‘Complexity appears in Project Lifecycle Project Lifecycle ee “A whole, made up Cade Development \ if ‘analyze, understand, Processes — = or explain". Social Networks \ d learning & Your Daylife S, Figure out your success metrics. Coe og ‘Simple's Better Than Complex ‘Make Each Program Do One Thing Well Build Prototype First Portability Over Efficiency Store Datain Flat Tex Files Use Software Leverage Avoid Captive User Interfaces is Worse is Better Clean > Clever Code ‘Make Your Code Robust Repair What You Can — But Fail Early and Noisily Write Programs to Write Programs How to Simplify Design? 1. Use whitespace ‘cyclomatic Complexity TRC LL Minimum Viable Product & iM “Merotive Feedback Oe Product (MVP) tcmmey | et 2 minimum vibe > yy sone 0 th Sa | Totworesemeiscode gO ge thats stripped from all features to focus on the core functionality eee aecad “Programmers woste enormous 2 ‘amounts of time thinking about [..) 3. the speed of noncritical part oftheir Programs. We should forget about 4. ‘small efficiencies, say about 97% of 5. the time: "=Donald Knuth 6, Performance Tuning 101 Runtime Complextiy Formulate hypothesis ‘Omit needless features Splittest to validate ‘each new feature Focus on product- market fit Seek high-value and low-cost features ‘Measure, then improve Focus on the slow 20% Algorithmic optimization All hall tothe cache Solve an easier problem version Know when to stop “ro the source code of ultimate human performance” — Kotler Flow Tips for Coders * 1. Always work on an explicit rm @ © © practal cade proiect, Work on fun projects that fulfil your purpose Perform fram your strengths Big chunks of caging time Reduce eistractions: [you can take raw resources and move them from a state of high entropy into a state of low entropy— using focused effort towards the loteainment ofa greater pion. “~~ 3-Step Approach of i Kameadetmsimanis || = peupbomasad 3. Remove features Howto Achieve Flow? JS «6. Sleep alot, eat healthily, A aston een srt Sua teed quay boos and font ype, color als a)nmediteeaback an) SPE UY ona = S__ 8 _ecomistentacossuls | (yGReESRRSRORTTER portage ut ne : eg Str * © Su 2. Apply focused effort ~ EEE tomakert real Seek feedback