Course code: WEB-21
  • Years with company: 3
  • Years programming: 15
  • Primary programming language: Swift
  • Other programming languages: Ruby C++ Java
  • Unit test harnesses: JUnit GTest RSpec
  • Something else: I lead a team that is responsible for teaching new hires TDD. Our division is making a shift to embedded development and we are considering how to retool the development teams.
  • Test practice now: TDD, ATDD.
  • Target system: Unknown at this time. Will depend on the client.
  • Dev tools: Depends on the language. Generally an IDE from Jetbrains and whatever build/dependency management tools are part of that language ecosystem. I.e. Bundler for Ruby, Gradle for Java. CMake for C++.
  • Build time: Under 10 seconds
  • Coding standard: Clean code. Formatting based on what is idiomatic for that language.
  • Function too long: If it's over 10 lines.
  • Code reviews: Pair programming.
  • Code time: 60
  • Test time: 40
  • Debug time: 0
  • Favorite thing about dev: Creating something people find useful/valuable.
  • Least favorite thing about dev: New shiny languages/frameworks.
  • Tdd knowledge: Quite a bit. Been doing it for a long time and have studied it in depth (books, experiments, etc).
  • Why are you attending: To learn how you teach TDD in an embedded context. What constraints are there? What are the pitfalls? What do you need to do differently from test driving a web or mobile app?
  • Back