Joseph Michael Cauley
Software Engineer
jmcauley04@gmail.com
I have 6+ years working primarily with .NET and the Microsoft suite, I am an effective problem solver. Dependable and organized with a passion to learn, to be challenged, and to have a meaningful impact. Trained in mathematics, data analytics, and problem-solving methodology, I create innovative solutions that solve problems and exceed expectations.
| Backend | Frontend | Database | Devops | Softskills |
|---|---|---|---|---|
| C# | Blazor / Razor | T-SQL (MS-SQL) | Azure | Team-oriented |
| Entity Framework Core | MVC | DB2 | Agile Workflow | Great Communicator |
| Class Library Development | ASP.NET Core | Oracle | Azure Pipelines | Critical Thinker |
| API Development | HTML5 / CSS3 | Azure DB | GitHub Actions | Problem Solver |
| Automated Testing | CSS Grids | 3NF (Third Normal Form) | Git Source Control | Motivated to Learn and Improve |
| Azure Functions | Bootstrap | -- | Microsoft's Trunk-based branching strategy | Accountable |
| Rust | Winforms & WPF | -- | Kubernetes | Confident |
| -- | Angular / TS | -- | Docker | -- |
| -- | JavaScript | -- | -- | -- |
Canopy is an external vendor that provides our business electronic media (images of products) to be used in our applications. Tasked with creating a proof of concept to show the functionality of their API and then to introduce it to our developers, I created a fluent interface class library as a mediator to convert Canopy domain knowledge to our business domain knowledge allowing our developers to use strongly typed and familiar properties to interact with the API.
Our business began an initiative to containerize our new applications in a Linux OS and I volunteered to help define this process. First, locally, I resolved various issues with Windows dependencies (IBM’s DB DLL, Windows Auth, etc.). In the end, I created a pipeline in Azure Devops that utilizes the project’s dockerfile to build and deploys to our Rancher environment using YAML configured environment variables, clusterIPs for pod-to-pod communication, and ingress.