Course code: BARR-9
  • Years with company: 0.5
  • Years programming: 3 years sort of. Actively been coding for 2 years
  • Primary programming language: C
  • Other programming languages: python for scripting, reading C++
  • Unit test harnesses: none
  • Something else: I started working as a firmware engineer 2 years ago and have learned most of what I know through work. I do have an MS in Computer Engineer but I feel I learn the most through actually doing.I've been the first firmware engineer at both the companies that I've worked for and have been responsible for setting up the infrastructure for firmware development
  • Test practice now: Manually. I run long tests and debug myself.
  • Target system: I'm using a nordic chip with m4 arm processor. I use IAR to build and flash the code.
  • Dev tools: IAR, sublime text editor
  • Build time: 11-30 seconds
  • Coding standard: I've been using Barr groups coding standard book
  • Function too long: If it's not readable anymore. I generally try to do one simple thing in a function, if it gets too complicated, i try to split into several functions.
  • Code reviews: We use github and create PRs where I generally tag other software engineers. We go through the code thoroughly for good practices, algorithmic correctness and general coding etiquette.
  • Code time: 50
  • Test time: 20
  • Debug time: 30
  • Favorite thing about dev: I like being able to solve problems and create logics. I like to look at an issue and think of how I can solve it in the best possible way.
  • Least favorite thing about dev: I don't like when I get stuck with debugging or fixing bugs, especially intermittent bugs!
  • Tdd knowledge: not much. I did buy your book some time back but I haven't been able to read it past the intro. Hence, this course :)
  • Why are you attending: I like writing code and take a weird pride in writing the best possible and most efficient code. I also hate debugging. I feel being able to write unit tests will help me with these things.
  • Back