This is often a signal for bullshit though. If people can't comprehend what you're doing, it's often because that's not their job. It doesn't have to be hard t

This is often a signal for bullshit though. If people can't comprehend what you're doing, it's often because that's not their job. It doesn't have to be hard to be incomprehensible. A large code-base built in the most simple language is incomprehensible to the person who hasn't put in the time to crack open some files. The value in code is in getting customers to pay for the product and for you to be a good person on the team. That means you are engaging (meaningful connections) with your team and with the customer. You don't do that by working in a silo in a world in which nobody can communicate with you. Better to concentrate on delivering value. Learning to write incomprehensible code is not the answer to impostor syndrome. You are immersing yourself in one rabbit hole when you should be putting time into better understanding your impostor syndrome (your emotions). That rabbit hole is a fear response and an attempt to gain a sense of control over your environment. Instead, you should be doing the opposite, embracing uncertainty and the impostor syndrome. And love your team. Code so that everyone can join in. Even if you feel the tools which allow this are inferior.