Course code: WEB-1
  • Years with company: less than 1
  • Years programming: 4
  • Primary programming language: C
  • Other programming languages: a little C++
  • Unit test harnesses: we usually use inhouse scripts and ISV's to verify our code functionality
  • Something else: I'm an engineering graduate, been working as a firmware(security module) engineer for SATA SSD's for more than 4 years.
  • Test practice now: We usually test our code with inhouse scripts and 3rd party scripts and tools.
  • Target system: SATA SSD, ASIC based on ARM
  • Dev tools: source insight editor, realview compiler and debugger, Lecroty SATA analyser, MS Visual studio, etc.
  • Build time: 1-5 minutes
  • Coding standard: Each product group defines their own coding standards, so it depends on the product.
  • Function too long: if hte functionis more than 25 or 35 lines, then i feel it is a very big function
  • Code reviews: reviews include self review, peer review, and walk through.
  • Code time: 50
  • Test time: 25
  • Debug time: 25
  • Favorite thing about dev: Enabling a device or an app to do its intended function with my code makes me feel good. And the constant challenges and learning makes me go for it.
  • Least favorite thing about dev: almost nothing
  • Tdd knowledge: I heard about this acronym "TDD" very recently.
  • Why are you attending: I'm expecting that this session would be of some help in developing a robust code with minimum defects and offer me some guidance in keeping my code modularized so that the code can be re-used on future hardware platforms too.
  • Back