Antony Church

At Kroo I am a technical lead on a product team. I help organise and prioritise work coming in to the team whilst helping to maintain the technical architectures and design patterns. I also work with the other technical leads on improving our architecture and development practices. Our tech stack is Clojure, Postrgres and Reactive Native. I work with all of the technologies on a weekly basis in differing amounts dependent on the current task.

At Codurance was a Senior Software Craftsperson and a Feature Lead. Codurance is a consultancy which prides itself on software craftsmanship with one of the founders being an author of the book "The Software Craftsman". Whilst working at Codurance I mainly worked with a medical transport client as a feature lead with a team of 4 developers of differing seniority levels. Being a feature lead meant organised the work that was coming in to the team and to help the business analysts and product owners shape the work items into something deliverable. This often involved a compromise between technically possible and usable by the end users. I also helped keep my team heading in the right direction with regards to technical decisions and implementations. The part of the project my team worked on the most is a cross platform mobile application for delivery drivers written in Xamarin communicating with a C# backend. We often also did work in the main application which was part Blazor but mostly .Net MVC using a RabbitMQ cluster to push messages around the system and between services. At Codurance I was also heavily involved in the recruitment process and general give at least one technical evaluation a week.

At Calero MDSL I was a Senior Software engineer working on a remote team that was half UK based and half US based. The team I worked on had the main objective to convert an existing Angular project into a React project to bring it in line with other software written within the company. The software itself is for Technology Expense Management. The front end project was backed by a C# ASP.Net API with SQL Server supporting the database queries and the software was deployed to Microsoft Azure through an Azure Build Pipeline.