Course code: WEB-34
  • Years with company: 7
  • Years programming: 2
  • Primary programming language: C
  • Other programming languages: C Sharp, C++
  • Unit test harnesses: none.
  • Something else: I did a lot of testing, our group is going to do some automation test in the near future. I did some programming, but not a lot.
  • Test practice now: Most test are done by testing with hardware and hardness. Few tests are done by some software unit test.
  • Target system: it is a system, with a control software, a gateway and control boards. The cloud will be included in the near future.
  • Dev tools: MS Visual Studio, and Eclipse Editor.
  • Build time: 5-30 minutes
  • Coding standard: Code Format should be uniform, easy to read. All the comments to explain what the codes do is preferred. Codes can be broken down to modules, so that they can be called by other modules.
  • Function too long: When it is too hard to understand, and when there are too many parameters, and too many logics in there.
  • Code reviews: Sometimes I do, sometimes not. But I prefer to do it. To check the logic needs some more thoughts or not, and coding is efficient or not.
  • Code time: 1
  • Test time: 7
  • Debug time: 1
  • Favorite thing about dev: develop something, then test to see if the implementation is correct. To debug needs logic thinking which is fun, but sometimes it is frustrating when there is no clue where it goes wrong.
  • Least favorite thing about dev: I don't like it when the logic becomes too complicated to think through clearly, or too hard to test.
  • Tdd knowledge: no idea.
  • Why are you attending: To learn more about programming; to help implement the automation software/firmware test.
  • Back