Course code: SAND-1
Years with company:
Primary programming language:
Other programming languages:
Matlab, LabView, Python.
Unit test harnesses:
I've been trying out Ceedling.
I'm an early career EE. I have done a fair amount of circuit design and hands-on lab work. My new position is almost entirely embedded software focused. I definitely have a lot to learn, and would like to be able to work faster.
Test practice now:
Before ceedling I'd often test code using print statements or toggle pins if testing on hardware. For timing critical testing I might throw test data into an array and print it all at the end. But that took a bit of extra work and system overhead.
I really like Notepad++
My team uses a modified version of the Barr group's Embedded C Coding Standard. We kept most of the rules with technical rational and modified the more subjective stuff.
Function too long:
I try to build functions that do only one thing. But, that is easier said than done, and pinning down what "one thing" really means can be tricky.
My team only just formed and hammered out our code standard. We haven't had any code reviews yet, but plan to.
Favorite thing about dev:
I like using logic to solve complex problems. I also really like the results, getting hardware to perform tasks and/or automate processes.
Least favorite thing about dev:
It's time consuming and can be somewhat tedious.
I've been watching Bob Martin's Clean Code videos and have started using it with Ceedling. It seems like a good practice and I'd like to develop a proficiency using it.
Why are you attending:
As my software team has just formed we decided since we are just starting out we might as well try to establish good habits from the start.