Hannu Piki Email & Phone Number

Eventually everything fails, especially in the cloud... so why not to build system that can recover from it?My main focus is usually on reliability and reducing manual work in all reasonable areas. Doesn't matter if it is applying the change or just reviewing the specifications to see if something can be improved. While head is full of ideas, some of them might even work for real? Have to take them for a spin or otherwise you never know!I have long history of developing different kind of system as a full stack developer before transformation to being site reliability engineer. I have been participating with many kind of integration solutions, for example HR, CRM, ERP, company and bankruptcy registries and web stores etc. Many of those has been projects I have been in responsible to lead and get them done, in some I have been "just" a developer.Knowledge I gathered as a developer, I have been strongly using while reviewing software/feature specifications, building IaC, CI/CD pipelines or whatever tools that I or someone else have ever needed. Those multiple positions along the road have created many different point of views I go through when facing a new challenge or just when reviewing current state of things.When I started my SRE journey, whole scene seemed to be so scattered. Even the name for the job tittle did divide people. I can't say that it is clear even now, but at least there seem to be quite good common ground what it does require to have robust and scaleable environment in your hands. Technical approaches might differ between companies and teams, but milestones between current state and the goal are getting more clear every year.

Listed skills include .Net, Asp.Net Mvc, Microsoft Sql Server, Iis, and 14 others.