2015, I moved to the greater Milwaukee area to launch a new DISTek
office. At the time, I was the only employee in the area but we wanted a
temporary office we could use to accommodate our growth prospects in this
region. We managed the “growth” reasonably well, growing to 8 employees
here … but the “temporary” extended a little longer than expected. Though
we started with a 14-month sublease, we ended up staying for three and a half
years. That all changed in December when we moved to a new office
location. We packed up everything during the end of November and the
first part of December, then made the move on Friday, December 14.
Eliciting a set of user stories can be a challenge when stakeholders are not sure where to begin their description of the solution they require. It is often up to Requirements Engineer (RE) to guide the stakeholders along in assessing the problem in need of a solution, as well as assessing the best solution for the problem. The RE must further help the stakeholders partition the solution’s description into manageable tasks, and express those tasks as User Stories. Workflow Driven Elicitation (WDE) is a systematic approach that helps achieve all of the above.
Monday October 22 was a pretty exciting day, the day DISTek recognized the first set of graduates from DISTek U. These 7 graduates completed all the coursework required of the Potential Leads Track, which included reading and answering discussion questions for the books How to Win Friends & Influence People by Dale Carnegie, The Five Dysfunctions of a Team by Patrick Lencioni, and Smarter Faster Better by Charles Duhigg. They also attended 7 Habits of Highly Effective People leadership training, and gave a presentation to the class and management team on their key takeaways. The group also heard from four current DISTek leaders on their perspective of being a leader, which was a highlight of the class. Below are some of the thoughts and experiences on the training from some of the graduates.
In my personal projects, I often work with various sensors which require digital data verification. One such sensor required the use of a Cyclic Redundancy Check (CRC) to verify that the information that the micro-controller read from the sensor was being received correctly. A CRC is a method for calculating a checksum from an array of data. The software examples that I was able to find to develop my understanding of implementing a CRC were poorly documented. Moreover, these examples were often so optimized that the underlying behavior was not immediately recognizable. Many examples simply used a lookup table---which provided no satisfaction for my "what-makes-it-tick?" personality.
The most recent AEFISOBUS Plugfest was held just a little over a month ago, during September 2018. We returned to the Savoia Regency Hotel in Bologna, Italy, where Plugfest had previously been held in 2016.
On Thursday, November 1, 2018, at 11:00 AM, DISTek will be giving a 45 minute presentation entitled: The Functional Safety in Autonomous Vehicles Is Not an Afterthought, at the Embedded Systems Conference (ESC 2018), held at the Minneapolis Convention Center.