About Programmer

10 Things about good and not good programmers

Good Developer
1. In-depth Understanding of programming language 
2. Think in code / programming / logical way
3. Write simple code that other programmers can understand 
4. Don't hesitate to delete the code
5. Experiment new tools and techniques
6. Always have side project for trials
7. Pursuit for perfect code
8. Think about flexibility 
9. Develop own tools 
10. Write Blog about their work

Not good Developer
1. Poor understanding of programming language 
2. Poor analytical and logical skills
3. Write unstructured, unorganised and ugly code
4. Never discuss about technical stuff with friends and colleague
5. Lack of self upgrade 
6. Unable to think about interlinked code (normally open more bugs when fix one )
7. Don't care about optimisation and memory management
8. Locked in stereo type of coding 
9. They complete Tasks only
10. They will wait until the 100% details are available.

Tips: Android design pattern

Design Pattern, a design pattern is a general reusable solution to a commonly occurring problem, In case of Android, I personally feel that existing design patterns like MVC, Abstract Factory,Singleton,etc. are not fit with the Android. Most of design patterns was evolved before the era of Android/Mobile. I think that code should be simple and optimise, does not matter which design pattern you are using. 

In this article I am going to explain few rules/pattern which I am following in my projects.


1. Package Structure
         src 
             com.client.app                   - contain Application class only
             com.client.app.views           - contain all activities
             com.client.app.fragments    - contain all fragments
             com.client.app.webservice   - contain all web services
             com.client.app.adapters      - contain all adapters
             com.client.app.db              - contain all db related classes
             com.client.app.models        - contain all models
             com.client.app.utils            - contain utility/misc classes
             com.client.app.widgets        - contain extended/custom views
             com.client.app.services       - contain all services
             com.client.app.animation     - contain all animations

2. Naming convention for Xml files

• activity_<ACTIVITY NAME>.xml - for all activities
• dialog_<DIALOG NAME>.xml  - for all custom dialogs
• row_<LIST_NAME>.xml - for custom row for listview
• fragment_<FRAGMENT_NAME>.xml - for all fragments

3. Naming convention for component/widget in xml files.

• all component for x activity must be start with activity name
• all component should have prefix or short name like btn for button
• For example,name for login activity component should be like following.
• activity_login_btn_login
• activity_login_et_username
• activity_login_et_password
• Short name of major components
• Button - btn
• EditText - et
• TextView - tv
• Checkbox - chk
• RadioButton - rb
• ToggleButton - tb
• Spinner - spn 
• Menu - mnu
• ListView - lv
• GalleryView - gv
• LinearLayout -ll
• RelativeLayout - rl

4.  Reference links related to Android design pattern / architecture

• Which design patterns are used in Android 
• http://stackoverflow.com/questions/4916209/which-design-patterns-are-used-on-android/6770903#6770903
• Android MVC
• https://github.com/gvaish/Android-MVC
• Android MVP
• http://jamespeckham.com/Blog/10-11-21/MVP_on_Android.aspx
• Android architecture part 1
• http://www.therealjoshua.com/2011/11/android-architecture-part-1-intro/