Course code: WEB-30
  • Years with company: 10+
  • Years programming: 10+
  • Primary programming language: C/C++
  • Other programming languages: Java Script
  • Unit test harnesses: None
  • Something else: I Have more than 15 years of programming experience but I use the traditional method of debugging.
  • Test practice now: Its mainly functional testing by putting the executable directly in the target board and use printf statements for debugging.
  • Target system: Its X86 board with stripped version of Linux ( Ubuntu 10.04). The Kernel is 2.29.6. It has the peripherals ( IOs), LAN Port, Zigbee port
  • Dev tools: Ubuntu 10.04 Eclipse (LUNA) for development For Microcontroller Keil5 and for ARM IAR
  • Build time: 1-5 minutes
  • Coding standard: Basic Coding standard
  • Function too long: 1. When you have to scroll the page 2. More than 100 lines
  • Code reviews: Peer to peer code review is done. Another developer does the code review and put comments in an excel sheet. Modification is done based on that and proper comments are placed in the same excel sheet.
  • Code time: 40
  • Test time: 30
  • Debug time: 30
  • Favorite thing about dev: 1. Seeing the transformation of idea/requirement to a real life solution 2. My idea controlling something real 3. Taking inputs from real world and giving some out put
  • Least favorite thing about dev: 1. Hectic schedule/Long hours of work 2. Unrealistic requirement 3. Stress
  • Tdd knowledge: Nothing. It is complete new to me. As I said I follow traditional method of debugging.
  • Why are you attending: With the older approach, some scenarios are left undetected in lab testing but appear in field scenario. Want to minimize that so that such situation can be avoided. Reproducing/debugging an issue reported from field is quite difficult.
  • Back