Course code: LG-4
  • Years with company: 7
  • Years programming: 20
  • Primary programming language: C/C++
  • Other programming languages: Python
  • Unit test harnesses: None
  • Something else: I'm leader of small part developing interface of media functionality of webOS. I haven't written any code for about 5 years, but scored on code review of my part members. Currently my major role is defining requirements, breaking them to proper size, and defining interfaces between SW components.
  • Test practice now: Although I don't write test code directly, I guide our part member to set-up test plan for each requirements before developing them. And I review test plan is enough to meet requirement and check any regression.
  • Target system: Arm-based SoC Linux environment
  • Dev tools: Gcc Cmake
  • Build time: 1 day or more
  • Coding standard: General C++ Standard Sometimes I refer google's one
  • Function too long: When use page up or page down to native code within one function
  • Code reviews: I don't understand this question
  • Code time: 0
  • Test time: 0
  • Debug time: 0
  • Favorite thing about dev: Well-defined components No-redundant code Separated code between abstract and concrete Readability
  • Least favorite thing about dev: Complicated Components Redundant code Mixed code between abstract and concrete Hard to read
  • Tdd knowledge: I think TDD is nice way to develop good quality code, but it's cost is too high and I sometimes hesitate applying it to my project.
  • Why are you attending: to know how to introduce TDD in real field case (not academic case)
  • Back