VP Software Development
-
Caregility
May 2020 - present
I am currently Leading the Engineering teams at Caregility. My previous roles at Caregility…
- Dec 2021 - Feb 2022 | Acting VP of Software Development
- Jan 2021 - Dec 2021 | Technical Product Manager (Tech Lead & PM)
- May 2020 - Jan 2021 | Video Communications Software Engineer
AI Powered Software Test Automation
- Uses AI/ML to create unit tests for your code
- Integrates with your GitHub Actions CI Pipelines
- Developer tools to make your team more productive
- The quest for developer productivity is a long journey, our mission is to make it a bit easier
If you are a developer, you know that every Pull Request has its own story to tell. Whether it’s a bug fix, a new feature, or just a code refactor, each PR has a unique history. And, just like any good story, each PR has a beginning, a middle, and an end. The beginning is when the code is first written and the middle is when the code is reviewed and approved. The end is when the code is merged into the main codebase. But, of course, the story doesn’t end there. The code will continue to live on, long after the PR is closed. It will be used by other developers, and it will continue to evolve over time. That is why it is so important for a Pull Request to be well documented and easy for a future developer to come back to. For The Record automagically summarizes your PRs so future you can easy get the gist of what happened when it was merged.
SecureMeeting is on a mission to rid the world of bad video-conferencing. Create rooms, invite people, and have conversations without leaving a trace.