Course code: WEB-23
  • Years with company: 0.5
  • Years programming: 6
  • Primary programming language: C
  • Other programming languages: C++, Python
  • Unit test harnesses: CppUTest
  • Something else: I did the layout/assembly/programming of an alarm clock for a class project that I'm a little too proud of (and I never implemented the actual alarm feature).
  • Test practice now: I'm just starting to use CppUTest and TDD, moving away from the 'Debug later' approach.
  • Target system: It has a wide range of peripherals: an LCD, Ethernet, SD card, etc.
  • Dev tools: GCC, GDB, VIM, MPLAB X, Eclipse
  • Build time: Under 10 seconds
  • Coding standard: I don't have a specific coding standard.
  • Function too long: When I get confused by looking at it.
  • Code reviews: I haven't had much experience with code reviews, I've primarily been a solo developer.
  • Code time: 40
  • Test time: 5
  • Debug time: 55
  • Favorite thing about dev: Organizing ideas, automation, making something happen on hardware
  • Least favorite thing about dev: Organizing project files, compiler/linker include management, breaking changes
  • Tdd knowledge: It's based on unit testing, where each function/feature has one or more tests that are run on each build cycle. Focus is placed on writing tests first, then writing only enough production code to make tests pass.
  • Why are you attending: I felt that I need to have hardware mocking explained to me, reading the TDD book exposed me to a lot of ideas at once and I need help focusing on what's important.
  • Back