SCALING YOURSELF BY WRITING GOOD CODE

Transcript

1. SCALING YOURSELF BY WRITING GOOD CODE REMY MUHIRE | forLoopZambia
2. About @kenessajr?
3. CTO at Exuus Lives in the country of a thousand hills, Rwanda
4. Open Sourcer at Pindo SMS Services for Humans primarily written in Python
5. Community Builder forLoop
6. KIGALI FIFA 18 CHAMPIONSHIP ORGANIZER
7. ADVOCACY FOR
8. Here we go ……...
9. Why are people reluctant to try something new? ➔ New things can pose danger ➔ They can create an Uncertainty
10. “Don't fear failure so much that you refuse to try new things. The saddest summary of a life contains three descriptions: could have, might have, and should have. “ - Louis E. Boone
11. Start by writing clean code ➔ Clean code is code that is easy to understand and easy to change. ➔ A clean code should be as efficient, readable, and maintainable as possible, and instead of only solving the problem.
12. Bad code vs Clean code
13. Rules for Good Coding
14. Optimization VS Readability Always write code that simple to read and which will be understandable for developers. Because time and resources that will be spent on hard readable code will be much higher than what you get from optimization.
15. Architecture first. Writing code without thinking of its architecture is useless in the same way as dreaming about your desires without a plan of achieving them.
16. Test coverage. Why test coverage are so important. ➔ It’s just save you time.
17. Always keep it simple Don’t write complex code. More it simpler than less bugs it may have and less time needed to debug them.
18. Comments. Comments shows bad code. Good code should be understandable without a line of comment
19. Mono vs Micro Always try to use microservice architecture. Monolithic software can run faster than micro-service software, but only in the context of one server. Microservices give you possibility to distribute your soft efficiently not only on many servers but sometimes even on one machine(i mean process distribution).
20. Don’t write code when you are tired or in a bad mood. When developers are tired they are making 2 to 5 times more bugs and mistakes then when they are full of energy. So working more is very bad practice. That’s why more and more countries thinking about 6 hours work day.
21. Go out, get hobbies. Work differentiation increases mental abilities and gives new fresh ideas. So make pauses and go out on fresh air, talk with friends, play FIFA, etc.
22. Learn new things as you get free time When people stop learning they start to degrade.
23. Thank you forLoop Zambia Any question? You can find me at @kenessajr | Twitter & Github