Course code: ACL-1
  • Years with company: 1
  • Years programming: 10
  • Primary programming language: C
  • Other programming languages: C++, Python, JAVA, PHP, C#, Assembly, JS and others.
  • Unit test harnesses: Cppunit, Google Test
  • Something else: I am a person who enjoys understanding every aspect of the technology. I like also sports but as I have very few free time I usually go to the gym. I try to be proactive and I never give up once a problem comes up.
  • Test practice now: Good question... In every company I have worked for, testion is a recurrent word that appears but, because of the tight delivery times the testing has been always avoided. Here, in ACLARA, our team leader is trying to change this. I had the chance to use CPPTEST but not in production.
  • Target system: Only about one? Right now the Renesas IC is a bit unknown. I now it is a 32 bits system, its endianess, some aspects of its configuration using its registers, peripherals... But all this, or most of all, is handled using a HAL layer.
  • Dev tools: Here in ACLARA we use IAR compiler for the target and MinGW for the tests using CMAKE to handle the tests and to build each of them. I like to code using vim (using cygwin now, because the use of Windows is mandatory) or VS CODE.
  • Build time: 5-30 minutes
  • Coding standard: For testing, it should take just a few minutes (I am not currently using the CMAKE testing environment that is being used)
  • Function too long: I try to use the cyclomatic complexity as metric. I try to have only one return point if it is possible. Besides, if I think the function is complex I try to break it down just thinking a bit
  • Code reviews: There are not code reviews right now. I have worked before using pair programming method and it worked well.
  • Code time: 10
  • Test time: 60
  • Debug time: 30
  • Favorite thing about dev: Everything. I like how developing SW helps you to think in a different way. Finding a solution to a problem or implementing a feature makes me feel good as I see the code working. I like to find the best way to reach to a solution.
  • Least favorite thing about dev: Sometimes you cannot understand everything. I don't like to have blind points... Because, usually those points turn out into serious problems.
  • Tdd knowledge: Just some theory. I think that is pretty hard to use it, or use it well, with the preassure and tight deadlines we have in our sector. But I am willing to see it being applied just to grant that our code is developed properly.
  • Why are you attending: I want to learn how to organize and reach to our goals in a better way. I have been following Barr Group for years and I think I could learn a lot from your trainigs. That is why I recommended Barr Group's trainings to the company.
  • Back