Course code: BD-1
Years with company:
Primary programming language:
C hashtag (aka C#)
Other programming languages:
Unit test harnesses:
I enjoy snowboarding in the winter time and I live in Baltimore, may pursue an MBA in the near future.
Test practice now:
We start using device simulators to run a "simulated run"
Then we basically make sure it didn't break any unit tests, which are mostly integration tests in our case.
Then we take it to a real instrument and test the code on the instrument, if it works it's usually approved for a merge.
Lots of devices which we connect to by creating objects to represent them via XML Configuration files, we have "Device Simulator" versions of these Devices for running in simulator (testing) mode.
Node, Sql Server Express, Git, Visual Studio Team Services, NuGet
Pretty strict regarding how we follow our design patterns. Our solution is heavily based on a factory model.
Function too long:
When it can easily be reduced to more testable units -So its modular and you know everything about the method by reading its Description and Title
We require 2 reviewers for any merge - usually people who are the most knowledgeable of the areas of code you're changing.
Favorite thing about dev:
I like to solve problems - I like thinking about things in terms of modular components which can be combined and moved around to achieve different outcomes.
Least favorite thing about dev:
I don't like when it takes forever to test something
I don't like long build times
Fixing bugs that should have already been fixed.
Write tests before methods are written
Why are you attending:
I have to