Course code: ELSTER-1
  • Years with company: 3.5
  • Years programming: 10
  • Primary programming language: C
  • Other programming languages: Python, PHP, Javascript, C++, C#, Java
  • Unit test harnesses: cunit
  • Something else: I like long walks on short piers
  • Test practice now: a small amount of unittesting (when applicable), alot of python tests acting on the DUT.
  • Target system: ARM Cortex M4
  • Dev tools: IAR, Visual Studio, Eclipse
  • Build time: 11-30 seconds
  • Coding standard: kind of a half way attempt at hungarian notation. Elster has a doc on this.
  • Function too long: no written rule. Try to break things out when it makes sense. I usually don't like scrolling on them, unless it's a long switch statement for a string parser or something like that...
  • Code reviews: we use review board. I find that most code reviews are more a factor of who attends them, than the amount of them. Having the right people in the room allows for better reviews.
  • Code time: 50
  • Test time: 25
  • Debug time: 25
  • Favorite thing about dev: I enjoy developing something that doesn't exist
  • Least favorite thing about dev: Nothing really. It usually the politics of code changes near a release that make I don't like.
  • Tdd knowledge: glanced at your book, learned about it some in college.
  • Why are you attending: required by management.
  • Back