Powerful Lessons From Splunk I’ll Never Forget

While working at Splunk over the past eight years, I’ve had the opportunity to work with incredibly wise people. It’s important to note that I joined the company as an intern before my junior year of college, these years were extremely foundational for my career and life overall.

There’s a long list of colleagues I’ve learned from, but these five people made the greatest impact on me. Some of these lessons came from projects we worked on, conversations we had, or simply their modus operandi. Over the years I’ve passed these lessons on to others, and hope to continue doing so.

Itay Neeman

Lesson: It’s not right until it’s right.

For any field, receiving project feedback early in your career can be frustrating. That feeling only compounds with additional feedback after multiple revisions. Before I worked at Splunk, I hadn’t gone through a real code review process. At previous internships I wrote some code, if I thought it worked that was good enough. After receiving very thorough feedback on a few code reviews (from multiple coworkers, after multiple revisions) I began to embrace an iterative approach to software development. Making 20 revisions is better than making 19 with a critical issue. It’s a mindset that I’ve applied to creative projects as well…