Staff Software Engineer
One of Corista's more recently developed components is a prototype that got shipped, which presents a resource challenge: only its primary author can work on non-trivial feature additions. What I did about this:• Survey internal users of the component to understand where it was working acceptably and what will have to change for it to satisfy their needs;• Integrate Checker Framework into the build procedure, as an example of a tool that finds latent bugs using static analysis;• Use Checker Framework warnings to guide an internal API refactoring, and overhaul the implementation to a standard of "zero warnings (with a small number of suppressions)";• Integrate Behavor-Driven Development tooling (Cucumber, Serenity) into the build, and write the first few "screenplay" browser automated tests to solve Basic Auth and unblock QE;• Return ownership to the dev team, not with an attitude of "it was bad and I fixed it", but quite the opposite: praising the good bones of the prototype's design, which supports a plugin model that will make its integration team happy on an ongoing basis once reliability/performance issues are resolved.There is a broader challenge of team cohesiveness, with almost all of the engineering staff fully remote. I got a good start on working on that, but some miscommunication around a medical issue cut my time at Corista short.