I fix things that break and try to design things that don't need fixing later. Started in desktop support, which mostly teaches you that the technical problem is rarely the real problem; the real problem is someone forgot to explain the network drive. From there: network administration, systems engineering, and now most of my attention is on cloud architecture and automation, because manually clicking through a console for the tenth time is how you learn to write Terraform.
I led the move from an on-prem environment to cloud infrastructure, which sounds cleaner in a bullet point than it was in practice. It was mostly piecemeal, as most of the business functions had to be re-coded from the archaic technologies to support modern options.
Philosophy and Approach
There's always a philosophy; here it's: systems reflect their architecture. Sloppy or short-sighted decisions early show up as outages later, and most "innovation" is just someone finally fixing the thing everyone agreed to ignore. I'd rather spend the extra hour getting the design right than the extra week explaining why it broke. I also agree with the saying that goes something like: there's nothing more permanent than a temporary solution.
Outside of Work
Outside of work, I've been getting into ham radio and trying to broaden my cultural experiences learning the Japanese and Italian languages... as I get time.
Reach out if you've got something worth building - Contact.