(Core Agile) Software Development Best Practices

1. Quality Culture

2. Mayank Patel
Application Architect - Oildex, a service of Transzap
/Linkedin @maxy_ermayank

3. (Core Agile) Software Development Best
Practices

4. Developer Looking For Docs In Legacy

5. Resolving Technical Debt

6. Developer looking at Production Logs

7. 6 Stages of Debugging

8. Sudo rm -rf /

9. Commenting (Avoid Obvious Comments) &
Documentation

12. Consistent Formatting

14. Code Grouping (Avoid empty lines after
every line)

15. Consistent Naming Scheme
File Naming convention
Function & Module Naming convention
Variable Naming convention
Database Naming
Server Naming
URL Naming
...

16. com.oildex

17. DRY Principle (Don't Repeat Yourself)

18. Avoid Deep Nesting

20. Limit Line Length
80 - 120 characters is good number to start wrapping

21. File and Folder Organization

22. Separation of Code and Data

23. Read Open Source Code

24. Rigorous, regular refactoring

25. Continuous integration

26. Simple design

27. Pair programming

28. Sharing the codebase between all or most
programmers

29. A single to which all
programmers adhere
coding standard

30. A common “war-room” style work area.

31. Memory management

32. Error Handling

33. Log management

34. Avoid hard coding

35. Modularity

36. Code Review & PR Guidelines

38. PR should have at-least Two reviewer
Pull request template should be used all the time

39. Handy Tools and Techniques
Debugger
Memory Detector / Pro ler
Putty / Terminal
WinSCP, FileZilla
Always keep adding new tools & techniques in your box.....

40. Leave the ego behind, Be eager to learn
Technical Forums over the internet
Technical magazines on various IT subjects
Technical Bulletin Boards
Conferences, Trainings and workshops
Latest versions of old tools and packages, languages etc.

41. Test-first programming (or perhaps Test-
Driven Development)
Testing is the Religion

42. Common Cases
Tight schedule, no compromise
Changed just a comment, still you have to test it
Changed just a variable name, testing has to be done
If you feel lazy...it's too dangerous
Validates your design
Rapid feedback
Requires more discipline

43. Celebrate every bug you find
Bugs are your enemies, so you have killed one.
Now your software is having one bug less.
Mistakes are good as long as they are not repeating.
What you learn today prepares you for tomorrow.

44. Results
Higher Quality
Flexibility
Readability
Maintainability
Predictability
Simplicity
Internal and External Quality are maintained
Well designed application

45. Testing Levels

46. Static Code Coverage
CPD: Class design problems, method design problems
CPD: Check code layout and formatting issues
PMD: Unused variables, empty catch blocks, unnecessary object
creation, and so forth
PMD: Finds duplicated code
Cobertura: Calculates the percentage of code accessed by tests

47. Unit Testing
Each module Individually
testing for business logic
Owner: Developers
Guidelines

48. Integration Testing
Top Down Integration
Bottom Up Integration
Create, Read, Update, Delete and destroy data

49. System Testing
Alpha/Beta Testing (Test team and Beta customers)
Acceptance Testing (Performed by customer - Product owners can
as perform well)
Performance Testing (Check to verify architectural criteria meets)

50. Tools
Unit Test Frameworks: JUnit, ScalaTest, specs2, Scalacheck
Mocking Framework: Mockito, EasyMock
Integration Test Tool: JMeter, Cucumber, Selenium, RestAssured
Automated Build Tool: Maven, Gradle, Sbt, etc.
Static Code Coverage Tools: Cobertura, Checkstyle, PMD,
FindBugs, etc.
Continuous Integration Tool: Jenkins
Data Builders
Security Testing Tools
Reporting

51. Java Tools

53. Full Build and Initial testing of feature prior
to pushing any commits

54. Thank You!