As a fellow full stack developer, I can relate. I have been called out for using Optional too broadly in Java because I was trying to treat it like Rust, and I

As a fellow full stack developer, I can relate. I have been called out for using Optional too broadly in Java because I was trying to treat it like Rust, and I too need to research specific syntax and API on a daily basis. On the other hand, when our company was bought out and I had to change technologies fast I think it was an asset. A year and a half in and I am clearly a senior dev again. Not the owner of any domain anymore, but like the article says, someone they come to to bounce ideas off of, and someone who can identify the cross domain architecture deficiencies with a concept of how to fix them. Also because I have to research constantly, once in a rare while I stumble across an elegant solution the domain experts weren't aware of.