Course code: WEB-17
  • Years with company: 3
  • Years programming: 6
  • Primary programming language: C
  • Other programming languages: C++, Python, Java
  • Unit test harnesses: Ceedling (Unity, Cmock), cpputest, Google Test/Mock
  • Something else: I have a background in electronics and computer science. During my career I've done a bit of everything: designing PCB, developing apps and in the last 3 years I've specialized in programming embedded systems.
  • Test practice now: I use unit tests in some parts of the code, however I have difficulties to make the rest of the team use it. If I'm the only one using it, even if it helps during development, it becomes pointless for maintainability. The rest of the code is manually tested. This is something I would also like to understand, where shall I draw the line between unit and integration tests?
  • Target system: Currently working on an ESP32 project
  • Dev tools: make, cmake, Visual Studio Code, Sublime Text, terminal, git
  • Build time: 11-30 seconds
  • Coding standard: No specific standard, it evolves
  • Function too long: When I have to read line by line to understand what's going on.
  • Code reviews: I tend to focus on trying to find bugs instead of asking myself why is this done this or this other way
  • Code time: 50
  • Test time: 30
  • Debug time: 20
  • Favorite thing about dev: Software is like a brain teaser. Everyday there's a new challenge and everything has to play along.
  • Least favorite thing about dev: There are too many tools available and not much good information. Good non-beginners content is hard to find.
  • Tdd knowledge: I know it can speed up the development, specially when bugs happen. I also know unit testing is not the same as integration tests.
  • Why are you attending: I want to create good code because chances are it will result into good products. I also think it's a key tool for teamwork, but if I'm not confident using it, it's harder to encourage the rest of the team to do it.
  • Back