Course code: BAX-1
Years with company:
3 years 8 months
1 year full time/professionally
Primary programming language:
Other programming languages:
C and Python (limited experience)
Unit test harnesses:
I really like being outdoors to explore and see the incredible variety of scenery we have in Minnesota and other states I've been able to visit.
Test practice now:
Using a debugger, trying the code on the system, and adding in test functionality that can run while the system is live (for example, changing a temporary test global value to be what's needed to inject a failure value in to see that system behaves correctly)
1 main processor running the application on a real time operating system (Green Hills), 3 bare metal processors that perform other secondary/safety functions of the system
Green Hills Software MULTI debugger and SlickEdit
has good guidelines for naming and formatting, not a lot of other opinions about it at the moment
Function too long:
When it's difficult to understand or does too many unrelated tasks that need to be broken up
They seem to focus (in general) on simple coding standard fixes when schedule is rushed, too late and rushed for it to be useful for making design improvements
Favorite thing about dev:
I enjoy testing my own software to think of all the ways I need to verify and prove it does what I want it to.
Least favorite thing about dev:
Pressure to get things working quickly
Unit tests are defined and written before the code is written. All tests should fail initially. As the code is completed, more tests will pass until all tests are passing. That's when coding should be complete.
Why are you attending:
I'm technically being required to go, but I am really excited about the topic, and look forward to learning and applying new ideas to my development skill set.
If it was optional, I would still be attending.