Spoken like a true journalist with little dev experience :). Though I don't understand why you felt it necessary to go borderline insulting/condescending? Ohwell.
Funnily enough, yeah, I'm a bottleneck… though for the exact opposite of the reason you're giving. My employer doesn't do job titles, elsewhere I'd be a distinguished or principal engineer. I have about 22 years of depth of knowledge in my area. I'm there to answer questions, guide design decisions, review things and provide context. There isn't enough of me to handle all that, so, yeah, bottleneck. Which is solved by people around me getting things out of the way when they aren't related to my "scope" as you say, so I don't waste time on them.
But even for a junior dev, your comment makes little sense. You need to learn breadth and depth. If you're working at a project, you should rather stick to the existing tooling and go into depth, especially if a bunch of senior devs have put time and thought into finding a local optimium.
So, then, does your comment make sense for a midrange dev? Maybe. But even then, only if they're not having to get shit done. Your AI agent doesn't get to decide to introduce you to new tooling or a new ecosystem midway through a sprint. You do that shit when you're in the initial exploratory phase for a project, or tinkering with a pet project.
Maybe journalism is very focused on breadth? I don't know. I thought journalists also have their in-deep areas of knowledge? AFAIK your area of knowledge is cryptocurrencies and related — if the AI agent asked you a safety question about fiat banking, what would you do?
P.S.: 2 layers below HTTP is IP. I hope I didn't introduce a misunderstanding there, I'm not in a project where 2 layers above me there is HTTP. There is nothing above. That's just where we are, IP. We don't work on anything that is HTTP, anywhere in the entire company. (Well, sure, we have a website, but if I were to even think about spending time on that somebody would blow a gasket.)