The Path to C# in 2024 

Thanks for sharing!

as a C# lead dev / manager: no, you will not, at least not on the us market and not in 2024.

Thanks for sharing!

Absolutely.

Yes. Completely agree. Back in the day, I had every book, magazine, and newsletter about FoxPro. I was so proud of my collection…it served me well. I am now navigating the .Net ecosystem with the same approach.

Practice, practice, practice! Build that braincell "muscle memory" I'm 62, been in programming since 1986, first 10 years just as fun for myself, since 1997 supported myself and my family with it and I learn new things every day! :) Just discovered Tim and he is a fantastic teacher! XAML finally clicked for me after watching his videos!

Fantastic!

Thanks for sharing!

You are welcome.

I'm glad my content has been helpful.

You are welcome.

Thank you! Will do!

You can do it!

@@IAmTimCorey thank you 🙌🏻 I agree 😅

Thanks!

I’m glad that my content has been so helpful.

You are welcome.

Thanks for sharing!

You are welcome.

You are welcome!

Glad you like them!

Happy new year!

Thanks for sharing!

Im glad it was helpful.

Great!

You are welcome.

Thanks!

Thanks!

I would add them in after you have learned C# itself (so after you have gone through the entire list for learning C# itself). Third party libraries are great, but which ones you will use will change. The underlying C# will not. As for SignalR, it is a wrapper for Web Sockets (and others). It is good to know later on for real-time web communication.

@@IAmTimCorey Thank you very much!

Thanks!

Following along and doing what the person does on the video can be really helpful for retaining the information. It can also be distracting. It all depends on how well you listen while you type. You can also pause and resume to help with that. However, that's not the only practicing you need to do. You need to build things on your own that use the topic you are learning, but in a different way than what you saw. Otherwise, you will just be copying what you saw, and you won't be prepared to use that item in the real world.

Thank you!

You are welcome.

If you are learning C#, I would recommend against learning Angular or React before you have a rock-solid understanding of C#. By learning Blazor, you are using your C# skills and deepening them. If you use Angular or React, you are introducing a LOT more complexity to get similar results, plus you are taking time away from learning C#.

That's totally fine. We have options for a reason.

You are welcome.

Happy New Year to you as well!

Excellent!

Great!

A great approach to what? Building things is an important part of the learning journey, but it doesn't replace the entire learning journey. For instance, I don't recommend people learn by just building things. That's how you get significant gaps in your education and misunderstandings in your application of principles.

They are important, but often very misunderstood. A data structure is how you store data in your application. It could be as simple as string or DateTime. It could be more complex, like Dictionary, Array, etc. However, understanding these is important. When you understand them, though, shouldn't be at a single point in time. Rather, you should learn them throughout your training in C#. Someday I may do a dedicated course on them, but that will only be to help people understand what they are and how to use them properly. But when I teach, I interweave these topics into learning C#. As for algorithms, what are they? What is an algorithm. That's something that most classes or other training doesn't really define. They show you algorithms, but they don't say what makes it an algorithm. An algorithm is just a bit of code logic. That's it. It is code that solves a problem. So again, you learn how to create algorithms as you learn C#. As you grow in your understanding, you get better at writing more efficient algorithms (logic code) that solves problems. When you get good enough, you start to see patterns emerge in your code. Things that you do repeatedly or situations that you often face. This is where common algorithms end up happening. Common solutions to common problems. In those cases, we call the common algorithm a design pattern. A somewhat standardized logic design to fit a common problem. This is why I don't push learning design patterns early on. In my opinion, you really need to see the problems a few times before you can appreciate WHEN to use the design pattern. Too often, people learn design patterns too early and they start using them every time they can. This leads to horribly inefficient code and over-engineered, buggy junk code. I hope that helps.

@@IAmTimCorey thank you Tim for the long reply, I did a few of algorithms and data structures (with python) and I have to say that it was a good training about how to think when I have to solve a problem (especially using the loops). Maybe I'll continue in the future but with C#. Congratulations again for your channel!

And those are the best lessons.

lol, I'm not sure that's the lesson I expected you to take from the course, but I'm glad it was helpful.

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

I'm not sure what you are asking, sorry.

Great! Best wishes on your journey.

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

@@IAmTimCorey Okay. I tried to now, but the send code feature is not working

We are looking into it.

Isn't there a DevOps course? I am sure I saw it.

Here is a video to help: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-viigJ9NwJ2o.html

