Code standards, style, version control, code review, build system, task and bug tracking, debugging

A small presentation with few words about common things for young developers

Transcript

1. Code standards, style, version control, code review, build system, task and bug tracking, debugging by Yuriy Berdnikov
2. Agenda • Code standards and style • Version control • Code review • Build system • Task and bug tracking • Debugging
3. Code standards and style
4. Code standards • Set of guidelines • Usually cover file organization, indentation, comments, declarations, statements, white space, naming conventions etc. • Improve the readability of source code • Make software maintenance easier
5. Readable Code a = b * c; weekly_pay = hours_worked * pay_rate; vs
6. Indentation or but not
7. Vertical alignment or but not
8. Spaces or rarely
9. Hungarian notation ! • Name of a variable or function indicates its type or intended • extended in C++ to include the scope of a variable, separated by an underscore
10. Version control
11. • What Is Version Control? • Version Tracking • Coordinating Teams
12. Structure
13. Diff between revisions
14. Version control systems • CVS • SVN • Git • and more ..
15. Code review
16. Introduction • Remove common errors, race conditions, memory leaks and buffer overflows • Enforce the Coding Standard • Ensure correctness of code • Typical code review rates are about 150 lines of code per hour
17. Types • Pair programming • Formal code review • Lightweight code review
18. Build system
19. Build automation • Compiling computer source code into binary code • Packaging binary code • Running tests
20. Advantages • Accelerate the compile and link processing • Eliminate redundant tasks • Improve product quality
21. Build automation software • Make - a classic Unix build tool • Apache Ant - popular for Java platform development and uses an XML file format • Rake - a Ruby-based build tool
22. Task and bug tracking
23. Tasks tracking • Managing tasks through its life cycle • It involves planning, testing, tracking and reporting • Help achieve goals
24. Task life cycle • Ready • Assigned • Terminated • Expired • Forwarded • Finished • Failed
25. Tasks board
26. Bug tracking system • Provide a clear centralized overview of development requests • Prioritized list of pending items (backlog) • Bugs and issues tracking
27. Bug life cycle
28. Debugging
29. Introduction • Process of locating and fixing bugs • Necessary process in almost any new software or hardware development process • Debugging tools (called debuggers) help identify coding errors at various development stages.
30. Debugging • Recognize that a bug exists • Isolate the source of the bug • Identify the cause of the bug • Determine a fix for the bug • Apply the fix and test it
31. Debuggers • GNU Debugger (GDB) • Microsoft Visual Studio Debugger • Eclipse debugger API
32. Debuggers features • Running a program step by step • Stopping at Breakpoints • Tracking the values of variables • Modify program state while it is running
33. Q&A
34. Thank you