Course code: JHAP-1
  • Years with company: 1.5
  • Years programming: 6.5
  • Primary programming language: C/C++
  • Other programming languages: Python, Java
  • Unit test harnesses: TDD
  • Something else: I am an early career embedded software engineer who is motivated to learn more and become more effective in my role.
  • Test practice now: Depending on the project we employ TDD or just test different areas of code via CLI commands and debug from there.
  • Target system: ARM microcontrollers for the most part.
  • Dev tools: IAR Embedded Workbench, Eclipse, Simplicity Studio, git, Jira, gitlab
  • Build time: 31-60 seconds
  • Coding standard: We have a document for our group on various aspects of our coding standard detailing naming conventions for variables, comments formats, the version of C we try to use, etc.
  • Function too long: If it exceeds 50-100 lines or if it tries to accomplish too much and can be broken down into smaller sub-functions to make it more readable.
  • Code reviews: We have coding reviews typically. They vary from project to project, some are very detailed and the whole team reviews added features, others only require very little review.
  • Code time: 30
  • Test time: 40
  • Debug time: 30
  • Favorite thing about dev: I like the challenge of figuring out novel ways to accomplish problems or learning a new way to do something I previously new.
  • Least favorite thing about dev: Debugging issues sometimes, merging code with other areas of code, version mismatch issues.
  • Tdd knowledge: I know that it involves developing test cases for your code to pass and to then write code that satisfies those test conditions.
  • Why are you attending: I want to learn more about this so that on future and current projects I can employ it and have it benefit myself and my team during our development process.
  • Back