This project was focused on creating a robot for the purpose of inspecting areas around Jefferson Lab. Its main focus is the data center at Jefferson Lab which has small corridors (about 4 ft in width) for the robot to traverse. Also, the robot has an extendable, controllable elevator with a camera at the end point; so the viewer can adjust the height of the camera as well as the camera angle. ...
Created a checkout system from scratch using such tools like: Blazor Server ASP.net Visual Studio Git CI/CD dotnet tools Functionality: Ability to add future reservations ontop of current reservation This required some brain power Automatic color changes depending on status of item Send an automated email to a specific address about the status of an item Search through Active Directoy (or LDAP) for users at the organization Lessons Learned: Making a usable and effective UI is achieved by getting advice from many testers of your application It is preferred to at least pair program with one other individual or use the “Rubber Ducky debugger” where you talk design problems out to understand them better C# is a very diverse language with many features Visual Studio is not my preferred IDE ASP.net framework feels a little clunky, but dotnet tools are easy to use ASP.net libraries can be a burden to use with version mis-matching errors Learned how to publish a .NET app through IIS Server on Windows Server with an Microsoft SQL database Learned how to build a .NET app in a container and use MySQL instead and connect two or more containers together
A complete UEFI toolkit with some nice EFI applications. Tools used: EDK2 EDK2-libc EDK-platforms docker (podman) edkrepo utility Lessons Learned: EDK2 toolkit has many repos associated with it and using the edkrepo tool and a container is essential Make sure you are building an EFI file for the correct architecture UEFI is pretty much its own operating system - similar to DOS Got VIM working under the EFi shell using this program
Project created to filter and output under JSON infiniband switches and nodes. Tools used: Rust cargo cargo unit tests cargo-llvm-cov clippy Git GitLab CI/CD Partial source code can be found here Full source code can be found here Lessons Learned: Cargo clippy is a really great way to clean your code and put it up to the standards recommended by the rust book - commit 21cf79e3 cargo llvm-cov is a great way to ensure code coverage cargo fmt: easily format a rust file cargo install [package]: easy way to add libraries Rust is entirely different from C or C++ in how it handles returns where the language revolves around Option<> and/or Result<> Sort of a hybrid between C and C#? CI/CD is basically where you run build, test, deploy steps to your app - commit 21cf79e3 This is achieved by the system through regular container images and running commands inside of them for each step For example, in the build step, I can download a container specific to rust and run cargo build and, if there are any warnings/errors, CI/CD will let me know