Course code: WEB-30
  • Years with company: 2
  • Years programming: 4
  • Primary programming language: C++
  • Other programming languages: Python, C, JavaScript, Haskell
  • Unit test harnesses: pytest
  • Something else: I enjoy programming and especially in the embedded context. It seems to me quite special to be able to program instruments and small devices. I am new to embedded programing and despite its initial challenges, what I have found most difficult is to organize a decent method of working within this domain.
  • Test practice now: Hardware Prototype in loop, trial and error.
  • Target system: 8 bit and 32 bit low end Microcontroller based Instrument Control Systems. These in some cases work in tandem with an Embedded Linux based HMI written in C++/Qt.
  • Dev tools: STM32Cube, Viusal Studio Code, Visual Studio, Qt Creator, Vim
  • Build time: Under 10 seconds
  • Coding standard: C++ coding standard guidelines
  • Function too long: If a function does more than one thing, or if it mixes pure computation and IO, I try to separate them.
  • Code reviews: No review process in place. Static analysis tools - not in embedded.
  • Code time: 10
  • Test time: 30
  • Debug time: 60
  • Favorite thing about dev: Building Abstractions that lift the semantics of the code closer to the domain of the project.
  • Least favorite thing about dev: As project size increases, new requirements are brought in - things can start becoming quite complex due to the hidden dependencies they have on each other.
  • Tdd knowledge: I understand its (immense) usefulness and do depend on tests to have confidence in the code I have written. However, I do no know of testing outside of Unit tests.
  • Why are you attending: I had a really bad experience on the previous project. I don't want to be in such a position again where my code is so fragile. Needing hardware in loop when programming embedded systems - I would like get out of this.
  • Back