Course code: WEB-33
  • Years with company: 23
  • Years programming: 23
  • Primary programming language: Java
  • Other programming languages: Javascript, Python,C++,C
  • Unit test harnesses: JUnit,Pytest,Jest
  • Something else: I have 7 kids, former musician. My aspiration is to get deeper into technical coaching.
  • Test practice now: I work mostly in mobs. Most of my coding in my current job is during katas. We use TDD with cyber-dojo. I would like to take TDD katas to the embedded world. The embedded developers in my area do MIL/SIL testing. There also are validation teams upstream who do a combination of manual and automated testing.
  • Target system: The area I work in develops Autosar based C code for embedded vehicle ECUs. 70% is model based, 30% is hand coded.
  • Dev tools: Matlab, Embedded Coder, Simulink,BTC Tester, Target Link
  • Build time: 1-2 hours
  • Coding standard: There are strict standards based on regulations. I know there are coding stds but I dont have the details.
  • Function too long: If its more than half a page.
  • Code reviews: Peer code reviews are a mandatory step for all code. They also review models and data dictionaries.
  • Code time: 50
  • Test time: 25
  • Debug time: 25
  • Favorite thing about dev: I like the feeing of accomplishment when something works.
  • Least favorite thing about dev: nothing
  • Tdd knowledge: Worked with it a lot in coding katas. Red green refactor cycle. It has a deep impact on the design of the system.
  • Why are you attending: Because I want to become a technical coach. My current job is in the embedded space and I would like to be able to help developers adopt TDD to improve the design, quality and fun in our systems.
  • Back