Course code: WEB-36
  • Years with company: 2
  • Years programming: 15
  • Primary programming language: C
  • Other programming languages: C++
  • Unit test harnesses: None
  • Something else: Taking a risk-based approach to developing device software reminds me of previous experience mountaineering. I also find that association amusing.
  • Test practice now: Our testing is done manually. Manually writing test cases for functions and modules.
  • Target system: Arm Cortex-M4, mainly STM32F4s
  • Dev tools: Keil uVision MDK, Parasoft C/C++ Test
  • Build time: 30-60 minutes
  • Coding standard: Currently undefined for the organization. Trying to st
  • Function too long: When I need to scroll up or down to find relevant portions of information within the function, it's cause for me to reconsider if anything done in the function is needs to be moved into its own function.
  • Code reviews: Reviews are done during pull requests of our git-based repository.
  • Code time: 30
  • Test time: 40
  • Debug time: 30
  • Favorite thing about dev: When approached properly, developing software can be intentional and deliberate to produce amazing things the world has never seen before.
  • Least favorite thing about dev: The misconception by other groups in multifunctional teams that developing software is quick and easy. It is quite easy to walk down the wrong path and write software quickly and haphazardly to produce code that functions for only "right now".
  • Tdd knowledge: I know that it relies to requirements as its pillars and testing against these requirements to consistently produce functional and purposeful code.
  • Why are you attending: In previous organizations I've worked, there wasn't a focus on testing. My co-worker shared 'Test-Driven Development for Embedded C' when he joined the org and I ended up purchasing a copy. After found this training while looking for more resources.
  • Back