Course code: WEB-24
Years with company:
Primary programming language:
Other programming languages:
C++ from time to time and I'm starting to use python.
Unit test harnesses:
Ceedling, started to use pytest for python.
In the team the hardware/firmware guy so I also design the schematic and PCB. So coding is only one part of my work.
Test practice now:
Before reading your book I was writing code, building the code, pushing the code on the target and verifying in debug mode that the code I just wrote was working as intended.
After reading your book I started to use ceedling to unit test my code. So now I'm coding and testing my code on the computer and when a bunch of module are ready to work together I to the same as previously but with less step by step debugging and more global verification like verifying the outputs with oscilloscope or logic analyser.
I'm currently using STM32F3 and F4 microcontroller families.
Eclipse + gcc for arm + openocd.
I'm using coding style based on the Linux Kernel coding style with some modification to better fit embedded world.
Function too long:
When making unit test for a function is too hard I try to reduce the size of the function.
We don't have code review as we are a small team.
Favorite thing about dev:
Adding new functionalities and seeing them working as expected.
Least favorite thing about dev:
Debbuging hard to reproduce event which are reported with only few information by tester / customer.
The goal is to write test before the functional code.
Every code functionality should be requested by test.
This allow to find errors at the moment they are introduced and ease their correction.
Why are you attending:
I'm not happy with how many errors I introduce to my code at the moment.
I started coding in a TDD way but I'm too slow at it. So when deadlines approached I skip TDD and more errors are found latter.
So my goals are: better and faster.