SoylentNews is people
SoylentNews
Most people advance through their careers with legitimate training, and yet many professionals may still feel about as ill-qualified for their jobs as Demara was for his various "vocations."
Indeed, psychological scientists have explored the "impostor phenomenon," a term first coined in the 1970s to describe the intellectual and professional fraud that many high-achievers feel they're committing. Despite academic and career success, these individuals believe that others overestimate their abilities and will eventually discover their incompetence.
A team of Belgian psychological scientists recently set out to explore the impostor phenomenon (IP) more closely, and found that it correlated with specific personality, emotional, and behavioral traits. Professionals grappling with IP manifest high levels of maladaptive perfectionism and neuroticism, the researchers found. And those individuals tend to be relatively unhappy with their jobs.
(Score: 1, Interesting) by Anonymous Coward on Thursday November 05 2015, @03:54PM
I tend to learn the theories behind it. The language/framework is just the minutia. I know how to do X so that it is most efficient, and I know I will need tool Y, and language Z has A that serves as Y, or it doesn't have anything like it but it has B and C that can work as Y, just not as efficiently. You seen one MVC framework, you seen them all. Some lack certain things, others have few pointless additions, but overall it's all the same. When I have to use something particular I pick up the basics in few days and go from there. Luckily for me I have a lot of creative freedom. If I want to use something in particular I'll just tell Management that it is the best tool for the job (usually is), and working with web services you can pretty much add ton of different tech together and it will still work.
Scrapping everything and starting over? I want to scrap a bunch of legacy systems and redo them. Hopefully I'll get a chance. Older staff tends to not be engineered int he least, it just sorta works and they keep piling things on top of it without wrapping anything with abstraction into reusable and modifiable packages. Which is fine for a system as long as it works. But when new features are requested all the time and you find yourself spending exorbitant amount of time in frustration modifying things in 15 places instead of 1 you kinda have to say it's time to redo this POS.
I don't really need a facade (other than in Laravel :P ), they assume I am the best person to make sense of it in the room. And I have proven time and again even if I don't know something obscure I can master it and get it done in short order. I realize thou that being in a smaller company is probably the only reason I can operate like this. In a giant corp there would be probably 4 other guys in the room ready to stab me in the back if I said I need time to get started with X. So to each his own.