James Duffy

First 30 Days of Being a Full-time Software Engineer

// By Updated:

Three months ago, I embarked on an exciting new journey as I started my first full-time job as a Software Engineer. As I look back on my first 30 days, I am thrilled to share the accomplishments and the positive impact I’ve made in my new workplace.

Upon my arrival, I quickly realized there was no server monitoring in place, leaving my team in the dark about real-time infrastructure usage. Determined to address this, I spent my second week setting up collectd on each server, as well as establishing a central InfluxDB and Grafana monitoring server. Since then, we’ve made some modifications, but the most significant change has been installing a TV in the office to display real-time usage for the entire team.

Thanks to the monitoring system I implemented, we’ve been able to identify and resolve issues proactively, preventing them from escalating into more significant problems.

In my third week, I captured a screenshot of Grafana that perfectly illustrates the impact of my work. Around 11 am that day, we deployed code containing numerous performance enhancements I had developed for our application. Initially, we were concerned that something had gone wrong, as we hadn’t anticipated such a dramatic improvement in performance. To our delight, the changes I made were genuinely that effective, and I couldn’t have been happier with the results.

Since then, I’ve continued to make substantial strides in my role, and I am more motivated than ever to keep pushing forward. My journey has only just begun, and I eagerly look forward to the challenges and opportunities that lie ahead.