“Experience is just a number”, in fact there is nothing difference between a Fresher and Experience. Every experience person also feels the same. When you are Fresher it doesn’t mean that you are less Intelligent / Skilled than Experience, you just need some time to stabilize your skills, intelligence, logical thinking and patience. Time will teach you everything. Most important difference is “Patience”, experience people will always show patience in any work. If you are a Fresher just keep some key points into your mind while coding, “That’s it”. Those key points will make you very closer to an Experience programmer/developer.
Key points to change you to an Experience programmer/developer:
- Learn how to Google
- Grip on OOPS
- Code Reuse
- Code comments
- Follow Standards
Learn how to Google:
- Most of the Experience developers in IT sector are surviving because of If you know how to Google for a solution no doubt you can survive anywhere in IT sector. But need to remember is “Compromise nowhere until find the solution”.
- Experience Developer:
- Analyze the problem first
- Google with the exact keywords
- Picks up the popular forum sites like (stack overflow, Code project, Code Guru etc…)
- start applying the up voted answers first
- If not working, go for the all the other solutions and keep trying
- if not working till, now he/she will start learning that new concept from technical content sites.
Note: As you have seen from the above process, “No where the person give up“. Just keep on trying till you find the solution, if not take your colleagues help.
Google API’s working formula
Minimum and simple words Maximum results
- Who is the author of C (many words) gives few results
- Author of C (few words) good results
- Prefer stack overflow first (Note: if it’s a known concept for you)
- Some of the popular discussion forum sites (stack overflow, Code project, Code Guru etc…)
- In the stack overflow the very first step search for the “Most up voted answer”.
- “Read all the solutions”. Many solutions will work even if it’s not an up voted and vice versa.
- Prefer site which has easy slang according to your terminology. If you pick the toughest slang of technical terminology you will never understand that topic in depth.
Grip on OOPS:
Strong in OOPS you will argue with someone
Weak in OOPS you will listen to someone
Yes when you are strong at something (For example: You know very well HTML). If your colleague doesn’t follow standards then what will be your reaction, sure you will argue with him and teach him the right way.
- Concentrate more and more on Loops (for, while, do while).
- If you are not confident on loops write every iteration on paper for some days.
- Iterate loops in your mind once you are confident.
- Use all oops concepts in every module if it’s not even required. So that you will not forget it.
- Teach someone who doesn’t know OOPS, teaching is the best-way to remember the basics all the time.
- Concentrate on unknown topics and learn at least one topic a day.
Most of the Experience Developers follow Code Reusing techniques all the time. Few techniques are using
- Libraries (DLL’s)
- Web Services & Web API’s
- Don’t ever write every piece of code in the same file
- Create libraries (or) Packages and Reuse them for Business Logics.
- Always prefer multi-layered architecture in all the Tiers of project. So that presentation of your code will be very clean.
- Create API’s for the Repositories (Repositories are noting but your Data Access Layer).
- Always try to maintain Loose coupling e., use Dependency Injection. This will be very helpful to test the application.
- Use Inheritance as much as you can.
Few places where you should write comments:
- File level / Class level comments
- Method level comments
- Code level comments
- Write a brief description on the top about complete file (Class file / script file) with Block Comment.
- Write XML comments on every method about the inputs, output, exception handling, date modified, and modified by.
- Write comments for every two or three lines, and for every code block in a function/ method.
Follow Code Standards:
- Always use Pascal case (or) Camel case
- Don’t use names begin with numeric characters.
- Do not use Hungarian Notation!
Example: strName or nCount
- Don’t include the parent class name within a property name.
Example: Use Employee.Name NOT Employee.EmployeeName
- Give prefixes to Boolean variables using “IS”, “Has”, “Can”.
- Every developer has their own coding style.
- Don’t give more than one empty line in any piece of code
- Don’t write multiple classes in same file.