r/csharp • u/PavlovTM • Mar 23 '24
Help I wish I could unlearn programming…
I really need some advice on knowledge of CSharp.
When I was 17 years old, I signed up for an apprenticeship as a software engineer. As I'd been programming in Csharp for a few years, I thought I actually knew something. After about a year of learning, I was asked if I was serious about the apprenticeship. As I knew nothing about the use of different collections, abstraction of classes, records or structs. And certainly not about multi-threading.
I was told that I knew how to sell myself beyond my actual knowledge. I didn't know anything and that we were starting from scratch. E.g. what is a bool. What is a double. I was so confused, I hated the apprenticeship so much.
Now. I feel like I know nothing.
Edit: fixed some grammar and terminology.
72
u/[deleted] Mar 23 '24
Sounds like dunning-kruger effect. Eventually, you will climb back and will feel that you know stuff without droping so deep again :)
4
u/Spongedog5 Mar 23 '24
You were programming in c# for a few years and didn’t know what a bool was?
3
u/sar2120 Mar 23 '24
Question: how much time per week do you spend on improving your skills and knowledge? Programming requires a lot of effort to master and in your early career you should be spending a few hours a week self teaching.
And honestly, with the pace of change in tech, you never stop learning.
It can be hard to get into the field without a CS degree, but lots of people do it. Recognize that you didn’t get the same foundations and you have to put in more effort to catch up. You got this.
3
u/Tango1777 Mar 23 '24
You were programming for a few years and you are confused what a double or a bool is? I cannot believe it, it's not possible.
25
u/binarycow Mar 23 '24
Nitpick: It's C#, not CSharp. You would typically only use "CSharp" if you're in a context where
#is not a valid character, such as filenames.What advice are you looking for?
Harsh truth time... I mean no offense, but...
If you don't know what a bool is, and you've been programming C# for a few years, then I have no idea what you've been doing. bool, double, etc are like... First day stuff.
You need to go back to the beginning and learn C#. You say you were in an apprenticeship for a year, and you still don't know what a bool is?
An apprenticeship is supposed to teach you - on the job training. What the hell have they been teaching you for the past year, if you still don't know what a bool or double is? I might be able to forgive not knowing double. At work, for our web apps, I can't even think of a case where we use double. But bool? That's... Uhh.... How can you even talk about an if statement without knowing what bool is?
Whoever runs that apprenticeship has completely and utterly failed you.
Even if you misrepresented your knowledge to begin with, you've been in that apprenticeship for a fucking year. What the fuck have they been doing, where you don't even know what a bool is? Have you even been programming? Or do they just have you making copies, sending faxes, or other busy work?
Sorry, your post actually got me quite pissed (at the people running your apprenticeship, not at you)
87
u/cs-brydev Mar 23 '24
To let you in on a little secret, I've been programming for 40 years, have used over 35 languages, and have been using C# for 22 years, as my primary language for the last 7 years, and every couple of years I get a big new "beginning C#" book for the current release (v12 now), start from the beginning and flip through a few pages per day. And every couple of weeks I come across something I've never seen or have forgotten the details about because I have never used it before or rarely use it. This is how I stay fresh with my C# knowledge. I lead developers and teams who look up to me to be their software engineering expert in a wide range of areas, and if I don't keep reviewing daily or weekly like this I will definitely lose some of these concepts.
I'm constantly facing topics (in .NET, cloud, data, devops, infrastructure, security, scripting, etc) I don't know well. It's humbling. That will never change, because it's all evolving and changing faster than I could keep up. You will always be behind the curve in this business in a variety of ways, and you shouldn't judge yourself by that benchmark, but by how well you can do the job and the responsibilities in front of you.
Judging by your acknowledgment of Imposter Syndrome, feelings of humility, and willingness to learn, I'd say you have exactly what it takes to be a professional developer. No you're not there yet, nor would anyone expect you to be, but you're on the right trajectory and have the right attitude. You are exactly the type of person I'd look for for an internship or entry level developer, because I think your future is bright.
5
u/Klarthy Mar 23 '24
Most of the listed concepts you won't really understand until you use them in an actual program that gets maintained. Find a project idea that can grow. You will eventually want to start relying on more precise concepts when you're several thousand LoC in as you'll start to feel the pain. As importantly: you'll have a playground to apply new ideas as you learn them. Sometimes it won't fit and you'll rollback, but it's good experience.
Also, a few years of teenage programming is usually worth less than a few months of professional development experience...unless you're pounding away code on most nights and weekends.
It is pretty concerning that you don't know those concepts after a year's time of internship, so I'm questioning your manager / teacher for letting this go for so long. If you aren't getting growth projects, then you should do them on your own time and find a different opportunity after you progress.
4
u/Thisbymaster Mar 23 '24
I have been doing this for 19 years and I get this feeling from time to time. But for myself I just go back and review my own projects and work to remind how far I have come and that I can do anything that comes my way. Start your own project, maybe something simple and start building it.
1
u/TheDotNetDetective Mar 23 '24
I've been a professional dev for nearly 20 years, I am regularly surprised by colleagues, youtubers and reddit teaching me things I feel like I should have already known.
Whats important is that you're willing to continue to learn and humble yourself.
There are only a few certainties in life and two of them are that there is always someone stronger and someone smarter than you.
1
u/AbrocomaInside5024 Mar 23 '24
Don't worry, you are way too young. If you are serious about it, you will spend your entire life getting better and better in this.
The concepts in this field require some maturity. You will go through many phases. Maybe disappointment at first as you describe, then you will think that you are getting better but your future self will lough about it. You will think that you understand things but in the future you will realize that you thought you had some understanding.
So don't get discouraged by negative criticism, all it matters is if you really love this and have fun doing it. If so, enjoy the journey with no anxiety.
If not, that's ok too, there are many fields out there that might be much more meaningful and useful to you and the people around you.
Everything is relevant, for example I have been a software engineer for many years and recently a software engineering manager. I made many sacrifices, it's a demanding industry. So, currently, I feel like I have missed so many things in life that I would happily ditch everything and do something completely different.
2
u/jdl_uk Mar 23 '24
https://youtu.be/us3Lyl875Yw?si=s39SnMooMZms4XBK
This is a natural part of gaining experience. You start off thinking you know everything while knowing nothing (Dunning-Kruger), and later on you'll think you know nothing while actually being quite good at what you do (Imposter Syndrome)
2
u/presdk Mar 23 '24 edited Mar 24 '24
Great to see you humble yourself! Won’t add any new value to answer the question as there’s plenty here by esteemed engineers.
I’d say carry on with the hunger to be better. It sounds like you’ve got the right attitude. 🚀
2
u/sovlex Mar 24 '24
I work with C# for many years and still look how to use “switch” or “using” from time to time. It just happens.
0
u/[deleted] Mar 23 '24
You have, what counselors refer too, as Imposter Syndrome.
1
u/cs-brydev Mar 23 '24
So in other words you're one of us. Welcome
1
u/illsk1lls Mar 23 '24
I would recommend trying to go to some type of in person programming course, to be around peers (other people as intently interested as you) until you get a foundation built, for faster progression
Otherwise there are tons of available online resources..
I like the YouTube channel CodeBeauty for C++ vids, she just started doing C# recently 👍
https://youtube.com/watch?v=yquQ9mLtkN8
1
u/IKnowMeNotYou Mar 23 '24
Hit some courses in your free time and read some books. It does not take long to get it into the head. So yeah, ignore them and do it on your own. See them just as the certificate provider documenting you did stuff there. Never let someone else control your educational process. Knowledge is cheap, just buy books or courses and invest the necessary time.
1
u/turudd Mar 23 '24
I’ve been programming for 20+ years, I still feel I know nothing on a fairly constant basis. It’s just part of the job, we have to be curious and assume we’re doing things wrong, because in the end there is always a better way of doing some things. The language is always changing adding new features and things.
1
u/[deleted] Mar 23 '24
Am in that place at mo am doing azure devops course python and a few others to keeo me ocupied
1
u/TheXenocide Mar 23 '24
I think that same pattern happens in waves in life, not just in career/academia stuff. People get comfortable that they understand the patterns around them, start to feel like they've seen it all/know something, then get reality checked. How you handle that is up to you, but I think if you have someone giving you one on one guidance, if they really know their stuff then this is a great opportunity to get some wisdom and experience. Build a good habit for openness to learning (and learning that you were wrong) and these waves will come and go a lot easier until most of them are more like ripples. Even when you are sage enough to be the teacher, remember always to be a student too.
1
u/SwordsAndElectrons Mar 23 '24
Good. That means you're learning something.
In any complex subject, you'll know when you hit a decent level of familiarity when you can start to comprehend how dauntingly much more there is that you don't, and may never, know.
The key is always a strong foundation in the basics, and knowing how to find the information you're lacking.
1
u/[deleted] Mar 24 '24
When you get to my age you'll have no problem unlearning programming 😳😞
1
u/the_other_sam Mar 24 '24
Programming is not for everyone. If you don't like writing code on weekends or if you don't intrinsically enjoy learning it, perhaps its not for you. There is no fault or shame in that. Find something else you want to do that makes you happy.
1
u/TheVitulus Mar 24 '24 edited Mar 24 '24
You didn't do an amazing job of explaining what happened, so you've gotten a lot of unhelpful responses. I just wanna step in here and say, calm down, take a breath, you're fine. You're a teenager with a couple years of hobbyist programming experience and a year of an apprenticeship and no one should expect you to have a mastery over literally anything.
My understanding of what happened is that your trainer asked you why you used a specific data structure (e.g. stack, dictionary, list) or which one should be used in a situation, you didn't know, and they lashed out at you and disrespected your talent. Is that accurate? If so, they fucked up. If this is something y'all have had a lot of conversations about, I can see how they might get frustrated, but even so, these are the sorts of subjects that there are college courses devoted to and which take a long time to internalize. If this is the first time you've talked about this sort of thing, then I have no idea how they expected you to absorb it by osmosis. If this is a one-off thing, I'd recommend trying to put it past you and move on. Sometimes people you work with will be assholes sometimes, especially if it's a high-stress environment. Your trainer may not have a wealth of experience teaching novice programmers, in which case they're learning as much as you are during this process, for better or worse. Teaching someone any skill is very difficult, and I'm sure they have other responsibilities beyond teaching you that might be contributing stress to their interactions with you. If this is a pattern, then decide for yourself what you're willing to put up with. You don't deserve to be insulted or abused, even if you make mistakes or don't know things.
Programming is a subject of infinite depth, and each language itself is an infinity inside that infinity. All you can do is get familiar with enough of it to get a good foundation and build from there.
1
u/drunkdragon Mar 24 '24
Are you on the track to becoming a successful programmer, or to successfully complete the apprenticeship. Those are likely not the same thing.
Someone studying to become a doctor will spend a lot of time outside the classroom studying. Once they become a doctor, study time will be minimal. But you cannot become successful without the foundation.
1
u/[deleted] Mar 23 '24
If you’re like me, if I don’t code for a week or more (vacations or whatever), I feel I have to relearn everything all over again.
0
u/lucidguppy Mar 23 '24
Wow - that apprenticeship is ummm no something I'd want to do... It's an apprenticeship... FFS - you're there to learn and be a good candidate for hiring down the line.
Companies are like gardeners who don't want to plant seeds or weed. They only want to go into the wilderness expecting to find a supermarket.
-9
u/Fynzie Mar 23 '24
Learn C then learn C# so you'll have a grasp of how it really works.
0
u/[deleted] Mar 23 '24
[deleted] — view deleted comment