Course code: WEB-34
  • Years with company: 1.5
  • Years programming: 20
  • Primary programming language: C/C++
  • Other programming languages: Minimal shell scripting.
  • Unit test harnesses: None
  • Something else: My development background is mostly in telecom field (cable boxes).
  • Test practice now: Run on simulator to check basic functionality since it's easier to control the environment. Then load and test on hardware to exercise the code.
  • Target system: Embedded Linux on Xilinx Zynq, running on small air vehicle.
  • Dev tools: Visual Studio, Keil IDEs. Git/Gitlab for source control and code reviews.
  • Build time: 1-5 minutes
  • Coding standard: Basic guidelines created by the larger development group. Focused on readability and general best practices (no hard coding, single return per routine, clear comments, etc.)
  • Function too long: Generally, I look at what it does rather then physical length. If it's going multiple different things, it's too long and could be broken up for reuse and clarity.
  • Code reviews: Performed in gitlab by peers of varying experience levels.
  • Code time: 50
  • Test time: 30
  • Debug time: 20
  • Favorite thing about dev: Seeing the end result of code in action running the system.
  • Least favorite thing about dev: Spending lots of time trying to reproduce corner case issues.
  • Tdd knowledge: Very little in practice... As part of the Agile process, I think it's meant to improve quality with a marginal increase in coding time.
  • Why are you attending: Part of a relatively new development group trying to implement best practices and adopt some Agile methods and ideas. Currently no TDD, but as the group matures, we would like to start...
  • Back