Course code: CARBON-2
  • Years with company: 0.5
  • Years programming: 35
  • Primary programming language: C/C++
  • Other programming languages: Python
  • Unit test harnesses: Google Test, Cpputest, Pytest
  • Something else: I am a cross-platform software engineer with a wide range of experience, but one who prefers writing code at the system level.
  • Test practice now: We're just now implementing unit testing. So, prior to that, it was write code, test the changes and debug any issues. We used unit tests in my last company, but the vast majority of the tests were written after the code was complete. However, there was still great benefit achieved as it greatly reduced the time needed for testing and debugging issues as that was resolved during the unit testing phase.
  • Target system: MacOS
  • Dev tools: Xcode, VI, LLDB
  • Build time: 1-5 minutes
  • Coding standard: There is no official coding standard that I am aware of for my team. I informally use portions of the coding standard from my last job.
  • Function too long: It is a matter of complexity for me. For example, the function is doing more than one specific task or the decisions made within the function require the examination of multiple variables.
  • Code reviews: Our code is reviewed via merge requests and informally requires at least 1 approval.
  • Code time: 40
  • Test time: 40
  • Debug time: 20
  • Favorite thing about dev: The challenge of solving complex problems.
  • Least favorite thing about dev: Nothing comes to mind.
  • Tdd knowledge: TDD is a way of documenting the requirements and expected behavior of an application, feature or object in unit tests before code is written. The code, once written, must pass those tests ensuring the requirements and expected behavior are achieved.
  • Why are you attending: I was asked if I was interested by my company and I said yes. We are just introducing TDD into my team and I want to make sure we're all on the same page.
  • Back