Hi, I'm
Software Engineer
+
- I began working with relational databases while working as a business analyst. Since, I have made extensive use of MS-SQL almost daily and yet the technology is so powerful I still feel I have much to learn. As of writing this, most recently, I re-designed a very poorly written stored procedure, 2000+ lines of purely unmanageable spaghetti acting on a single dataset to create a report, by breaking the code into logical chunks using table-valued functions and a user-defined type resulting in something understandable and runs in half the original time. + I began working with relational databases while working as a business analyst. Since, I have made extensive use of MS-SQL almost daily and yet the technology is so powerful I often continue to discover new functionality. As of writing this, I recently re-designed a very poorly written stored procedure, 2000+ lines of purely unmanageable spaghetti acting on a single dataset to create a report, by breaking the code into logical chunks using table-valued functions and a user-defined type resulting in something understandable and runs in half the original time.
T-SQL, MS-SQL, MySQL- + Frequent fetches to address conflicts. Frequent commits and pushes to save and safely store work and to allow others to address conflicts. Finally, a pull request to merge changes with a master branch. Source control is a simple concept, albeit serving a critical function, and I believe I'm taking advantage of its primary benefits. Admittedly, it's not a topic I've invested much research into so I may later discover that I'm wrong.
TFS, Git, TFVC- + My company has entered the DevOps world extremely late and still has not quite embraced the potential. Having recognized the value good DevOps can bring, I have pushed for this extensively up to creating our first build, test, and release pipelines to showcase the potential and benefits. We are an on-premise company so this meant working with YAML directly as the hosted pipelines are unavailable.
Azure DevOps, YAML+ Although development is my passion, I have a wide breadth of other skills that accentuate my abilities to create good solutions; key among these is my ability to define and measure a problem, analyze it to find an improvement plan, and finally implement a controllable solution. +
+ Problem Solving, Statistics, Mathematics, Engineering, Lean Six Sigma, Data Analysis ++ + Blazor (client-side), C#, Bootstrap, HTML, CSS +
++ This site. I won’t say much about it since by reading this, you are experiencing the work first-hand and can draw your own conclusions. Admittedly, I took design inspiration from others’ (color theme and layout) but the coding is entirely mine. +
++ + Blazor (server), C#, T-SQL, Bootstrap, HTML, CSS +
+
+ This project is used by my wife and me to make grocery shopping easier. A user picks which recipes he/she wants to make for the two-week period and a grocery list is aggregated automatically showing specific ingredients and quantities. The user then checks off the things he/she already has and is left with the remainder to go shopping. The user can also add non-meal related items to the list.
+
+
+ The main challenges in this project were deciding how to control the user’s choices when creating a recipe (ie. ‘eggs’ vs ‘carton of eggs’), allowing the user to use various units for quantities, and maintaining proper sync if my wife and I were using the app at the same time – we only have one grocery list for both of us.
+
+
+ The app could be improved by implementing a good database-driven inventory system that adds and subtracts according to which meals are eaten and according to expiration date and automatically removing the items that are already available.
+
The image on the right is the login page. The logo is an SVG that I created for this project and I tried to stay with the theme throughout the application. I don't recall from where but I was inspired by another logo. The app was designed with mobile-first in mind as I imagined it being used in a grocery store on a phone or tablet.
+
+ 
+ The image on the left is the menu. It scrolls down to show a two-week period.
+The image on the right is of the grocery list that is generated from the selected menu. The unit each item is converted to is chosen according to the magnitude of the item to be user-friendly. Items are checked off using an SVG swap of an image consistent with the logo.
+
+ + + Winforms, C# +
+After creating a few WindowsFormApp1, WindowsFormApp2 applications I realized that I could save time by making re-usable code and create permanent reference to remind myself how to do things that I’d once discovered and forgotten by doing it inside a persistent application. To that end, I created this application to practice and share ways of doing things I was learning with my colleagues.
+The image on the right is a list of the topics I have decided to add to this library over the years.
+
+ 
+ The image above is a snippet of an asyncronous progress bar form that opens when topic two is selected. Note that async and parallel functionality is accessible. The application serves to show how each behaves and allows the user to toggle them.
+The command pattern is one of the coded design patterns. It is one of my favorite patterns. This view below allows the user to drag the boxes around the screen with the mouse, to move the boxes with the buttons, to move the boxes with the keyboard, and to undo any of those moves with the undo button using the command pattern with an Execute and Undo logic and a Stack object with stack and pop logic.
+
+ + + Ignition, Python, PLCs, T-SQL +
+This project is one of the first manufacturing automation projects that I've worked on. I suggested and supported with data the idea that introducing Indutive Automation's Ignition to replace some of our very old RSView applications for HMIs would be a cost savings and a significant improvement for manageability. The HMI would communicate with our casting furnace PLCs to perform the casting process and communicate with SQL to validate inputs and outputs. As an added bonus, recipe management is now also handled in the HMI with a backing SQL database where as before, the recipes were simple notepad files that were being parsed by RSView. Due to some unexpected circumstances causing a huge priority shift, the project went from infancy to deployed in a little under a week.
++ + Winforms, C#, DevExpress, T-SQL, Statistics +
+The Engineer's Toolbox started out as a tool written for myself to perform data analysis. Later, I modified it to be usable by others and released it as a tool for engineers to quickly gain insights, especially on dimensional data. Some of the most useful features are: Quickly identified dimensions (features) by percent of non-conformance, calculating leadtimes and expected yields based on WIP, and calculating statistics on a subset of product.
++ + Azure DevOps, YAML +
+I created my division's first automated pipelines using Azure DevOps. We use an on-premise solution so the build pipeline required a manual setup since the hosted build pipelines were not available. Additionally, I established an approval gateway to prevent breach of policies stating approval are necessary before release. The process was straight forward and I documented it for future use.
++ + Blazor (server), ASP.NET, C#, T-SQL, Bootstrap, HTML, CSS +
+This is a fairly new project. Presently, our entire system is comprised of hundreds of seperate applications performing extremely specific tasks. In order to reduce complexity and to maximize code re-use, I am planning to fully replace the system with an ASP.NET backed Blazor (server-side) solution. This change will pay for itself very quickly due to the amount of optimization opportunity that exists for both the development and user sides of these applications. This project is set to begin immediately after a blocking issue is resolved.
+