Tools Engineer: Core Software Development - Software Engineering, Writing Code/Unit Testing/Refactoring

Knowledge

Writing Code

• good function/variable names
• maintainability/readability vs performance
• commenting code, comment rot
• code smell
• exit codes vs exceptions
• cyclomatic complexity
• code review
  • what to look for
  • what to automate

Unit Testing

• the “unit”
• other types of testing
• why write test
• mock, stub, spy
• what to test / what not to test
• code coverage
• maintenance vs provided value

Refactoring

• what does it mean to refactor
• techniques
• when it is time to refactor
• estimating the effort
• when not to refactor or when to stop
• testing

Misc

• RegExp
• Development Tools
  • Visual Studio Code
  • Visual Studio

Resources

Book Links

• Code Complete: A Practical Handbook of Software Construction
• Clean Code: A Handbook of Agile Software Craftsmanship
• The Pragmatic Programmer
• Modern C++ Programming with Test-Driven Development
• The Art of Unit Testing
• Working Effectively with Legacy Code
• Refactoring: Improving the Design of Existing Code

Web Links

• Write unit tests for C/C++ in Visual Studio
• A quick introduction to the Google C++ Testing Framework
• Googletest Primer
• Walkthrough: Create and run unit tests for managed code (C#)
• IT Hare: My Personal Take on Testing
• Is TDD Dead?
• Learn Regular Expressions with simple, interactive exercises
• Regular Expressions editor (regexr)
• How to choose good names in your code
• Putting comments in code: the good, the bad, and the ugly.

Video links

• CppCon 2014: Matt Hargett “Pragmatic Unit Testing in C++”
• CppCon 2015: Matt Hargett “Advanced Unit Testing in C & C++”
• CppCon 2015: T. Winters & H. Wright “All Your Tests are Terrible…”
• Unit Testing Best Practices with Roy Osherove