I am a husband, father, gardener, fish keeper and weekend warrior cyclist. In my professional capacity I am the Cloud Architect at Assima responsibility for security, infrastructure and deployment of the product at a software design level as well as in its deployed state. As part of my role I manage a small team of system administrators and software developers.
I’ve had a few successive promotions at Assima, each taking me to new and exciting experiences. My previous position was that of Technical Architect and Lead developer on the Core team where I was tasked to oversee the development of the infrastructure required for the WCF services.
I am now the cloud architect looking forward to identify and overcome the challenges to take Assima forward into the cloud by leveraging the abilities that the cloud provide around scalability and reliability.
Before working at Assima I was the co-owner of a small startup called Netready Software. Me and Richard Sletcher started the company in 2001 and after 9 years I decided to move on.
My roots are firmly based within software engineering and engineering practices. What do i mean with software engineering? There is a difference between a software engineer and a developer.
A software engineer takes a problem / business requirement, research, plan, design and implement the best technical solution to fit the business requirement while considering future maintainability, scalability and extensibility while a developer does the task assigned to him as quickly as possible without thinking about the larger issues at hand and within 2 years business finds itself in a situation that the code they paid for needs a major rework to deal with some variation.
I am a firm believer that a engineer should strive to understand the inner workings of the technology that he works with. The more in depth a understanding you have the better a engineer you will be.
It is difficult to put me in a box and say “This is what I can do as a person” as technology and requirements change every year, my skills change. In the end I help engineer sustainable business solutions.
I have 20+ years experience working mainly on back end systems using Microsoft development languages although I owe my OO foundation to Delphi and Pascal. I have been privileged to work for companies that valued technical knowledge and had a strong focus on planning, design and implementation.
I have worked on several types of application through the years ranging from stand-alone desktop application, client server applications, web applications, mobile applications and Enterprise level SOA based cloud solutions.
What I am doing now
Me and my team are responsible for all the cloud infrastructure, security and diagnostic. We are also responsible for scaling, deployment, integration and hosting. I fulfill the role of architect over these cross cutting concerns.
There are 4 architects at Assima, all serving on different teams. The cloud team is a non functional team while the others are all functional teams. Assima practices the IDesign method also called “The method“. The method is the design principle developed by Juval Lowy for developing service based application.