I'm 70 years old and started to learn dotnet core last year. I'm good at building console application and have started with aspnet MVC. Next year I plan to learn some vanilla javascript. Thanks to channel owner for your honest advice. God bless you
@@ytg6663 Go to church, Grandpa? It sounds to me that you feel so threatened by a grandpa. Who do you think built the Internet, boy? Show respect and learn or you will never get hired by a grandpa or a dad because rarely will you get hired by a junior.
I was a JavaScript developer for the last 2 years, but I wanted to switch to C#. This is the first video I came across while looking for roadmaps. Damn, you are really good at explaining things. I hope learning C# will be worth it. I'm excited!
Thank you soo much for this video! im 40 yrs old and spent that last 17 yrs being a VB desktop programmer, to the point i got lazy and complacent... now i am struggling with just trying to stay modern. i have been watching videos, chasing buzz word frameworks, its all been soo overwhelming where to start, i didn't realize i have to go back to Jr level at this point. This video helped me to at least start somewhere! Great advice, straight to the point. Subscribed and looking forward to more.
Been there, I am 47, worked in management until I got fed up with it and stuck, used to be a C developer before that. Then I started my own journey to stay modern 4 years ago. I got the Azure Architect, Dev and Admin certifications, learned Terraform, Python, Javascript, React, functional programming, some Kubernetes and lots of APIs.
Came here after 16 years into developing with .Net, admittedly skeptical, expecting some level of bullshit, but everything checks out with my experience. Good job. Kudos on keeping it under 10min.
This video has been more helpful than other 1 hour or more videos about what you need to know. Simple, concise and to the point - liked and subscribed - thanks so much for this!
Dev with 25+ yrs experience here. This is pretty much all solid advice. If you were to follow all of it, you’d save yourself a fair amount of time and trouble.
I find this video to be very solid. Sound and sane advice that applies to me, a developer with over 8 years experience whose trying to re-learn some things after a break from coding of about 2 years. Thank you so much sir.
This is actually a very good set of advise and a pretty sweet roadmap - short and simple! 100% agree with everything said. And being able to do full-stack development gives you an edge again! Depending on the local market, I'd prioritize Blazor over React though, but check what the job descriptions are asking for first. As of late 2024, fundamentals matter even more - follow the roadmap in the video.
Concise, to the point, fantastic delivery and as a bonus an extremely soothing voice 😊I appreciate the advice. I'll work on these and try to get a job by the end of the year. Thank you once more!
This is the best advice video I have watched so far. Everyone tells you what you need to learn, but no one tells you what you shouldn't learn. I hope similar videos for other topics will come out. (Example: What not to learn in C#, what to learn, etc.)
Agreed! I would add that after you've written unit tests for a couple years, TDD really offers no benefit and will usually slow you down. But before that it can be a good tool.
4 месяца назад
Great recommendations. I'm not even a .NET developer, but as a developer with many years of experience, I can tell this is well intentioned, and bullseye accurate. Liaten to this man if you want to be a .NET developer.
So good to hear from an experienced and professional Dev! Straight to the point on the what frameworks and architecture concepts to actually learn. So many videos out there at the moment with young Dev's that have worked 1 year with Google letting everyone know they are 'ex-google' and just provide the same content talking about Leetcode or giving stock standard industry information you can find on Reddit.
As .NET / fullstack developer with 22 years of professional experience, I have to disagree on many points. MVVM - niche, MVC - no longer used in favor of Minimap APIs etc.
Thanks for the advice. I am a coding dinosaur; however, I put this advice into practice today. I have some legacy VB stuff and was working on something new today. Struggling with all the VB related .net framework nonsense - so I promptly scrapped the project. After creating it in C#, I'm 100% certain that I will be happier as a result. Your advice is forcing me to re-think the final 10 years of my career. Looking forward to availing myself to the books you've suggested and moving forward. Thanks again
Great advice and well laid out! I *am* intrigued though as to what technology has now popular more popular with StartUps, and why. One thing I will add though... coming back to programming (and .Net) after quite a few years away, I do think there have been some backward steps in technology compared to the early days of .Net. Some stuff has been made overly complex, and as you say, some stuff hides a lot away from the developer.
Excellent advice. It was spot on. When I first saw the video I was like: Oh no! not another brutally honest video that is just another click bait. But I was glad I fell for it.
Nice video. I loved the comment "Do not let clever abstractions prevent you from learning these building blocks" because it just so reminds me of how things have developed during my very long career as a developer. How long? Well when I started there was no Windows and Microsoft were around but very few people would have known of them. So clever abstractions include things like not writing in assembler, writing in C++ instead of C, desktop applications instead of (text based) front end for server applications, event handlers rather than handling a windows message, and now I guess we are back to server applications but we call it the web and we are even taking a step further and having off line "web" applications. Ultimately everything moves on and we have clever abstractions over clever abstractions all the way down. 😀
Thank you so much for this video much needed , worked in mern stack and joined a startup where they were using .net core . Did a web form project at uni nothing else about C#. Watched your video of difference between .net,core and c# and started to make some apis (not following youre advice ) , was demotivated but , end of video gave me some inspiration that "You need to understand how it all works " .
As a .net dev since 2007 (from vb script all the way to maui and blazor), I can attest that this is thoroughly sound advice! I also cant stress the importance of building something for the real world. This is the best way to learn anything really. Thanks for the video. Liked and Subscribed :)
Likewise, started back on .NET Framework 3.5 and still going strong. I'm mentoring a new graduate at my job right now and I'll probably be sending him this video.
I did the same and it was the best thing I did for my career and got me out of the enterprise focus companies and projects. Started using typescript a while back and thats how I get my c# adjacent fit every now and then. I do miss dotnet sometimes, and it seems to have got much nicer over the past 5 years, then again it was never that bad. Dotnet core is pretty nice.
@@starlords.7788 15+ years dotnet dev here, it was trash until 2017, they rewrite everything and around 2019 it became stable and blazing fast, comparable to Node it's around 20 times faster 🎉
Quite entertaining video. I have 20+ years experience of software development and are currently working on modernizing integrations to move away from the red flags mentioned, among many other things. Your vide made me smile.
Absolutely impeccable advice. I've been a professional .NET developer for more than three years after a year of self-teaching, and there's not a single thing I would disagree with or even add to.
Excellent recommendation that fortunately I already picked up elsewhere earlier, without really knowing why. But here I get the explanations! Thank you!
This is a really solid concise list for people starting out. There are so many similar titled videos that list *way* too many topics that will send people down the wrong wormhole. I usually don't bother commenting on here, but this deserves it. [More years of .net than I care to remember]
Im a fresh junior just gonna graduate from university very soon. I always wanted to be a programmer since my childhood but i never decided which field i should choose. A couple months ago i was makind 2 d games and then i wanted to make something more real and after i learn about .net i decieded to give a shot at this. Note that i hate javascript ect. Frontend definetly not for me. Information on this video was so helpfull and updated . I hope it will be a good carrier for me.
Good advice. I would also recommend not to skimp on these for understanding the storage aspects: 1) relational DB theory 2) ANSI SQL query language basics (not SQL Server's or Oracle's dialects) 3) Basics of non-relational/no SQL DBs like mongo, document DBs, etc.
This is most important video i seen on C#. I come from VB background, didn't learnt c# in 2010 now want to move to web development but not sure which one to begin with JS or C#. This video cleared my doubts. 👍
@@edandersen thanks, I subscribed you. I did tried web forms back then, made some Contact Us forms in it. Beyond that couldn't find any use for it, overall output was a ugly looking website. Then from 2012 onwards moved to mobile development from desktop apps. Now everything is web, even mobile app development is reduced. JS stack is used in new companies, Java and C# in large and stable companies who don't often change to new tech fast.
Great video. You've described my journey 90% skipped learning JS(react) something i regret every month when I try to learn it. Skipped the step to learn blazor. Once you go blazor you cant go back.
LOLS......this video is a good advice for starters. I have been coding for two years. Started with video tutorials, but currently i have been battling starting afresh from fundamentals and build up, as it seems i dont have DEPTH.......your video just gave me a good stating point and direction...Thanks. You have earned 1 more subscriber
Advice here is spot on. I started with .NET around 2015 and have worked at 3 or 4 companies where it's used primarily for anything on the backend. In 2022 I switched to a well funded start up that have a single critial to the business .NET component. We fixed the perf issues, delivered some important features and simplified things and now it's in maintenance mode. Since the jump I've been doing a lot of Python which has been an interesting journey. There's lots I don't like about Python and it's ecosystem especially the lack of types without a lot of ceremony. I still feel like I'm a .NET developer at heart but I'm glad I've got to see how companies and devs operate without any notion of .NET or Microsoft in their tech stack. I can see things from both sides which I'm glad about. Like you said no start ups are using .NET, most likely due to the perception of Microsoft even after all their efforts to be more "open" and cross-platform. I miss writing C# day to day but I'm enjoying not having my salary capped so much as a .NET dev.
Appreciate this, I'm about to start a first proper .NET dev job in two weeks - some slightly terrifying points but glad to see it (it's .NET Core, no SOAP/WSDL, etc. but they do use Blazor and I was about to learn that, jumping ahead of brushing up on JS - so thanks for the tip!)
Spot on good info. Made me chuckle at some of the "red flags" since I still deal with a lot of that stuff. Been at the same "larger Enterprise" company for 20 years this year (currently 44 and was hired at 24) and been with .Net since it's beginning (also still maintain a legacy VB6.0 code base when I can't avoid it), but enjoying working in .Net Core and Angular as well as AWS Cloud technologies these days... Btw, you say to "avoid" Angular but truthfully it is used by many "large enterprise companies" so it would be a good skill to have. Typescript, too. Also, totally agree with Dependency Injection focus for .Net Core as well as being very proficien in LINQ (but these days there's ChatGPT / Co-pilot to help you when needed lol). Again- good video!
Understanding what topics to skip as a junior developer is very important. Many beginners abandon programming due to feeling overwhelmed by the sheer volume of information and struggling to filter and prioritize the basic concepts.
Very good advice, seriously. With the one exception of "Blazor is for people who don't want to learn JavaScript". This is the equivalent of "Automatic transmissions are for people who hate cars". There are lots of reasons to like or dislike Blazor but I haven't heard a dislike/lack of ability of JavaScript being the catalyst for moving to Blazor.
It was an attempt at humor. I can't recommend a beginner starting out in their career to learn Blazor first. If they learn React or Angular at least it's a transferable skill to another tech stack
Not wanting to learn (or use) JavaScript is the main reason that I looked into using Blazor. 😁 I just wish that it was more adopted and supported. I’d love to write an entire web application using one language end-to-end.
I spent the first 15+ years of my career specializing in .NET, and migrated to the JavaScript universe after that - Node, React, etc. I left off with early Core and never learned much about Azure. I left .NET behind because I wanted to work on more fun greenfield projects and it seemed to be going down legacy road, like Java. I’m also more interested in AWS and it’s in much greater demand. I’ve been tempted to brush up on .NET but this video confirms my suspicions; I’d be faced with lower pay on less interesting projects, at less interesting companies. MVC is still relevant? MSSQL is still the center of the universe? It doesn’t sound like much has changed, fundamentally?
Similar situation here. I keep wanting to return to my roots, but every time I look into it, it’s kind of a mess. I was hopeful that Blazor would get adopted widely, at least in Enterprise, but those are the slowest ships to make a change. I will say I do have “unicorn” friend or two that work at small size / tons of money hedge fund etc type companies and they happen to use C# stack. High pay and mid level developers get to use practically whatever they want as long as it produces the results for the company. That’s a cool job. But yeah, the 99% large Enterprise jobs on LinkedIn for legacy apps, no thanks. Need to catch one of those projects that got greenlit to migrate to a modern stack, but those usually end up being React with Java on the backend so not so interesting either (depending on what Enterprise architecture deems as “target state”).
In Brazil it is very common in small businesses to use MySQL or even PostgreSQL, but MSSQL is king for dotnet. And no, every project uses just API as backend. MVC is just for sites and small projects.
In my position, we use .NET Framework 4 combined with .NET 6. We utilize SOAP services for a dynamics NAV ERP. Dynamics NAV is (even tho its a .NET app) a completely own entity, with its own programming language, database abstraction, etc. But i still love it.
As a .net developer since the first version I have to say: Congratulations, great recommendations! *But Microsoft's SQL Server only has advantages over open-source databases in extremely specialized functions. The exorbitantly high costs for M$ SQL can very well be saved.* 🙂
For a typical company, if they been using SQL server, it's not going to be your choice. And my experience is that in vast majority of cases the free edition with 10 gig limit suffices in most cases anyway. Can't remember the last time I ever walked into a job and was able to specify some new database system over what they are currently using. This video is 100% correct - if using the Net ecosystem, then 9 out of 10 times your using SQL server.
Yes MSSQL is widely used, but there are lots of big products which are running on MySQL because it's open source, I would love to listen more about learning. Thanks for this amazing guidance.
4 месяца назад
Great video! I agree completely. The topic I'm interested in, which you could maybe cover in the future, is the comparison of the Blazor framework and React...
After working for a c# company, this is so true. Working with soap and wcf was hell. Worst part is their source control is likely to use team foundation server having multiple branches.
As someone who started programming in the 70s, I was startled by your assertion that F# is for people with galaxy brains. The complete opposite was true for me; I use F# because I never figured out how to do OO that well; I'm more of a fan of what used to be called "abstract data types" or modules, and did my best to hack them with C back in the 80s and 90s (never touched C++). I've enjoyed watching the C# language team learn from the F# team over the years, starting with getting generics for .NET Framework 2.0 from Don Syme and Andrew Kennedy in 2005. Anyway, it makes sense to learn C# because there are more jobs for it, more's the pity. Learning F# would help new folks broaden their understanding of programming in general, but that is a different topic.
Grand response. I somewhat stalled viewing your video following my F# hiccup, but I've now watched it properly, and think it's great and very sensible. I'm a huge fan of Mark Seemann's work, and follow his excellent blog. Uncle Bob deserves praise for elevating the importance of testing and testable code, through his evangelism of TDD. Some of Uncle Bob's work hasn't aged quite so well; I generally agree with Dan North's response to SOLID, called CUPID, which espouses some great properties of good software, rather than "principles".
Finally some one said it. I agree with you, It is better if the DotNet team focused more on creating/enhancing the built-in templates (for example creating a sold template for API auth using JWT/Aouth2 - not the default Identity) instead of each year adding more and more staff that probably will not be used (at least in most of the app). I think, for me at least (after 10+ years on DotNet) , the lacking of support for built-in templates is one of the main reason why beginner prefer other framworks (nodeJS & Laravel)
One thing I'd advise for people who want to be .NET developers, is that the jobs tend to be mainly medium-large sized or rather corporate companies (as you mentioned in your video!) If I could go back I'd probably stick with NodeJS or Python which tend to be a bit more startup friendly. I would say though that C# has given me a lot of opportunity, and played an enormous role in my development as a software engineer and how to think about how to design/architect software. Disclaimer I'm a UK based full-stack c# and react developer who does work for a small startup who allows 100% remote working, but these jobs are few and far between sadly - enjoy your weekly townhalls!
WOW- I am a senior dev (work with C# since it's start) - and have almost the same opinion! MVC is a must to know in any case - although I am currently porting everything to minimal APIs, which I think will become the norm.
First time watching him and i love him He is straight to the point he doesn't seem like most RU-vidrs out there yapping on every thing to get views he talk he wants just to teach or advice I trust him
I am a 3rd Year computer science student i have learned JavaScript and React JS and built some projects now I decided to start learning .Net and C# MVC and this video helped me a lot and explained to me clearly what Roadmap should i follow. This video is great 👍
As much as I hate to admit it, this is 100% correct. I wish it weren’t true. I wish that there was one language that you could learn and be able to build a web application, but that’s not the world we live in. .NET is probably the closest thing, or perhaps JavaScript with React. But realistically, you’re going to have to learn both if you are going the Microsoft route. I would like to say, however, as far as reading Clean Code, I would recommend it, but only so that you learn what not to do. Everyone else would have read it, and will believe that it is the “ideal” way to develop professional software. However, after nearly 30 years of software development, I believe that simplicity should be your highest priority when designing and coding a system from scratch. I’ve seen almost every system I’ve ever worked on grow too large and too complex to reasonably manage, and preventing that from happening is probably the most difficult challenge in software development today. But this is a great video. More of this, please.
I’d also like to mention that after learning .NET, SQL Server and JavaScript, at some point I’d highly recommend learning assembly language for at least one hardware platform. It doesn’t have to be Intel, but it will give you the ability to understand what is going on when you are using .NET, and give you an advantage when it comes to writing small, fast, efficient code in any language. This is, of course, completely optional, but I did it, and I feel a lot more comfortable knowing what computers are good at (i.e. math) and what they are not. (i.e. artificial intelligence) The more you understand the hardware you are working with, the better software you will create.
I would also like to mention that .NET Framework and .NET 5+ aren’t “completely different”, in the sense that you can easily move between them and write identical code. But it is true that .NET Framework is no longer being updated with new features, so it will be missing a lot of functionality that .NET 5+ will have moving forward. But from the programmers point of view, for all intents and purposes, NET Framework 4.8 is just an older version of .NET. It’s perfectly capable of creating business software, but it will become unsupported in the next few years. So I wouldn’t recommend using it for new projects, and I would seriously consider upgrading to the latest .NET version in the next year or two, if at all possible.
Your last point - build an app - is the most important for getting a job. So many young people present a github repo with what amounts to an example project or coursework during their job hunt. Don't do that. If your only example is obviously a "guided course", just don't submit it. But _do_ make an app. It doesn't have to be big or complex. But it does have to be your own work.
I'm an experienced .Net developer, and I disagree with almost everything said in this video. Opinion debates are of little interest, but I give another piece of advice to beginning developers: don't let yourself be too easily influenced by simple opinions and form your own on more tangible elements.
I initially thought this is another fear mongering video do not learn X learn Y instead. But man, your advice is brief, concise and very accurate. These are exactly the thing I wish I knew when I was starting my career.
@@edandersen I am gonna get into C# which is incredibly similar to Java and I like Java. There is another reason I wanna get into .Net framework with C#. I bought a Dell PowerEdgeR720 refurbished Rack Server and multibooting it with Windows 10, Red Hat 8.10, Debian 12 and Ubuntu 24.04. Now I like windows cos my PowerEdge server has 150GiB RAM ...and Visual Studio runs first....hence I wanna develop .Net based web application....
Actually! I am the startup! I have managed to come up with a small enough project to start building a program because all my other ideas would take me too long to build.
