Course code: WEB-34
  • Years with company: 5
  • Years programming: 36
  • Primary programming language: C
  • Other programming languages: C#, C++, Java, Groovy, Gradle, Pascal, Python, Awk, Javascript, GroovyScript,
  • Unit test harnesses: CppUnit, CuTest, Spock, Selenium, SoapUI, LoadBear, JUnit, Jasmine, NodeJs, Visual Studio
  • Something else: Debate and Commit. I only need to hear your opinion once. If you have nothing new to add, saying it again louder does not make you more right.
  • Test practice now: Developers use Brute force, Product Assurance (PA) does black box testing.
  • Target system: IAR - STM32, MSP430
  • Dev tools: IAR, VSCodium, Meld, AStyle, Git (migrating from SVN). Visual Studio 2019, Corporate provides Git, Jenkins, Sonar Qube
  • Build time: 31-60 seconds
  • Coding standard: Defined set of rules for ASytle which are generally followed.
  • Function too long: That concept does not exist within the business.
  • Code reviews: Up to this point had Subversion as VCS, are now in process of migrating to Git. Once we are on Git will be using pull-requests for code reviews. Up to now it was by using a patch or by examining changes once committed.
  • Code time: 6
  • Test time: 2
  • Debug time: 2
  • Favorite thing about dev: making code that: 1. does what it is supposed to do, 2. is easy to maintain 3. is easy to understand 4. is done right the first time
  • Least favorite thing about dev: Stake holders that tell how to write code to meet a requirement instead of stating the requirement. Usually preceded by "Can't you just" or "All you need to do is".
  • Tdd knowledge: 1. Will require more effort from developers 2. Will require change in the process followed. Because of the items listed, it is doubtful that it will be embraced.
  • Why are you attending: Will do just about anything in an attempt to change the current process.
  • Back