Just because you are prepared to be a junior (or even mid-level) developer doesn't mean you will be able to apply to any junior or mid-level C# position. You are ready to start applying. You need to continue studying and broadening your skills. However, you are more prepared to get a job than someone that just graduated from college since you have more actual, practical experience than they do and you know more about how to do the actual job. A junior-level position in C# should require just an understanding of C#, not a bunch of extras. I know a lot of companies say a job is for a junior but ask for a senior-level of knowledge and experience. Some of those jobs you would still be right for. They are just publishing a wish list. I used to work for a company that hired junior developers right from college. I had to train them afterwards. The C# Mastercourse was heavily influenced by what I wanted to see developers have for skills before they started.

Thank you!

I linked to the C# Mastercourse in the video itself, but you can go to www.IAmTimCorey.com to find my courses.

Avalonia ui

You cannot build .NET Framework apps if you aren't on Windows. You also cannot build WinForms or WPF apps unless you are on Windows. However, you can build Console apps, web apps, and mobile apps. You can also build desktop apps with Avalonia or Uno if you are looking to add those skills to your inventory. If you want to practice those Windows-only skills, though, you will need to get access to a copy of Windows. Just so you know, you can use VS Code as well. It is free. If you already have access to Rider, use it. I just wanted to make sure you didn't think you had to pay to develop in C# when not on Windows.

Getting that first job is always tricky. Adding a bootcamp won't really improve the odds that much. The biggest thing, actually, will be networking with other developers. But here is a video on how to get work experience before your first job: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-HLEeK212uXw.htmlsi=LL4omSeTiwckiqdM Here is how to build a network of connections: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-OeMDhUN7xvQ.htmlsi=jd8MaRdGDp6KqPJn

Additionally who you worked with in the past doesn’t really matter. What matters is, knowing how to solve problems and providing solutions. You can easily demonstrate this by building projects that demonstrate your skills. Other thing to do is volunteer to build solutions for small businesses, charities etc something that people can use at a free cost or a small fee.

C# is still very widely used (especially enterprise), so is Python, Java, C++, etc… It also depends on the country you live in. Most jobs out there are for JS but most of them are also either freelance/temp or smaller companies.

Bro just learn, take off all these thoughts about which language is better to learn by x or y. Just stick to the plan and have fun

Absolutely. First, C# is actually a rather popular language, and it is growing in popularity. Second, every new developer flocked to front-end development with a framework (Angular, React, or Vue). The problem is that you need back-end developers to supply those front-end developers with data. You also have a flooded market where there are too many JS developers and not enough jobs. That makes it hard to stand out. It also makes those jobs less valuable, which is why front-end development pays so much less than full stack development (Angular, React, and Vue are front-end development only - full stack requires building back-end code that talks directly to the database, not just calling an API). Don't get distracted by trying to pursue the most popular. That changes constantly and popularity doesn't equal best money or best positions. Your depth of skill will be much more valuable than chasing after the next hot thing.

Then build something great. You've been complaining about knowing it all and having nothing to do for years now. I gave you a challenge going on two years ago now and I've renewed it repeatedly and you still haven't actually accomplished it. No employer cares if you have memorized what every C# command does. No employer cares if you have built a practice app with every project type in C#. What employers care about is what you can actually do with those skills. And they aren't going to just take your word for it. You need to prove what you can do. I've tried to help you do that for years and you still haven't done it. I think what you are missing is that you telling yourself lie #4 - "I'll advance even if I give up when things get hard." For you, the getting hard seems to be building a complete business application. Not a demo. Not a game. Not something that has an unintuitive UI and limited functionality. A complete line of business application. Do that and you will have something to show potential employers.

Best wishes.

Happy 2024!

Here is what I would recommend: speed run this path until you can't. What I mean is watch a video on the topic, create a quick practice project to ensure you actually know how to use it and how to implement the syntax, then move on to the next topic. I'd love to tell you to jump into the middle somewhere, but the problem is that there are probably foundational things that you will miss that way, which will leave important gaps in your knowledge. By speed running, you will ensure you know the topics and then when you start to make mistakes or not understand a topic, you can slow down, practice more, and ensure that you are grasping what may be new concepts for you. You will probably find that you speed up and slow down a number of times.

@@IAmTimCorey yes, this sounds logical to me. Really appreciate the response!

Absolutely. I outline that in this video.

