Tyler Busse Email & Phone Number | Fresh out of college if someone would have told me that I would be a software engineer I might have laughed at them. My economics degree surely would take me to be an analyst of some sort. Maybe I'd query a database or write a R script but a full blown engineer seemed out of reach. However, my experiences as a Data Analyst at Revolution Retail Systems would shape me into one. My main job as a Engineering Data Analyst was to analyze issues from the field and categorize it as a hardware, software, or training problem. Revolution creates cash and coin recycling units for retail stores as a way to automate backroom accounting. Usually these issues were accounting imbalances that we needed to remedy based on their cause. Many of our tasks were manual processes that we had to repeat daily, so in my spare time I learned some basic scripting in Python and SQL to help automate some of our workflow. Writing my scripts and watching them do my work was oddly fun. Before I knew it, I was pawning off most of our manual processes and some of our analysis off to microservices in Azure and storing it in an Azure SQL Server I managed. This gave me more time to analyze how our machines worked and solve issues. Reading through device trace logging can only get you so far in properly dispositioning an issue. I was given access to the desktop app's code base so I could truly understand the problem. I began to learn how it worked by cross referencing logs, user stories, and the code. Our application was written C# so I decided to go learn C# and WPF through videos, documentation, and leaning on a few engineers who served as mentors to me. Not long after, I had become an exterminator, rooting out bugs in our code and even fixing them. It was almost like solving a puzzle and became strangely addictive. My passion and enthusiasm for solving these problems eventually led to a transfer to software engineering where today I spend my days implementing new features, cleaning up bugs, and learning as much as I can. Whether it be through discussion with my teammates, reading a development book, or browsing Stack Overflow for advice, I am always looking to add skills to my repertoire and sharpen the ones I already have.

Tyler Busse

Fresh out of college if someone would have told me that I would be a software engineer I might have...
Dallas-Fort Worth Metroplex, Dallas-Fort Worth Metroplex, United States

*50 free lookup(s) per month.

No credit card required.

Tyler Busse’s Email tbusse@revolutionretailsystems.com

Tyler Busse’s Phone Numbers

Get TYLER’s Phone Number (For Free)

Social Media

Tyler Busse’s Location Dallas-Fort Worth Metroplex, Dallas-Fort Worth Metroplex, United States

Tyler Busse’s Current Industry Revolution Retail Systems

Tyler Busse’s Prior Industry Ntt Data Services | Buffalo Wild Wings

Not the Tyler Busse you were looking for?

Find accurate emails & phone numbers for over 700M professionals.

Work Experience

Revolution Retail Systems

Software Engineer II

2022-01-01 00:00:00 - Present

Ntt Data Services

BSA / AML Compliance Analyst

2016-11-01 00:00:00 - 2018-02-01 00:00:00

Buffalo Wild Wings

Bartender

2012-04-01 00:00:00 - 2017-06-01 00:00:00

Skills

No Skills Available

Languages

No Languages Available

FAQ About Tyler Busse

Tyler Busse is located at
Dallas-Fort Worth Metroplex, Dallas-Fort Worth Metroplex, United States

Tyler Busse is a Fresh out of college if someone would have told me that I would be a software engineer I might have laughed at them. My economics degree surely would take me to be an analyst of some sort. Maybe I'd query a database or write a R script but a full blown engineer seemed out of reach. However, my experiences as a Data Analyst at Revolution Retail Systems would shape me into one. My main job as a Engineering Data Analyst was to analyze issues from the field and categorize it as a hardware, software, or training problem. Revolution creates cash and coin recycling units for retail stores as a way to automate backroom accounting. Usually these issues were accounting imbalances that we needed to remedy based on their cause. Many of our tasks were manual processes that we had to repeat daily, so in my spare time I learned some basic scripting in Python and SQL to help automate some of our workflow. Writing my scripts and watching them do my work was oddly fun. Before I knew it, I was pawning off most of our manual processes and some of our analysis off to microservices in Azure and storing it in an Azure SQL Server I managed. This gave me more time to analyze how our machines worked and solve issues. Reading through device trace logging can only get you so far in properly dispositioning an issue. I was given access to the desktop app's code base so I could truly understand the problem. I began to learn how it worked by cross referencing logs, user stories, and the code. Our application was written C# so I decided to go learn C# and WPF through videos, documentation, and leaning on a few engineers who served as mentors to me. Not long after, I had become an exterminator, rooting out bugs in our code and even fixing them. It was almost like solving a puzzle and became strangely addictive. My passion and enthusiasm for solving these problems eventually led to a transfer to software engineering where today I spend my days implementing new features, cleaning up bugs, and learning as much as I can. Whether it be through discussion with my teammates, reading a development book, or browsing Stack Overflow for advice, I am always looking to add skills to my repertoire and sharpen the ones I already have.