Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Effective Programming in Development Process

Effective Programming in Development Process

Aditya P. S.

March 25, 2015
Tweet

More Decks by Aditya P. S.

Other Decks in Programming

Transcript

  1. Efficient Programming in Development Process Presented by Aditya Pradana at

    Engineering Brownbag Session in Oneb1t on Wednesday, March 25th 2015
  2. Why? • Code is read much more often than it

    is written • We need to deliver the product quickly • Avoid too much bugs
  3. Write Human-Friendly Code • Follow consistent naming conventions • Discuss

    naming conventions before anyone touches the code • Descriptive variable / method name • Indentation And Line Breaks
  4. Think Organization • If you need to scroll up and

    down multiple times to find your affected section, you need to work on the structure • Don’t throw all the code into a single script • Try to separate code into different files
  5. Planning Before Coding • Know exactly what to do •

    Figure out the procedure first, then write a solution • Really good programmers spend a lot of time THINKING. Not madly typing in code. Typing should be the last act, not the first. • Use only tools, plugins, components, libraries, whatever that are necessary for your project
  6. Write Manageable Code • Write code that requires as few

    manual changes as possible • Avoid tight coupling
  7. Learn To Debug Smarter • Breakpoint setting • Put the

    log function into the code • etc.
  8. No Extra Prototypes • Prototyping is a beneficial behavior in

    the long run • It doesn’t help when you do it to escape from work
  9. Always Learn Something New • Most people are not driven

    to become good at anything. They reach a point that is comfortable for them and stop improving • Do read and write • Challenge ourself with practical projects that require higher scalability
  10. –Someone who cares about code and design “Great programming requires

    not only intelligence but also creativity. The best programmers I know are artists not engineers!”