Course code: PRAQ-1
  • Years with company: 3
  • Years programming: 8
  • Primary programming language: C and python
  • Other programming languages: Rust
  • Unit test harnesses: Cmock, cmocka
  • Something else: I play drums and guitar. Call me and we can jam! What about some good old CCR, or Hendrix?
  • Test practice now: I don't :(
  • Target system: Nrf52, a cortex m4 with a 2.4 ghz radio
  • Dev tools: Vim and git (youcompleteme for semantic auto completion in C)
  • Build time: 11-30 seconds
  • Coding standard: I disagree with it (don't we all?), but at least we got one, a comprehensive list with rationale for each point
  • Function too long: When I can't fit the function on one screen page
  • Code reviews: Through atlassian stash, not obligatory but recommended
  • Code time: 30
  • Test time: 0
  • Debug time: 70
  • Favorite thing about dev: I like design, and I think tdd brings some interesting mechanics into the api and structural design
  • Least favorite thing about dev: Others code ;) On a serious note, I hate trying to convince the managers or the group that code review and unit tests is time well spent.
  • Tdd knowledge: Not much. Bought your book but did not read it yet.
  • Why are you attending: I find it hard to actually implement Tdd in practice for embedded systems. Do you test static (private) functions, and if so how?), how do you test a hal? How do you test code in irqs? How do you test code that relies on hw timing?
  • Back