Becoming an unusual developer

Peter Ekene presents key points and tips on how to stand out as an unusual developer instead of trying to fit in and be like everyone else.

Transcript

1. Becoming an unusual developer Don’t Fit In, Stand Out
2. Profile • Peter Ekene • Author : Scotch, Practical Dev, AndroidPub etc. • Android Nigeria @kenny_io
3. 19/02/2018 … Who is a usual developer ?? A NORMAL developer who does everything like every one else
4. 19/02/2018 ..Who is an unusual developer ?? Just another developer who does everything a bit differently in a very good way
5. 19/02/2018 1. Understand the negligible details 2. Performance conscious development 3. Write 4. Diversity 5. Contribute to open source 6. Write maintainable code 7. Familiarize with your IDE 8. Others Key Points
6. Understand your code private String getRP(Uri uri) { Cursor cursor = null; try { String[] projection = { MediaStore.Images.Media.DATA }; cursor = getContentResolver().query(uri, projection, null, null, null); @SuppressWarnings("ConstantConditions") int column_index = cursor.getColumnIndexOrThrow(MediaStore.Images.Media.DATA); cursor.moveToFirst(); return cursor.getString(column_index); } finally { if (cursor != null) { cursor.close(); } } }
7. 19/02/2018 Write WHY ?? 1. Build Your Portfolio 2. Help Someone 3. Learn More 4. Get Paid 5. Get views, Feel good Time Expensive It gets daunting sometimes REF
8. 19/02/2018 Unusual developers befriends their IDE’s • Get to know the short keys • Install Plugins • Customize your pref keys • Apply themes and fonts REF
9. 19/02/2018 Performance Conscious Development Unusual developers build products with utmost performance in mind Users reactions and expressions
10. COOL… WELLDONE!!!! 1.
11. DUDE…. WTF 2.
12. Jeeeeezzz..! i can’t take this anymore 3.
13. You know what, don’t worry, i know what to do 4.
15. Write Maintainable Code 19/02/2018 Once upon a time memory was scarce and cycle times were slow. programmers were encouraged to write complex single lines of code that did many things. Today memory is plentiful and cycle times are fast. You should write 5 lines of code people can follow instead of one line they cannot understand ~~ StackOverFlow Every developer can write codes that the computer understands, UNUSUAL developers writes codes humans understands. The only viable means of assessing code quality is how many WTF’s i say per minute ~~ one dude like that
16. 19/02/2018 Maintain naming conventions o Keep comments short and helpful o Define specific methods to handle major tasks String person_name = “Eric”; int person_age = 20; String person_position = “Marketer”; o //…… short helpful comment o /** long and complicated comment **/ Private void uploadToCloud(){ //………… } String person_name = “Eric”; int personAge = 20; String position = “Marketer”;
17. Contribute to open source 19/02/2018 If you have developed a library, plugin, or other useful piece of code and you're using it in your own app, consider open-sourcing it. There's much to learn in the process of contributing to open- source projects or maintaining your own. If you don’t have anything to open-source, consider checking out other open-source projects that interest you, and fix some bugs, improve the documentation, or write a few tests there. Even the smallest bit of contribution (such as fixing some grammatical errors in the docs) will be helpful for the project maintainer to keep the project running. Tip: there’s an awesome guide for you to get started in open-source development attached.
18. Learn more 19/02/2018 Kotlin Xamarin React Native Ionic Javascript
19. 19/02/2018 Use Libraries only when necessary Be Diplomatic I don’t know is not a crime Complement Colleagues Others
20. Ref: 19/02/2018 2. Android Studio Keyboard Shortcuts for Mac and Windows https://developer.android.com/studio/intro/keyboard-shortcuts.html 3. Android Studio Plugins to enhance productivity https://medium.com/mindorks/how-to-become-more-productive-in-android-with-android-studio-plugins-3beb3861fa7 1. Learn How To Write https://medium.freecodecamp.org/developers-the-why-and-how-to-writing-technical-articles-54e824789ef6
21. THANK YOU