HEY! LISTEN TO THE END, IT WILL MAKE A TON OF SENSE. I am sorry for the alerts. It was on the opening to my stream and i just felt inspired. The opening of the stream i just let them fly because its fun (its where 80% of them happen). So sorry, but i mean this from the bottom of my heart. please don't have imposter syndrome and i do think what i am saying, if you listen to the end, will help you.
Pro tip, if this is pulled from the stream vod then ignore the rest of this comment, otherwise, if you can try recording while you stream and put alerts on a separate audio track
You're the senior dev and mentor everyone could benefit from, and the fact you're able to broadcast your wisdom and advice is amazing. I can't say it enough, thank you for uploading these to the RUclipsz
Honestly, I haven’t even tried to find a mentor, because of content creators like this and knowing how to research things on my own. I REALLY enjoy the research part. I’m not studying to be a programmer, I’m studying to become a hacker, but there’s a lot of overlap. I need to have knowledge that’s an inch deep and a mile wide, though I’m striving for at least a foot deep 😂 I’ve been having trouble in some of my hacking classes, so I took a step back to study a little bit of programming and scripting.
Real Talk. I have been able to be a part of so many amazing things in my carrier because of the "Can Do" attitude. I don't know everything, but I am confident in my ability to learn what needs to be known to do the task that is placed before me. That has served me so well professionally. "Big K can you do this?" "I've never done it before, let me figure it out. I will tell you in an hour what I think it will take." The boss loves that.
You have two takes to deal with the syndrome: 1). You can feel sad because there’s much to learn, much you don’t know. This is a let down for you. 2). Avoid comparison with others, get excited for new things to learn, and as prime said, build stuff. Just be curious, try different techniques, stacks.
Dunning-Krueger is the secret to programming. Until lately, I have been always dismissing "hard" ideas when I want to create a side project. Trying to come up with something in my "level", which deemed impossible, because simple ideas are boring, and boring ideas will make programming not fun.
Key points: - Continually expand your skills and knowledge through exploring new technologies (both in and outside of work). - Reviewing basic data structures. - Practice building greenfield projects. - Try, even if they fail, as it's better than not trying at all.
I have made my career off of being able to translate my "hobby" programming explorations to innovative solutions within my field. You are 100% right about the value of "side-projects". And the beauty of R&D is that failure is often more informative than success... at least initially 😉
dude i dont know why talks from this guy motivates me to become me better engineer and actually kinda reminds why do i like this stuff and why did i started it in the first place... thanyou primeagen!
I moved from Support into a Junior Dev role. It was me and two senior devs. After three years in I quit purely because I didn't think I was good enough. I've been back in the field for years, and in hindsight I was crushing it and could have easily been given a raise had I asked instead of quitting. Please learn from my mistake, if you're in your first few years of dev just focus on being better than you were yesterday by working on problems that push you. If you do that you are already ahead of 99% of people and will soon shed any remaining imposter syndrome.
I just recently got out of Impostor Syndorme after left my full time Java/C# developer job and spend the last year and a half working the bare minimum I needed as a freelancer while spending most of my time learning as much stuff as possibile and building a lot of useless side projects. Now not only I feel confindent... I also enjoy building software and learning about new techs like nothing else I do. (and hopefully this will lead me to much better paying jobs in the future)
Absolute stack of good things in this video. I'm also in one of these situations right now. Shoehorning localisation into the heart of a complex old system with every gotcha in the book being thrown at me. Client has given me 1/5th of the time needed to do it in. Every other team member says "hell no, not me". The kind of change that once you start, you have to write an enormous of amount of code and change almost every part of the system before it will even run again. Having used all the tech stack in an ideal environment, often in my own time "greenfield" style, is my saving grace.
Oh man. I18n and l10n are sooooo terrible to bolt on after the fact. It's like a death from 10,000,000 paper cuts. It's so much easier just to require it from the outset, and once you have the support libraries built out it doesn't really slow you down either.
@@bobbycrosby9765 Amen to that. I think this change is probably going to hit ~80% server side code/classes and every component and service. It's all the knock on things. Testing. QA. Even the code review is going to be mega ...
The problem with this advice is it's supposed to be a job, something you do for X hours per day, so you can afford to switch off and do other things in the other hours. The idea that you should be effectively working 24/7 just to keep your job is so bad. Most of us enjoy exploring this area in our own time, but we shouldn't let companies take advantage of that or demand it as a minimum.
Great advice about greenfield projects. Before I try to incorporate new technology into existing codebase, I almost always have to try it on a side/empty/new project. That way I can get a feel of how it works, and less chance of something going wrong and bringing things down. It's also much easier to learn on a new project than an existing project that may have many layers to it already.
I’m not studying to be a programmer, I’m studying to become an ethical hacker, but I find your videos extremely relevant, interesting and also pretty hilarious. I need to learn a little bit of programming to be able to hack, so there’s a lot of overlap here.
One of the thing i do personally is fail. Badly building something which is quite complex at the beginning but as soon as i start, i get to solution to some problems and some i don't but everytime there is a new thing i learn!
1:55 just experiencing this right now as a new dev lmao. I just got on board onto a big project, and I was given a pretty simple task. I thought I could do it within an hour or so, but holy fuck man it took me quite a while because I had to do some codebase acrobatics so that I won't break anything
Год назад+5
Great advice from The Prime, but one thing about impostor syndrome: it's probably a mental problem. So, if you suffer a lot from it, just go to a psychiatric doctor to get yourself properly treated. If you EVENTUALLY suffer from it for a specific thing happening in your life, it is normal. For example, you may think you're a good developer, but then you enter Twitter or Twitch and see people like Theo or The Prime (who works at Netflix, by the way) doing awesome stuff with Typescript and Rust, working at huge companies. You may be working on a small project, and suddenly the impostor syndrome comes in, and you feel like shit. It happens, and it's normal. What is NOT normal: When you're a great husband, and even if your kids or wife say that you're awesome, you just don't believe it. When you deliver an extremely complex project that has millions of dollars in returns to the company, and even after that, you feel like you should have done better, and what you have done wasn't enough. When no matter what you do, nothing fulfills your feeling of accomplishment. If you feel like that, GO TO A DOCTOR. It happened to me, and I'm working on it. It's not as easy as it looks for some people.
it's not, fuck off. it's a highly solvable issue and saying people can't solve it on their own just adds to the impostor syndrome of everyone who believes that
I've been unemployed since I left university (1 year, the job search is a total shit show) but I have not stopped diving deep into topics that interest me. The main things are Distributed Systems, Networking with a RPI 4 cluster. At this point I'll just launch my own startup since I can't seem to land a job.
I thought about it a lot, and my conclusion is: it's hard to gain confidence in your skills based on easy things, when hard skills/things become easy when you master them. You just need to reconsider what your co-workers see in you as valuable asset during dev and problem solving - and put those into your own list of valuable skills, even if these feels like not worthy of it.
The Dunning-Kruger thing is a magma temperature take. If you're on the Dunning-Kruger peak, then by definition you're arrogant, and that, to most people, especially in a professional setting is completely unacceptable. Whereas the behavior of someone with imposter syndrome is. I understand the former might be better for your personal growth, but definitely not in terms of how you're perceived by your peers and superiors, which could really hurt your career.
Agree. Easier to just be real. Scratch the Imposter, Scratch the Newb, Scratch the Guru. You can fall into a trap of Dunning-Kreuger one way or Imposter the other way. No one can possibly know you. Whatever criticism you get, a simple "they don't know me" works. Whatever expectations you get, modestly summarize: "I only just read that." Reputation kinda does matter in the workplace. It's always being checked and foolish to ignore which is why people get Imposter Syndrome. If you level, they stop checking. Let the work do the wow'ing. And yes, while it's a balance, erring a little Dunning Krueger for habitual imposters gets them more challenges.
Coding itself is fun but I quit learning because web dev was frustrating. Do you think trying again with Rust and backend only or maybe Leptos would be a good idea?
try again with web dev. build resilience. do difficult shit intentionally and struggle your ass off. this is the ONLY way. otherwise the same thing will happen with Rust.
100% disagree about being on the Dunning Kruger side. There is nothing more annoying than dealing with a co-worker who confidently spouts bullshit 24/7 like it's received wisdom from On High. If I wanted that, I would work in car sales.
Thanks Prime, now I think I am schizophreniac. I am a "Can do" person WITH constant impostor syndrome. On good days I pleasantly surprise myself, on bad ones I say "they made a mistake thinking I of all people could pull this off"
@@BusinessWolf1 That is so true. I always mean to start a work diary for the sake of tracking progress over time and what I thought about it at the time. If I am in a good mood, I can see how much I both contributed to the project and also improved myself over time working, but on a daily basis, if you don't even get a bite to speak in your metaphor, that can sometimes be hard to spot.
I get imposter syndrome intermittently. It’s even more so now with all this AI tools. I feel like I’m regressing out on things if I don’t work new tools every chance I get.
Hi Mr. Primeagen. Switching company for the first time and the imposter syndrome is really kicking in hard. I'm going to work on a high spike, realtime system and don't know if I have what it takes to succeed, let alone contribute there. Any advice for new onboarding?
That is called discrete math, it's a lot of proofs and stuff, just do a language based one. You can simply take any concept and move it to another language
hate to be a negative nancy but it does worry me that it is in some sense required either directly or passively that you have to be a workaholic as a programmer to stay relevant. feels like if that is a real world expectation then the employers should be paying for that learning process. because otherwise that is juse devaluing your work value cuz that training is work you are not getting payed for. and im sorry but i view workaholism to be unhealthy so if this is the case we as a worker class are letting an unhealthy work environment be imposed on us.
Prime has never worked mission critical - one time events. SW development usually has the privilege of create/destroy without consequence. Sometimes it Matters.
When I was working at an agency, they asked me to do backend for a small feature for a client. I said "No, I just want to focus on my front end skills and be as better as I can in that field", after that I got called all to the time to help other team members when they got stuck with CSS or Javascript, and also I had to lead a few projects that where mainly front end. So this is what confuses me, should I learn a new tech even if it doesn't have too much to do with the roles I want in the future or should I focus 100% on front end and learn as much as I can?
That's not true at all. The impostor syndrome is actually good for you. Because you'll be too embarrassed to ask questions so you'll actually do your homework and read the manual. If you're overconfident, you'll just be lazy and never learn anything
Unpopular opinion: the vast majority of people who believe they experience this "impostor syndrome" are impostors indeed, and they're right to feel inadequate. Painting it as an "impostor syndrome" is their coping, nothing else.
It’s also a cope for those of us that are decent at coding but get by on other skills such as logical reasoning and teamwork to say we can trust in our DK to fake it til we make it. But activity is key, that’s for sure.
In my experience devs tend to undervalue themselves rather than overvalue themselves. The worst devs I met where the once who confindently presented themselves as if they never experienced imposter syndrome. As socrates said "all I know is that I know nothing." The best devs I know are also the devs that are the most aware of how little they actually know
@@samuelmorkbednarzkepler a healthy understanding of your limits of knowledge do not result in doubt and fear of inadequacy. Any decent engineer or scientist knows to routinely check their biases and limitations. It is those who lack systematic knowledge and rigourous training in scientific method who experience "impostor syndrome", and more often than not quite rightfully so.
Real talk: if you have imposter syndrome, you probably are kinda of an impostor. You should try to learn and improve your programming knowledge and skills.
whats the opposite of imposter syndrome? where we've done this shit for years and are as good as developers as the leads, but dont have that magical x-many years on a resume, so we're highly underpaid and under utilized, whats that called
HEY! LISTEN TO THE END, IT WILL MAKE A TON OF SENSE.
I am sorry for the alerts. It was on the opening to my stream and i just felt inspired. The opening of the stream i just let them fly because its fun (its where 80% of them happen). So sorry, but i mean this from the bottom of my heart. please don't have imposter syndrome and i do think what i am saying, if you listen to the end, will help you.
also first
@@ThePrimeTimeagen Now you did, I won't be able to do so :(
Pro tip, if this is pulled from the stream vod then ignore the rest of this comment, otherwise, if you can try recording while you stream and put alerts on a separate audio track
how to handle imposter syndrome while being rejected in interviews, even when you think you done well in them?
Just dont have impostor syndrome 4head, finally the answer!
You're the senior dev and mentor everyone could benefit from, and the fact you're able to broadcast your wisdom and advice is amazing. I can't say it enough, thank you for uploading these to the RUclipsz
Honestly, I haven’t even tried to find a mentor, because of content creators like this and knowing how to research things on my own. I REALLY enjoy the research part. I’m not studying to be a programmer, I’m studying to become a hacker, but there’s a lot of overlap. I need to have knowledge that’s an inch deep and a mile wide, though I’m striving for at least a foot deep 😂 I’ve been having trouble in some of my hacking classes, so I took a step back to study a little bit of programming and scripting.
Real Talk. I have been able to be a part of so many amazing things in my carrier because of the "Can Do" attitude. I don't know everything, but I am confident in my ability to learn what needs to be known to do the task that is placed before me. That has served me so well professionally. "Big K can you do this?" "I've never done it before, let me figure it out. I will tell you in an hour what I think it will take." The boss loves that.
"It is so much better failing, than to never try"
100% jive with this mentality, keep on preaching!
:horse_handshake:
You have two takes to deal with the syndrome:
1). You can feel sad because there’s much to learn, much you don’t know. This is a let down for you.
2). Avoid comparison with others, get excited for new things to learn, and as prime said, build stuff.
Just be curious, try different techniques, stacks.
Dunning-Krueger is the secret to programming. Until lately, I have been always dismissing "hard" ideas when I want to create a side project. Trying to come up with something in my "level", which deemed impossible, because simple ideas are boring, and boring ideas will make programming not fun.
Key points:
- Continually expand your skills and knowledge through exploring new technologies (both in and outside of work).
- Reviewing basic data structures.
- Practice building greenfield projects.
- Try, even if they fail, as it's better than not trying at all.
My secret? I suffer from Dunning-Krueger Effect, and can read.
And you can read?… a double threat
Stop killing me 😊
Or you think you can read... 😏
@@T1Oracle You've gotta believe me I can read
Best comment
I have made my career off of being able to translate my "hobby" programming explorations to innovative solutions within my field. You are 100% right about the value of "side-projects". And the beauty of R&D is that failure is often more informative than success... at least initially 😉
dude i dont know why talks from this guy motivates me to become me better engineer and actually kinda reminds why do i like this stuff and why did i started it in the first place...
thanyou primeagen!
I moved from Support into a Junior Dev role. It was me and two senior devs. After three years in I quit purely because I didn't think I was good enough. I've been back in the field for years, and in hindsight I was crushing it and could have easily been given a raise had I asked instead of quitting. Please learn from my mistake, if you're in your first few years of dev just focus on being better than you were yesterday by working on problems that push you. If you do that you are already ahead of 99% of people and will soon shed any remaining imposter syndrome.
I just recently got out of Impostor Syndorme after left my full time Java/C# developer job and spend the last year and a half working the bare minimum I needed as a freelancer while spending most of my time learning as much stuff as possibile and building a lot of useless side projects.
Now not only I feel confindent... I also enjoy building software and learning about new techs like nothing else I do.
(and hopefully this will lead me to much better paying jobs in the future)
5:17 -> 6:07. Now that was just gold! Good stuff here.
Message received. I work at Costco now.
Absolute stack of good things in this video.
I'm also in one of these situations right now. Shoehorning localisation into the heart of a complex old system with every gotcha in the book being thrown at me. Client has given me 1/5th of the time needed to do it in. Every other team member says "hell no, not me". The kind of change that once you start, you have to write an enormous of amount of code and change almost every part of the system before it will even run again.
Having used all the tech stack in an ideal environment, often in my own time "greenfield" style, is my saving grace.
lets go! also sorry you got such the responsibility on your shoulders
Oh man. I18n and l10n are sooooo terrible to bolt on after the fact. It's like a death from 10,000,000 paper cuts. It's so much easier just to require it from the outset, and once you have the support libraries built out it doesn't really slow you down either.
@@ThePrimeTimeagen It's all good. I like the challenge.
@@bobbycrosby9765 Amen to that.
I think this change is probably going to hit ~80% server side code/classes and every component and service.
It's all the knock on things. Testing. QA. Even the code review is going to be mega ...
The problem with this advice is it's supposed to be a job, something you do for X hours per day, so you can afford to switch off and do other things in the other hours. The idea that you should be effectively working 24/7 just to keep your job is so bad. Most of us enjoy exploring this area in our own time, but we shouldn't let companies take advantage of that or demand it as a minimum.
Yeah Prime is a bit of a workaholic. Personally I'm investing enough so I don't have to code for money forever
Great advice about greenfield projects. Before I try to incorporate new technology into existing codebase, I almost always have to try it on a side/empty/new project. That way I can get a feel of how it works, and less chance of something going wrong and bringing things down. It's also much easier to learn on a new project than an existing project that may have many layers to it already.
I’ve been doing that as well. Feels a lot safer to chop up the code and recompose it.
I’m not studying to be a programmer, I’m studying to become an ethical hacker, but I find your videos extremely relevant, interesting and also pretty hilarious. I need to learn a little bit of programming to be able to hack, so there’s a lot of overlap here.
Definitely have imposter syndrome, but the goal moving forward is to put in more effort to earn feeling confident
One of the thing i do personally is fail. Badly building something which is quite complex at the beginning but as soon as i start, i get to solution to some problems and some i don't but everytime there is a new thing i learn!
So basically, leveraging the forgetting curve on commonly used data structures...
Good point about greenfield projects. Sage advice.
I've seen 0 videos on this channel where prime didn't forget to turn off his notifications
shhh
@ThePrimeTime it's an important indicator for the viewers to know on which channel they are watching, great QoL feature
damn, you gotta love this guy, thanks for the content
straight facts. watching your vids & streams recently just made writing code fun again, haven't felt like that in a minute
1:55 just experiencing this right now as a new dev lmao. I just got on board onto a big project, and I was given a pretty simple task. I thought I could do it within an hour or so, but holy fuck man it took me quite a while because I had to do some codebase acrobatics so that I won't break anything
Great advice from The Prime, but one thing about impostor syndrome: it's probably a mental problem. So, if you suffer a lot from it, just go to a psychiatric doctor to get yourself properly treated.
If you EVENTUALLY suffer from it for a specific thing happening in your life, it is normal. For example, you may think you're a good developer, but then you enter Twitter or Twitch and see people like Theo or The Prime (who works at Netflix, by the way) doing awesome stuff with Typescript and Rust, working at huge companies. You may be working on a small project, and suddenly the impostor syndrome comes in, and you feel like shit. It happens, and it's normal.
What is NOT normal:
When you're a great husband, and even if your kids or wife say that you're awesome, you just don't believe it.
When you deliver an extremely complex project that has millions of dollars in returns to the company, and even after that, you feel like you should have done better, and what you have done wasn't enough.
When no matter what you do, nothing fulfills your feeling of accomplishment.
If you feel like that, GO TO A DOCTOR.
It happened to me, and I'm working on it. It's not as easy as it looks for some people.
it's not, fuck off. it's a highly solvable issue and saying people can't solve it on their own just adds to the impostor syndrome of everyone who believes that
Great advice too! Thanks man!
I've been unemployed since I left university (1 year, the job search is a total shit show) but I have not stopped diving deep into topics that interest me. The main things are Distributed Systems, Networking with a RPI 4 cluster. At this point I'll just launch my own startup since I can't seem to land a job.
Which country are you in?
It’s been a year and a half for me here. My country is at war and I can’t work where I’m currently staying lol
I thought about it a lot, and my conclusion is: it's hard to gain confidence in your skills based on easy things, when hard skills/things become easy when you master them.
You just need to reconsider what your co-workers see in you as valuable asset during dev and problem solving - and put those into your own list of valuable skills, even if these feels like not worthy of it.
I love you, Prime
As soon as this video fired up, I knew someone was going to trigger the gunshot
Interessant, never thought about it like that "duning kruger is better than imposter syndrom". But it makes a ton of sense
The Dunning-Kruger thing is a magma temperature take. If you're on the Dunning-Kruger peak, then by definition you're arrogant, and that, to most people, especially in a professional setting is completely unacceptable. Whereas the behavior of someone with imposter syndrome is. I understand the former might be better for your personal growth, but definitely not in terms of how you're perceived by your peers and superiors, which could really hurt your career.
Life lessons everyone should take to heart
Greenfield projects will connect the dots! 10000%
Agree. Easier to just be real. Scratch the Imposter, Scratch the Newb, Scratch the Guru. You can fall into a trap of Dunning-Kreuger one way or Imposter the other way. No one can possibly know you. Whatever criticism you get, a simple "they don't know me" works. Whatever expectations you get, modestly summarize: "I only just read that." Reputation kinda does matter in the workplace. It's always being checked and foolish to ignore which is why people get Imposter Syndrome. If you level, they stop checking. Let the work do the wow'ing. And yes, while it's a balance, erring a little Dunning Krueger for habitual imposters gets them more challenges.
I don't have imposter syndrome I'm just incompetent
Interesting bit I could not listen to the end. I said to myself that one more "welcome to costco" and I'm done, so I was
i struggle with imposter syndrome , and my company has been incentivising my effort generously . therefore, sometime i do sense guilt
Ive turned down big jumps to move companies because of imposter syndrome
DR of technology. I love it!
Coding itself is fun but I quit learning because web dev was frustrating. Do you think trying again with Rust and backend only or maybe Leptos would be a good idea?
try again with web dev. build resilience. do difficult shit intentionally and struggle your ass off. this is the ONLY way. otherwise the same thing will happen with Rust.
@@BusinessWolf1 Stop watching hustle pron. Rust is very different from JavaScript.
100% disagree about being on the Dunning Kruger side. There is nothing more annoying than dealing with a co-worker who confidently spouts bullshit 24/7 like it's received wisdom from On High. If I wanted that, I would work in car sales.
"the dunning kruger side" lol i love it
Thanks Prime, now I think I am schizophreniac. I am a "Can do" person WITH constant impostor syndrome. On good days I pleasantly surprise myself, on bad ones I say "they made a mistake thinking I of all people could pull this off"
we should look at programming like fishing. On some days you just don't catch ANYTHING.
@@BusinessWolf1 That is so true. I always mean to start a work diary for the sake of tracking progress over time and what I thought about it at the time. If I am in a good mood, I can see how much I both contributed to the project and also improved myself over time working, but on a daily basis, if you don't even get a bite to speak in your metaphor, that can sometimes be hard to spot.
doing anything are painful
I get imposter syndrome intermittently. It’s even more so now with all this AI tools. I feel like I’m regressing out on things if I don’t work new tools every chance I get.
Hi Mr. Primeagen. Switching company for the first time and the imposter syndrome is really kicking in hard. I'm going to work on a high spike, realtime system and don't know if I have what it takes to succeed, let alone contribute there.
Any advice for new onboarding?
Ask every question that comes to mind. Don't think appearing to know the answer already is better than asking it ...
Remember that "I don't know, I'll find out" IS an answer ...
@@Prod-23 Thanks for the advice
what it takes to succeed is the ability to learn and nothing else
amazing advice!!!!
Impostor syndrome is such an American thing. You never hear it in other countries. We just call it whining or drowning in a glass of water.
Just don't be the guy who gets rewarded for your hard work with more work. Move jobs every few years or do your own startup
Can you recomend a good datastructure training, language agnostic?
That is called discrete math, it's a lot of proofs and stuff, just do a language based one. You can simply take any concept and move it to another language
If you’ve been a working programmer for five years, any skills that are atrophy, you don’t need
the moment you think you have imposter syndrome you stop having imposter syndrome
you start having dunning-krueger effect
dunning-krueger effect being that you really think you're not an actual imposter and it's just a syndrome
but the moment you think you have dunning-krueger effect you start having imposter syndrome (until you think you have imposter syndrome)
hate to be a negative nancy but it does worry me that it is in some sense required either directly or passively that you have to be a workaholic as a programmer to stay relevant. feels like if that is a real world expectation then the employers should be paying for that learning process. because otherwise that is juse devaluing your work value cuz that training is work you are not getting payed for. and im sorry but i view workaholism to be unhealthy so if this is the case we as a worker class are letting an unhealthy work environment be imposed on us.
Blazingly Fast !!!! B)
Welcome to costco, i love you.
Hehe what does it mean?
Just work 24 hours a day guys. That's totally realistic.
Prime has never worked mission critical - one time events.
SW development usually has the privilege of create/destroy without consequence.
Sometimes it Matters.
umm... i didn't realize you knew my career so well, yet some how is completely wrong.
thank you though for the comment
@@ThePrimeTimeagen You left Netflix. Now it sucks.
Lol, so you are basically ignoring his advice on GREENFIELD PROJECTS, which essentially tells the opposite of what you are claiming.
What's green field?
New project without any legacy code, so you can make all the decisions how you wanna implement it
i love you
This could have been a good video but it was impossible to focus with all the alerts going off.
Why is SWE in the title? He's swedish? Swedes are good at imposter symdrom?
When I was working at an agency, they asked me to do backend for a small feature for a client. I said "No, I just want to focus on my front end skills and be as better as I can in that field", after that I got called all to the time to help other team members when they got stuck with CSS or Javascript, and also I had to lead a few projects that where mainly front end.
So this is what confuses me, should I learn a new tech even if it doesn't have too much to do with the roles I want in the future or should I focus 100% on front end and learn as much as I can?
That's not true at all. The impostor syndrome is actually good for you. Because you'll be too embarrassed to ask questions so you'll actually do your homework and read the manual. If you're overconfident, you'll just be lazy and never learn anything
So shiny object syndrome is the secret to defeating impostor syndrome.
Unpopular opinion: the vast majority of people who believe they experience this "impostor syndrome" are impostors indeed, and they're right to feel inadequate. Painting it as an "impostor syndrome" is their coping, nothing else.
It’s also a cope for those of us that are decent at coding but get by on other skills such as logical reasoning and teamwork to say we can trust in our DK to fake it til we make it. But activity is key, that’s for sure.
Found the guy on the DK side.
In my experience devs tend to undervalue themselves rather than overvalue themselves. The worst devs I met where the once who confindently presented themselves as if they never experienced imposter syndrome. As socrates said "all I know is that I know nothing." The best devs I know are also the devs that are the most aware of how little they actually know
@@ChillAutos keep coping, this is all you have
@@samuelmorkbednarzkepler a healthy understanding of your limits of knowledge do not result in doubt and fear of inadequacy. Any decent engineer or scientist knows to routinely check their biases and limitations.
It is those who lack systematic knowledge and rigourous training in scientific method who experience "impostor syndrome", and more often than not quite rightfully so.
Real talk: if you have imposter syndrome, you probably are kinda of an impostor. You should try to learn and improve your programming knowledge and skills.
got goosebumps at the end @theprimetime
whats the opposite of imposter syndrome? where we've done this shit for years and are as good as developers as the leads, but dont have that magical x-many years on a resume, so we're highly underpaid and under utilized, whats that called