It depends on your goals and your timeline. HTML, CSS, and JavaScript should take you six months or more to learn well. In fact, if you go beyond the basics in JavaScript, you should probably plan on a year. After that, you will be employable as a purely front-end developer but only for a small percentage of those jobs and the pay will be pretty low (front-end pay is low in general). Adding C# will take you another year. At that point, you will be able to apply for C# jobs (entry-level). Adding SQL and Git will elevate your skills and allow you to broaden your appeal to employers. So I would expect that this path would take you an extra year or more to get a job if you are looking to be a C# developer. If you are looking to be a web developer who also does C#, this might get you a job faster, but you will probably need to add Angular, React, or Vue to this list before C#, thus pushing your timeline back out another six months to a year. As far as pay goes, you will be paid better as a C# developer than you will as a purely front-end developer until you at least add a JavaScript framework.

Sounds good.

I did make all of these videos. They are in the C# Mastercourse.

Great!

Yes it is. The key will be how much you practice and apply what you learn.

Build a simple example. Watch what it does. Practice it. See if that helps. Also, try tutorials from different people to see if a different way of saying something might help it click. I have videos on them on this channel if you haven't seen them yet.

I had a similar experience when starting out with interfaces. Or most dummy tutorials really. I just could see wth it was ment to do and how DI relied on it. Then I got a job where I some real world code to work with. Within a few days it just started to click like a gear slowly, but exponentially starting to rotate. That’s when I learned that I most likely need to dive into real world production-level code

Those are smaller parts of the picture. We are really zoomed out here in this path. There is a LOT that isn't said just because it would take a lot longer to cover. But beyond that, some of these things are outside of the scope of learning C# even though they are really good to know. For example, CI/CD is a massive topic unto itself and isn't language-specific and it also isn't something that everyone needs to dive deep into. Everyone should use it with their production projects, but that's beyond a junior-level understanding of development. Authentication/Authorization is a tough one - it is really a senior-level concern, even though people will probably end up doing it earlier. As for software architecture, design patterns, etc., I recommend people wait on these until after they have significant experience building projects. That should happen before your first job (we build two "full" projects together in the C# Mastercourse, for example, in addition to the smaller ones I encourage you to do at every lesson). Once you've built applications multiple times, you will start to see where things could be better. That's when you will be able to learn about patterns and apply them. If you do it too early, you will apply patterns before they are needed, which means you will make your applications worse, not better. Architecture is the same way. Trying to study it or learn before doing is a mistake. Build tiny applications. Make mistakes. Learn from them. Learn how to make them better. Otherwise, you will try to apply complex architectural patterns onto an app that does not need it. You will make things worse, not better.

@@IAmTimCorey Thanks for the response. In my current test project(as you said, it is all about trying and personally I have built more than 50+ projects until this point) I have 10+ projects/modules with 5000+ lines of code in total and I am touching on a lot of complicated stuff. I talked to my teacher and he told me that I have done more than enough and I should stop and consolidate before jumping to new things. That being said I am pretty comfortable with that level of complexity and to be fair I kinda enjoy it, which is the reason as to why I keep on adding things. I hope you are right about the requirements of juniors and hopefully when I get to my first job since I have touched on these issues I will be overqualified, which will make my imposter syndrome go away :).

Rider works on Linux. I don't know which flavors of Linux it works on, though.

Thank u

Thanks for sharing!

It depends on the type of application you are building. There is a publish menu option on the right-click menu on the project name. You can publish your project and then distribute it from there (whether that is a desktop application and distributing the exe and supporting files or a web application and you are putting it on a web server or something else).

