Under-promise and over-deliver.

Same. I am 20 years stuck with WinForms (and happy with it), but I'm almost a greenhorn in web development. Not that I need it, but I don't feel up-to-date.

Thanks for sharing!

@@holger_p I am too and I am learning web developer now .

realy struggling with #2. working for a small shop and man, those support issues really can eat into your dev time...

Thanks for sharing!

You are welcome.

This is actually a very inspiring thought. I remember thinking at some point, do developers really think they are not good programmers? Since beginning my programming journey as an eleven year old child, I did always think: I love programming, I think I am a good programmer, I want to learn more to create greater things. Of course I have been humbled a thousand times. I think these moments should inspire you to conquer whatever you're lacking.

Outstanding comment. Couldn't agree more!

Thanks for sharing!

Thanks for sharing!

same

It is important to keep up the skills that you want to use in a future position. I know it can be hard, though, when your current job doesn't allow you to use them.

But this should never result in the reverse effect "I'm not yet ready to be productive, I need to learn, learn learn". That's not so seldom. Sure you can go "too deep" it can cost you a week or a month, if you want to know too much. You become smarter, but also slower, and slower means inefficient.

You are welcome.

That's a learned skill - asking enough of the right questions.

I am glad it was helpful.

Thank you!

You are welcome.

That's exactly what I was thinking as he's explaining the bell curve. I think his explanation is from the perspective of the person where Dunning Kruger is from the perspective of the observer.

It is, but like @bbrazen said, people don't know when they are under its effects.

Thanks for sharing!

Yes, I have (and still do at times). I did a video on it and I'm probably due to do another one: kzfaq.info/get/bejne/mJp3rcWLzdCpYXU.html

I understand that. Unfortunately, selling a course isn't just about the initial sale. When I sell a course, I also support that sale. If the person has a problem with the purchase or they need a different receipt or any number of sales-related questions, I pay someone to handle it. I also pay my course host and others based upon the number of students I have. All of those costs are in USD. So if I were to do regional pricing, I would actually lose money per sale. Since the purpose of selling courses is to fund my free content, that would actually hurt how much I could provide for free to the community. So, the best thing I can do is not provide regional pricing. Instead, I keep the pricing at USD-equivalent so that I can continue to create more free content. That will allow you to get more training.

And that's why I said those were my biggest. I've also made plenty of them.

Thanks for sharing!

It sounds like you may have been burned by a bad situation. I don't think hiding your skill is a necessary thing. In fact, it has served me well to show my bosses what I can do even outside of software development.

@@IAmTimCorey Every job I have ever had. The fun bit is when carrying teams gets boring the managers are usually very upset when I leave because they know their days of successful projects and good bonuses are over. This is fundamentally a problem with having salary bands, it doesnt encourage people to work to their potential.

Thank you?!?

Bummer.

Email help@iamtimcorey.com for help.

@@IAmTimCorey sent you the email with different email ID. Please check sir.

I'm not sure what you are saying. Email help@iamtimcorey.com and someone will help you out as soon as they can. If you emailed somewhere else, we will not be able to help you.

@@IAmTimCorey Please verify I had purchased using this email only.

Not sure what you mean. Do you mean because they were all standing around looking for who was to blame? It wasn't because they wanted to punish someone. It was because the production system was down and they wanted to know who should fix it. I made it a blame game when I didn't just look at my code to see if I could diagnose and fix the issue.

@@IAmTimCorey I may have misunderstood what you where trying to say, but it sounded to me like it was more important who to blame than finding where the bug was hiding. In my experience it's almost never one persons fault alone when a bug slips into production, and IMHO playing the blame game only leads to an unhealthy work environment. And on second watch I see it was you doing the blaming and not so much management, I think I get your point now.

Andy, that is just not possible. Also, I gave you an assignment the last time you were saying this. Have you completed it yet? If not, you still have something to do.

Cool, looking forward to see you creating the next generation of a large language machine-learning model on a combination of neuromorphic hardware and quantum computing. :-)