Professional Developer Qualities

775 views

Published on

Professional Developer Qualities

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
775
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
8
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Professional Developer Qualities

  1. 1. Professional Developer Qualities http://www.fideltech.com Bhavin Patel [email_address]
  2. 2. Thinking problem <ul><li>Think professionally </li></ul><ul><ul><li>Think about complete deliveries. </li></ul></ul><ul><ul><ul><li>What it should include? </li></ul></ul></ul><ul><ul><li>Think about end user, </li></ul></ul><ul><ul><ul><li>How delivery will be presented to end user? </li></ul></ul></ul><ul><ul><li>Think about next developer or code maintainer </li></ul></ul><ul><ul><ul><li>How code maintainer will maintain it? </li></ul></ul></ul><ul><ul><ul><li>How next developer will use or read it? </li></ul></ul></ul>
  3. 3. Minimum Quality Standard <ul><li>Code Indentation  </li></ul><ul><li>Brace Style  </li></ul><ul><li>Casing standards </li></ul><ul><li>Naming standard </li></ul><ul><li>Minimum comment </li></ul><ul><li>Write code that can easily understood or output of code can be easily predicted. </li></ul>
  4. 4. Code Indentation <ul><li>Do not type space for alignment </li></ul><ul><li>Always use tab from first line </li></ul><ul><li>Do no realign after testing code, Do it before testing code. </li></ul><ul><li>Do not write long lines </li></ul>
  5. 5. Brace Style <ul><li>Show consistency in brace style </li></ul>
  6. 6. Casing standards <ul><li>Pascal casing—The first character is upper case, and the first letter of each word in the object is also upper case, e.g. InvoiceNumber or PrintInvoice. All other characters are lower case. </li></ul><ul><li>Camel casing—The first character is not upper case, but the first letter of each word in the object is upper case, e.g. invoiceNumber. All other characters are lower case. </li></ul><ul><li>All word in lower case & word are seperated by underscore. </li></ul><ul><li>Do not mix any of this in at one place. </li></ul><ul><li>Can use different standard for HTML, XML, JavaScript, PHP, SQL etc… </li></ul>
  7. 7. Minimum Comment <ul><li>Comment will always help to next developer. </li></ul><ul><li>Write description for code block </li></ul><ul><ul><li>specially write description about input & output. </li></ul></ul><ul><ul><li>Not much require about process. But next developer should be able to predict the output based on input. </li></ul></ul><ul><li>Comment will help to identify </li></ul><ul><ul><li>What block of code is for what. </li></ul></ul><ul><ul><li>Why added? </li></ul></ul><ul><ul><li>Who added? </li></ul></ul><ul><ul><li>When added? </li></ul></ul>
  8. 8. SQL code formatting <ul><li>Use upper case for SQL keyword. </li></ul><ul><li>Break line for each clause like SELECT, FROM, WHERE, LEFT/RIGHT JOIN, ORDER BY, GROUP BY etc… </li></ul><ul><li>Write each condition on separate lines </li></ul>
  9. 9. How should be written? <ul><li>Check code for existing implementation </li></ul><ul><li>Use same mechanism, control structure, naming convention etc… as used in existing code. </li></ul><ul><li>Selection of suitable control structure for the problem </li></ul><ul><li>Modularize the code using classes & functions </li></ul>
  10. 10. Root cause analysis (RCA) <ul><li>RCA is predicated on the belief that problems are best solved by attempting to correct or eliminate root causes, as opposed to merely addressing the immediately obvious symptoms. </li></ul><ul><li>By directing corrective measures at root causes, it is hoped that the likelihood of problem recurrence will be minimized. </li></ul>
  11. 11. How should be designed? <ul><li>Use proper OOAD techniques </li></ul><ul><li>Use proven design pattern </li></ul><ul><li>Use existing implemented technique </li></ul>
  12. 12. Thinking Difference <ul><li>There is big difference between thinking of mechanic & engineer. </li></ul><ul><li>Try to understand the problem. </li></ul><ul><li>Use engineering approach to solve. </li></ul><ul><li>Make your self software engineer not software mechanic . </li></ul>
  13. 13. Thanks

×