I write code. It's not the best code in the world but it's good code. It considers the requirements of the system we need. Will it be run only once? Does it need to be 99.9% available. Who will use it? These answers drive design - every project is different. I once developed an algorithm to sort
I write code. It's not the best code in the world but it's good code. It considers the requirements of the system we need. Will it be run only once? Does it need to be 99.9% available. Who will use it? These answers drive design - every project is different. I once developed an algorithm to sort data in constant time - because I learned that the expected input was already ordered. I write code with consideration for the next guy who will have to read it or make changes to it - knowing that might be two-weeks-from-now-me. So I try not to make that person's life too difficult. I used to think a good coder does everything right the first time, but I've learned that a good coder does things wrong quickly, then fixes them quickly, then makes sure they don't break again. So I take testing seriously. I write unit tests, and integration tests, I take performance benchmarks, I run the system under load, and I think about how to automate operations to deliver faster, more reliable software.
I was a test engineer at Microsoft, then a product engineer on Windows 8 apps at Microsoft, and am now a backend engineer at Amazon working in Cloudwatch Logs, a distributed log monitoring application that is a part of AWS.
I focus on writing reliable and performant code with strong attention to quality of the end user experience.
Software Development Engineer @ AWS Cloudwatch Logs From July 2014 to Present (1 year 4 months) Seattle, WashingtonSoftware Engineer @ My first position at Microsoft was as a SDET for Trackpad Settings (http://apps.microsoft.com/windows/en-us/app/indstillinger-for-pegefelt/5a4e4cdf-4d60-4084-8d9f-61d2e8f4830b), a Windows Store Application for Microsoft Surface and Surface Pro that enables users to modify the settings of the Touch Keyboard for the Surface. On this team, I did end-to-end testing and wrote a set of driver security tests that exposed several critical bugs in the TrackPad Settings driver.
Afterwords, I worked on a secret project that was later announced, Surface Music Kit (http://surfaceremixproject.com/). Much of my experience has been on this team. As an SDET on this team, I was responsible for testing our audio effect and beat/pitch matching features, as well as some device simulation investigations. This involved writing reliable UI and component-level automation in C# and C++ for both UI and product components.
Looking for a different
Get an email address for anyone on LinkedIn with the ContactOut Chrome extension