# Post | Feed | LinkedIn
URL:: https://www.linkedin.com/feed/update/urn:li:activity:6805047523200380928/?commentUrn=urn%3Ali%3Acomment%3A(activity%3A6805047523200380928%2C6805179606057017344)
Author:: View Profile
## Highlights
> James Leatherman 1st degree connection1st I used to do performance. I still do, but I used to, too. 1d The imposter syndrome we experience is largely due to the massive span of generalist knowledge we need as performance engineers. It can be very limiting, since you really cannot spend the time developing expertise in one area as well as a developer or DevOps engineer due to all of the distractions from other parts of a complex human-machine system. At the same time we are considering performance aspects of the entire stack, trying to communicate complex results, helping prioritize performance issues, and still living down low in test and application code, we also have to evangelize performance concepts in a way that makes sense to our audience. It is a tumultuous juggling act, and can leave you longing for times when you can just sit down and write code for a week. I don't know a solution for this, but I feel like Nicole is further ahead of most of us by concentrating on communication and mentoring in our changing scope of work.
---
Title: Post | Feed | LinkedIn
Author: View Profile
Tags: readwise, articles
date: 2024-01-30
---
# Post | Feed | LinkedIn
URL:: https://www.linkedin.com/feed/update/urn:li:activity:6805047523200380928/?commentUrn=urn%3Ali%3Acomment%3A(activity%3A6805047523200380928%2C6805179606057017344)
Author:: View Profile
## AI-Generated Summary
None
## Highlights
> James Leatherman 1st degree connection1st I used to do performance. I still do, but I used to, too. 1d The imposter syndrome we experience is largely due to the massive span of generalist knowledge we need as performance engineers. It can be very limiting, since you really cannot spend the time developing expertise in one area as well as a developer or DevOps engineer due to all of the distractions from other parts of a complex human-machine system. At the same time we are considering performance aspects of the entire stack, trying to communicate complex results, helping prioritize performance issues, and still living down low in test and application code, we also have to evangelize performance concepts in a way that makes sense to our audience. It is a tumultuous juggling act, and can leave you longing for times when you can just sit down and write code for a week. I don't know a solution for this, but I feel like Nicole is further ahead of most of us by concentrating on communication and mentoring in our changing scope of work.