


The Problem With Solving Problems
As engineers we pride ourselves on problem solving. That’s what we do. However I find the use of the word problem to be somewhat problematic (pun intended).
When we use the word problem, typically we are referring to something that is not working. Often it was working, but for


Gang Of Four Patterns in LabVIEW
I have written a bit about design patterns previously. Recently Tom McQuillan and I were talking about how it would be nice to have examples on how to implement the GOF design patterns in LabVIEW. To be fair, Elijah Kerry put together some great examples several years ago, but he




Docker in Action
Note: for more on Docker itself, see here.
Chris Stryker has recently put a lot of effort into getting LabVIEW to run inside of a Docker Container. This is really exciting news. I think this is really a huge step forward in improving Continuous Integration (CI) with LabVIEW. It offers



August 2020 Webinar
Be A Craftsperson
August 26, 11:00am MT
The way we think about coding and the way we approach it has a huge impact on our results. Approaching software from a craftperson perspective helps us to produce high quality valuable software.
Sometimes we feel like firefighters running around putting out




Automatically Creating A Gitlab Repo
I’ve been working on streamlining some of my processes lately. I noticed that one of the one things that takes a little time is creating a new GitLabRepository. It just seemed like it took too much time.
Here are the previous steps
1. Goto GitLab Webpage
2. Login
3.




What does scalability actually mean?
So recently the question of scalability came up on an NI forum post. Stephen Loftus-Mercer (aka AristosQueue) made a very interesting point. He talked about how scaling can mean many different things to many different people. A solution that is scalable on one axis might not be scalable on another.






June 2020 Webinar
Technical Skills For Agile Development
June 24, 11:00am MT
Agile has a lot to say about how we manage the software development lifecycle, but it requires good technical skills to be successful.
Often we get caught up in the software development lifecycle side of agile software development. It is