Maybe it's just me but there seems to be a rise in the developer community surrounding impostor syndrome.
This feeling seems to affect the full ra...
For further actions, you may consider blocking this person and/or reporting abuse
I loved reading through this. Lots of interesting points to argue about. In general, indeed I think the "imposter syndrome" is no stranger to a lot of us these days, especially people working in something I'd consider "creative professions". However, there is one thing in here:
This has two implications. First off, indeed it leaves a load of us feeling like imposters while most of the time, like sleepwalkers, dancing on a thin wire right above an immensely deep ocean of complexity in which we would immediately drown. It's difficult to be in this situation from a personal point of view. But it's also difficult from an enterprise and quality point of view: What will happen if you end up continuously building software just like that? You end up with software built out of third-party bricks, in most cases glued together by people who have just a very vague idea of what pieces they are using, how they work and what they do. This is a nightmare in terms of virtually every non-functional requirement you possibly could imagine (reliability, stability, quality, ...). And this is the point where, then and now, I recommend people to, at least a bit, take that "imposter syndrome" seriously - and not by accepting that it is there but by trying to get rid of it, by trying do actually do dive into that complexity, trying to understand how most of the tools work and eventually trying to get rid of things they don't feel reasonably safe using. This will of course slow you down a bit, but it will reduce imposter syndrome and improve overall software quality, which definitely seems a win-win to me. ;)
Thank you.