i can upload source but still somebody with knowedge need look at it and told whats heppen. aplication writed in Net framework4.7.2 (Windows forms C#) with a loots additional stuff to run and render 3d models play sounds and generate scripts @@IAmTimCorey

No, don't upload source code. Use the publish dialog to generate a published output.

and after that its generated Instaler for this but sill not wok outside my pc@@IAmTimCorey

Most of it will still apply, but the IDE will be different.

You use double as the primary way to store a decimal point number (1.23 for instance). A double is an efficient way to store decimal point numbers. There are instances, however, when you might want to use a decimal type instead. The two most common cases are when talking about money or astronomical units. The reason why is because decimal is very precise. Off of the top of my head, I believe double is precise up to the 13th place after the decimal and decimal is precise up to 25 places after the decimal. When you do operations on those numbers, though, those precisions will change (for the worse) based upon what you do. That's not normally a problem, but it is something to consider in specific cases (like money).

@@IAmTimCorey Thank you sir.. Last one question.. What deference .(dot) operator vs =assignment operator?

@@Short_vau I can't believe you ask these question here not on Google or from ChatGPT.

Absolutely. The only thing you cannot do is Windows-specific development such as .NET Framework, WinForms, and WPF. You can build Console apps, Web apps, mobile apps, and more.

It sounds like the first person you need to convince is yourself. Do that, and then you will have a much easier time making it a reality.

I lumped "improving your job" in with "get a job" in my list, but you are correct. As for lying to the FBI, what is that in reference to?

@@IAmTimCorey lol. You said lying to yourself is the worst thing you can do, sort of at the beginning. Just joking with you.

😆 got it. I was like, I'm pretty sure I didn't say to lie to the FBI. That would definitely be bad.

@@IAmTimCorey lol.

My recommendation would be after you have learned a lot of the syntax as well as how object oriented programming (OOP) works in depth.

Every Thursday I put out a podcast/RU-vid episode of Dev Questions where I cover the non-coding side of software development. That's basically mass coaching for developers. That's all I have time for right now, though.

No to reflection (that's beyond the foundational topics we cover and not something you should be using that often anyway). Not sure what you mean by attributes. In the multi-threading area, we cover async/await and how they work, but I do not go into threading, since again, that isn't something you should be doing directly that often.

😆

That means you’re learning :D

OK

Great! Make sure to keep up with the practice. Once you find out what exactly you are working on, practicing that more will be really helpful too. Congratulations!

If you don’t mind paying, the C# Mastercourse is the way to go. If you want to pay with your time instead, you will need to do some research. Https://docs.com is a good place to start. So is RU-vid.

Most of the advice does, yes. The same is true of my Dev Questions podcast. Most of the advice I give covers all of software development, not just C# development.

I would encourage you to rethink your beliefs because that is really bad advice. You even alluded to one of the reasons in your response. The basics are called the foundation for a reason - all other code is built upon this foundation. This is like saying "I don't need to learn to use a mouse because voice commands exist." You seem to be under the mistaken view that software developers primarily write code. That's not true. The primary role of a software developer is to express logic. You identify a problem and then identify how you will solve that problem. The code is just the tool to get the job done. You are skipping out on learning the foundational code pieces that will help you express even basic logic. Beyond that, learning how to write code (the actual syntax of it) is probably the easiest part of software development. The thing that is the hard part is learning how to use that syntax to create more and more complex logic. When it comes to debugging, it is never going to be easy to debug. No matter how advanced the tools get, they aren't going to be able to do the debugging for you. Again, debugging is about logic, not code. It is about identifying how a system is failing, identifying why it is failing, and identifying the solution to that failure. As for AI, no. Just no. AI is not going to be the junior developer for you. You have to not only drive it, but you also have to identify when it is wrong. A recent study found that ChatGPT is wrong about coding solutions 52% of the time and 39% of the time, developers didn't realize the solution was wrong. That means that AI will lead you down the wrong path. If you don't know what the right path is, you are going to create a mess (at best). Here is the full article: gizmodo.com/chatgpt-answers-wrong-programming-openai-52-study-1851499417 It sounds like you are new or newer to software development. I would encourage you to actually start to learn how to write C# code. Build real applications. You will find out that you need the foundational syntax and that debugging isn't just something the IDE does for you. That idea might live on when you are a beginner, but once you get into real-world development at any scale, it will quickly change.

Then you are watching the wrong videos. GPT will not replace developers. The only way it could replace developers is if it replaced practically every other profession first. Don't believe the hype from people who are inexperienced in the industry and don't actually understand what developers do.

​@IAmTimCorey is not going to replace developers if you adapt to the new technology, if not you might get replace.

It’s all about perspective, right? A boot camp will cost you over $10,000 and you won’t get better training than this course. If you can find the quality and cohesive training over multiple courses on Udemy, though, go for it.

There's an hour's worth of content here. It isn't a "few points" and a bunch of fluff. It is time-tested material based upon decades of experience.

Sure Tim, I like your content, it’s high quality,thanks for making it available. For this particular video, I think you could convey all of the same great arguments in a much shorter time. Just my 2 cents, please continue the good work

What is one hour compared to all the hours spend learning and practicing?

And unqualified developers apply for roles that are beyond them and ask for money they don’t deserve. Thats how things work. It will always be a push/pull.

You are welcome.

I'm not sure what you were expecting from this video, but I gave exactly what I said I would give in the title. Yes, I also mentioned that I have courses that cover these topics, but that's not the primary focus of the video, nor is it the main part of the video. What do you think this video was missing?

Practice builds confidence. When you've done something 100 times, you are more confident doing it than when you have done it 2 times. Beyond that, though, you will just need to take the leap without being fully confident. Almost no one is fully confident. We do it anyway. You can do it.

@@IAmTimCorey thank you for inspiring words Mr. Corey! I really appreciate that.