Brutally honest advice for new .NET Web Developers
Вставка
- Опубліковано 28 тра 2024
- Want to become a Microsoft .NET / C# web developer? Enjoy this sometimes harsh advice for which comes from a decade and a half of experience. I go through what you need to know first, the best books to read, provide a roadmap to getting started as a .NET Developer and things to watch out for when getting your first .NET Developer job.
0:00 Intro
0:10 What to learn first as a .NET Developer
2:34 Essential books to read as a beginner .NET Developer
3:52 The types of companies that use .NET
5:48 What NOT to learn when starting out
#dotnet #csharp #dotnetcore - Наука та технологія
Please consider subscribing - it would mean a lot to me and also encourage me to make more tutorial videos 👍 Thanks for your support 🙏
There should be a video like this for every programming language/framework! Brutally honesty is always appreciated by smart people.
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
Amazing Grandpa.. ❤
Goto church Grandpa.. Pass sometime in devotion with God..
thank you for the inspiration. I am approaching 60yo and thought I was over the hill
Senior devs - programming is a relaxing activity. Perhaps making VR games in Unity? Build worlds in VR even if this takes you a long while.
@@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.
The best advice I've ever heard in my life. The most accurate description of what .Net and its ecosystem is. I absolutely agree with everything!
I have more than 25 years developing .Net
That’s how you do it when you know your stuff! Clear, concise, and covers all the key elements.
I am very appreciative of this information and pieces of advice 🙏
Man, you are sooooo right! I'm a C++/C# developer since decades, and this really warms my heart. Thank you!
Subscribed!! Thanks for this valuable info. I started as a React dev, but learning C# and .Net core has been such a breath of fresh air.
Great choice - .net backends work really well with react frontends.
As I .NET developer, I approve this message. GREAT VIDEO!
Thank you for crystal explanation!
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...
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 " .
Spot on with testable code, SOLID and understanding dependency injection!
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.
You just answer my question in my head about the .net version and what company uses .net .great video 👏
Glad you liked it! Don't forget to like and subscribe 😁
You're a realist i like that. Thank you for the guide
Awesome video! It perfectly describes my experience with .NET
I hope i come back and ask more questions... Thanks
Thank you! The advice for what to avoid was particularly useful!
This is actually really good information.
Excellent. Thanks ❤
Great guide thanks buddy.
No problem 👍
Awesome video thanks for sharing
thanks a lot, this was helpful
Lovely video thanks.
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.
I seriously cannot recommend Blazor for beginners as it limits their career options so much, hope you figure React out
I've a couple of decades .Net under my belt.. This is all solid advice 👍
I’ve been learning .NET for the past 1 year and this is the first video that summarises my journey. I learnt it in order. I build API and use React JS for frontend.
I need community where I can have accountability partners where we can work on fun projects together while I’m searching for job
Yeah. Me too!
Great video, 👍thanks, upvoted ... I am about half-way on this path, and I am wondering about Bootstrap, just started learning it after doing some steps in MVC, it seems quite relevant ...
It is very relevant and worth learning. Try Tailwind too.
I use bootstrap for new or small projects. It’s probably the easiest way to throw together a quick web page that looks somewhat professional. If the project survives long enough, you can always swap it out with something more functional later, like React.
The same goes for jQuery. I use it for small or new websites, but if you have a dedicated front end developer or even a front end team, they probably will use React instead.
My only real problem with React is that every time I try to use it, it has just been completely redesigned, and all of my previous experience is now worthless. It’s like the React team exclusively hires developers with ADHD…
True. I started studying from c# v 1.1 without a road map. And when I kept studying I found that there was a barrier and if I wanted to break it You have to do it by going back and studying something else before. Otherwise, what you write will not be of high quality. So it is a waste of time. If there is no correct path There are no shortcuts on these routes, just like Ted said. The recommended route is the best. It's better than paving the way yourself like I've done, going round and round like a jigsaw puzzle. Until I understand that Where should I start? What next?
Subscribed. I like the tips. I am not a junior developer, but I wish I had this information when I started my career. Thank for sharing.
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.
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!
Thanks, yeah not the first person to say take a look at Angular. It's changed since I've last touched it I've heard.
I agree with everything this article says. Oh, and my startup uses Sanic/Python for our API and NextJS/React for frontend with kubernates.
As a long-term .NET developer I totally acknowledge and confirm your "red flags". 🙂
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. 👍
TypeScript goes really well with C# I suggest learning both
@@TedsTech 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.
மிக்க நன்றி. இப்போ எனக்கு நிம்மதியாக உணர்கிறேன்.🎉❤❤❤❤❤
What NOT to learn as a beginner is so helpful. It's usually the thing that holds you back the most as you try to learn everything and get stuck.
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.
I fell for the C#, Blazor, Postgres trap because I was taught jQuery, ids, and markup not knowing that JS has classes, this,, polymorphism, etc. I also wanted to start a business using this stack. I'll be coding in TS for front end and C++ for the backend end next time.
I don't know what database to use. All relational databases seem to be the same to me.
Wow! As stated by many, I wished someone did this for JavaScript or ruby years ago
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”).
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.
You are my man:) I agree 99%, except WindowsForms which are really nice for some quick prototyping when making POC with e.g. some hardware...everyhting else is taking much more time to implement to get the the one time purpose. I miss it at my MAC:(
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.
Yeah that sounds awful
There are better places though
thanks for super content
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.
Not sure about the SQL server point, it’s true that the majority of enterprise businesses will use it, but it’s no sweat either to install and register a different DB provider… Postgres for example, there is literally 0 setup complexity, code first / migrations work perfectly fine out of the box, there are subtle subtle differences to contend with such as DB defaults / column naming etc etc but it’s all very very minor…
I agreed with pretty much everything else apart from the .NET framework / .NET core point, I think the bridge between them is so short that it’s not even a factor, if you spend 2 years developing and maintaining .NET framework and then suddenly having to start working on .NET core - the changes that you will encounter and things you will have to learn will be most inconsequential and breezy, it’s not like going from React to Vue, it’s more like going from Class Components and lifecycle methods to Functional Components and hooks.
Hello, good timing as I'm kinda new to web development using .net I've built apps using vb .net , unity and .net framework ( basically runtime)
but when it comes to web and backends ( asp , orm dbs odata API etc...) I'm pretty much new despite some little overview knowledge.. I learnt fullstack js and still deciding if blazor worth it ( despite some issues like community support , stateless connection etc ..)
I'm certain that I will probably do both as I'm into polyglot programming.. but when it comes to unified tech stack I really can't decide between next or asp although I will most likely use BaaS for rad development. .
for the future cloud native vs monolithic I think time will tell and I shouldn't bother about it.
I'm really interested in the idea of one codebase I'm pretty much onto it but recently I think it's vague idea and won't be practical.
When it comes to native app development I think I would rather use unity or fuseopen ( I know all UI frameworks out there) probably gotta try blazor_maui binding few more times I think pwa with no ui framework is better option for me then just Warp it into native app when it's necessary.
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.
Great insights ❤
It makes me wonder why Blazor is not widely used despite the fact it is a strong alternative to React and Angular?
You can make a video regarding this.
all very true,
It seems I avoided exactly what you said except using PostgreSQL. I'm building an entertainment web app with .NET Core Web API and React on the front end. I've found my Controllers a bit messy and started looking for a solution. What do you think about the repository-service pattern? Is this overkill for a small web app (at the moment) or it will pay back in the future when implementing a new feature? Thanks for the video.
I don’t think it’s ever a bad idea to use a clean architecture starting out. It doesn’t really take much more time to set up but, as your app grows you save time.
@GiantsOnTheHorizon Thank you for answering my question. I'm more confident that I made a good decision.
I generally don’t like starting with a particular “pattern” when building a new system from scratch. The reason is that it introduces an artificial abstraction on day one that may not be necessary. So, you may have to work around that abstraction at some point, which is just wasted time and effort for no real reason. Instead, I would recommend learning a pattern, specifically what it’s strengths and weaknesses are, and then, as you build your application, implement your own pattern that has some of the strengths and none of the weaknesses. I know that is a bit vague, but to put it another way, use what you have learned to come up with your own patterns that fit your mental understanding of your system, but write your own code instead of using someone else’s approach for maximum flexibility and understanding in case you need to make changes to it in the future. Hopefully that helps a little. 😉
thanks, my goal is unity C# game dev but good to know mastering c# can this route as well,
Yes, the coding style is a bit different but C# gives you web dev as a backup
I've been learning .net recent and it's so painful. I assumed the problem is that tutors and learning are coming from Java or are at the experienced end - hence are oblivious to how painful this is starting from a more beginner level.
Great video telling what MVP wouldn't.
However, I don't agree on MSSQL, which is contradict to SOLID, testable and di(as a result).
EF core is an abstraction layer, on which our code depends on and doing so is conforming to advices from SOLID and other design principles.
Telling C# developers to lean MSSQL or any specific db product is the same as telling to stick to a concrete although you already have good abstraction.
EF core made consuming db is one thing and providing is another, calling is ours and implementing is theirs, and the choice of db is a matter of business, not a technique; which db is suitable in terms of money at current business standing of us or out clients.
On the "learn MSSQL first" suggestion - its just to be maximally employable. I'm not making a statement on how good it is or if using it is good architecture. Thanks for the comment!
Maybe the recommendation should be “install SQL Server” first, and build an application using it. You can get by without actually writing any SQL queries or stored procedures these days.
I used to develop web apps in .NET but moved over to Python. I have an obsessive dislike for C# (always used VB). Great advice though.
Respect ❤
thanks and may I know what's your opionion of AL / ML with .NET as compared to Python?
For the sake of your career use Python
@@TedsTech but I am in the (investment) bank industry and they are still slow in adapting AI. So I am not sure if I should learn Python or just sharpen my .Net skills
Learning Python is an extremely good idea for your career. Knowing it plus C# is a great combination. Don't pigeonhole yourself as a .NET only dev is my advice.
100% agreed
Follow this guys advise..
is it ok to jump right to learn wpf after learning c# instead of asp net mvc because I want to build desktop app?
Yeah why not?
I'd look at Avalonia or Uno for cross platform support.
Thumb up, if your current position composes of all red flags mentioned :)
poor b*stard
sir is System Analysis and Design prototyping is also needed to learn?
Learn to build an app first
Gold
The only thing I think is not perfect advice here is the react part. Angular for all its flaws is still wuite widely seen in job offerings and can serve its purpose well. Other than that pure gold this video 😊
Maybe less so in my part of the world. Thanks for the comment!
@@TedsTechMost of the corporate companies using .Net choose angular for front end. Primary reason is Angular is full fledged framework and React is a library and needs other packages to create a complete app.
Angular is good, but be aware that there about double the number of jobs looking for React experience.
what do you think about the future of .net as AI is progressing further . Is it still a better to option to learn as compared to java
Not a bad option. C# in particular opens you up to game dev with Unity too
Even the best code written by AI is a long way from replacing a skilled programmer.
I am surprised there is a .NET Dev that is happy and excited to share some insights about .NET. Most that I have met on Tech Support forums were cold blooded animals that made me want nothing to do with .NET.
wow
I agree on almost everything except the MSSQL part. It's already trivially easy to use MySQL or Postgres on .net core 3+. EF Core will handle most cases and most of your code will remain the same. And as per your advice, if you already know SOLID, DI, etc... implementing the exceptions will be simple. We went full Postgres almost 7 years ago and never looked back.
Also yes! Blazor is for JS haters, not for ASP lovers.
Absolutely right. My advice is for people to maximise their chance of getting a job though, hence the MSSQL recommendation
Sir...so your advice for me is to start learning MVC before blazor?
@@chikalawrence8502 My advice is don't learn Blazor at all until you need it.
@@TedsTech OK. Thank you very much Sir.
If you want to work in a .NET environment, then learn MS SQL Server because that is what the company will be using more than 90% of the time. You need to learn T-SQL and how to interact with stored procedures. Tip: If your SQL compilations value is greater than 1, then your application will never perform well and it will not scale.
FYI - Oracle is the best RDBMS on the market. Even with ACID transactions its implementation of redo logs (in addition to transaction logs) prevents the problem of reader blocking writer. This does require the developer and/or the database administrator to understand how to properly configure redo log segments and to tune a number of other parameters. Out of the box, Oracle is only configured to support development of application prototypes; it is not tuned for enterprise loads.
Agreed with 90%. This is what I don’t agree with:
1) MVC. Don’t do this. Use Minimal APIs as this is how most web apis are done in iother languages. MVC is dated and you can pick this up later
2) Clean Code. This book has so many questionable advice might as well read what good about it online. Two much better books ( a philosophy of software design and A pragmatic programmer 20th edition). You can read these many times during your lifetime.
3) Learn basic SQL and then Postgres or MySQL as this is the world outside of Microsoft. I’m a dotnet dev for a decade and NEVER used MSSQL. I know it’s an outlier but now i can jump to other stacks and have a solid DB under me
thanks for the great comment, my thoughts:
Any large application using Minimal APIs either ends up writing its own crap version of Controller routing or ends up using MVC directly.
For some noddy azure function or lambda yeah go nuts with Minimal APIs.
MVC is dated?????? Yeaaaaaah....no
You said most start-ups dont use .Net. What in your opinion are they using ? Node.js + Next.js + React ?
For web apps yeah, stuff along those lines. Which is why you should learn React as an SPA if you have to - so you can transition out.
React and Node.js are my thing since my bootcamp focused on them and my projects use them, but I see loads of .Net jobs and barely any for Node.js.
Learning C# now so I can get into the .Net world. Had my eye on it anyway since I wanted to make games with Unity as a hobby, but seeing the jobs available pushed me to switch sooner rather than later.
Can you recommend me some courses to become a dotnet developer? I currently only know Js/React and nothing about backend or databases.
Microsoft provide great resources, everything you need to know is on here: dotnet.microsoft.com/en-us/learn/aspnet
@@TedsTech yeah I tried going through that but didn't understand anything, can we have a quick call? if you do mentorship, please provide me a way to contact you, thanks.
Hey sadly I don't. @nickchapsas does some great courses on his "DomeTrain" website
@@lostinthenarrativvecheck out Nick Chapsas
even as a 20+ years developer (mostly .NET) that statement "blazor is for those who don't want to learn JS" hit hard, especially as I am concerning this for a new project and want to go "forward" technology wise :-/
The thing is once you hit the edges with Blazor and need to do something tricky, you'll have to use JavaScript anyway
Thanks a lot! But i see it too late 😂😂😂. New subscriber!
Thanks for subscribing!
The more stable the job, the older the technology. And there is logic behind it.
Unless you want to be a job hopper and move every 1-2 years, you need to be able to cope with older technologies even things as notorious as MSMQ.
In .NET world everything becomes old on average in 4 years!
There are certain skills that you never learn in those small startups using coolest technologies, you have to play with big boys in those boring enterprises in order to become a big boy.
Not every enterprise stack can be lifted to Azure, in reality most of the time you have to work on prem regardless of how cool the cloud is.
Useful insight, hope it helps someone. Thanks!
I completely agree with you. I was a Unity Game Developer and have spent my entire career working for startups. Now, I find myself in a career gap of five years. However, one crucial lesson I've learned is the importance of starting your career in a reputable, large-scale company.
Many startups are in their infancy and often prioritize launching their product in the market over its quality. Consequently, I didn't gain much knowledge or skills from the companies I worked for. It felt like a waste of time.
Therefore, I advise securing a position in a large company where teamwork is valued, and the focus is on building high-quality, robust products. If you've never been part of creating a high-quality product, you may struggle to do so in the future.
That's why it's vital to work in a well-established company that prioritizes the quality of their products. This contrasts with the fast-paced environment of startups where, despite exposure to various technologies, you may not master any. So, choose wisely where you start your career journey. It can make a significant difference in your skill development.
True. All the stuff he mentioned not to learn I have all of them in one project code base. That code has comments from a time when I wasn't even born 😂😂😂
@@l1f07bscs0035 Respect to you sir for keeping the flame of WCF alive
@@TedsTech i learned while I'm last year if graduation working on internship where they hired for 15 per week but end up working 60 hrs. It came with lit if lagacy stuff I would say c++ libs to turn on highway signs during snow.
But the concept of Angular is similar to MVC , why choose React, just a question bcos I am stuck at this point
More job opportunities
As someone who has developed in .NET since version 1, Angular for 6+ years and React for 2 years, I would suggest that your question is very valid. Angular implements all the concepts that you will be familiar with in .NET such as controllers, routing, dependency injection, services etc. React has none of them. To implement them, it requires a dozen extra packages and nearly all of them are 'fudges' trying to make React look respectable when it isn't. If you want to build enterprise level, quality, well architected software, Angular is the way to go. If you want to follow the latest fad and create poorly structured code then go for React.
You have to remember that React came from the UI developer direction and enabled non-programmers to get into the coding game, writing poor code. Angular came from the back-end software engineer direction, hence it is much better structured and engineered.
@gppsoftware while correct, there are about double the number of jobs out there with React vs Angular.😊
Hi Ted, I was a Unity Game Developer. Now i have 5 years of career gap, I have forgotten everything. Now I want to start my career once again from scratch. I want to become .Net developer because I was using C# while developing games. The question is how can I get a job with 5 years of career gap? Any suggestions for me?
depends on the reason for the gap.
@@TedsTech 🥺 I don’t have a clear reason. I just didn’t like game development anymore, so I quit without a plan. Then, I wasn’t sure if I should do web development, mobile app development, Data Science, or something else. Now, I’m not good at game development, web development, or app development. I feel like I’m not good at anything. Companies aren’t hiring me because I have a gap in my career.
@@rosepainting8775 Build a complete application that fills some need and release it as an open-source project. This will be your resume builder to demonstrate that you have the skills, experience, knowledge and, just as importantly, a real interest in software development.
Just lie. At least to reduce the gap to ~ 6 months. Though I'm not sure if your laws allow you to.
Also, create some project that you can show to recruiters.
@@dieter5220 Looks like that is the only option now.
I want to change my work from gamedev (Unity 3d - scripting backend based on C#) to web .net . And ... it will be hard. Sadly 😞
Web development is only hard because the industry has gone a little crazy in the past 10 years or so. I don’t envy someone starting out today because the landscape is complete chaos. My advice would be to pick one platform and focus on it like a laser, until you feel like you have mastered it, before moving on to something else. (.NET, JavaScript, React, Blazor, etc.)
The reality is that any one of these will get you in the door somewhere, and from there, you will learn everything else you need to move to other companies whenever you want.
As a .NET Developer with 19 years experience in .NET, I would not recommend starting DB access using ANY ORM framework, including entity framework.
Learn SQL, learn to do things directly with SQL queries, and table designs, database indexes and performance optimizations.
ORMs may abstract all this away, but will very easily lead you to horrible database performance
ORMs are a useful tool, especially when building dynamic queries in a typesafe way. EF uses parameterized queries so the query plan is cached - if the resulting query is basically the same then perf will be. Microsoft also tune the generated queries for SQL Server with tricks that would make a DBA proud.
It's not that cut and dry. For the 5% of queries EF generates that are slow yeah go for it and drop down to SQL or sprocs
Modern development is moving away from joined tables and stored procedures, and toward microservices that just return JSON data, and does all of the “logic” on the client side. It has its advantages and its disadvantages… but stored procedures aren’t as important as they used to be. You can avoid them entirely nowadays for most applications.
I agree with you. But it is too late for me.
learn blazer web assembly with a .net core backend
About Dapper and Blazor ?
I mention them, watch the vid.
Forget Dapper - it is very outdated tech. Use Entity Framework.
What do you think about .Net MAUI?
For the sake of your career don't touch it with a barge pole
I got no idea about the webdev or appdevworld. I work in industrial engineering and i haven't seen a single thirdparty component for MAUI, Xamarin Forms, WinUI, Win8/10 Store Apps or any of the fancy new UI frameworks of the last ...15 years. There's a reason Microsoft brought WinForms and WPF back for Net5.
I still use WinForms for almost all of my personal projects. It just doesn’t get any easier for desktop apps. (Feel free to change my mind)
I am a newbie, i wanted to became a .Net web developer. Please Suggest some piece of advice
Watch @nickchapsas roadmap videos
@@TedsTechcan you do a review video on that roadmap video?
Why do you recommend learning ASP .NET MVC instead of leaning .NET 6? Isn’t ASP .NET MVC outdated?
MVC is in .net 6 (and 8). Just learn to use controllers.
Why do you prefer react vs angular ?
React because there are more and better job opportunities
@@TedsTech there may well be more job opportunities, but there are also sufficiently large numbers of Angular opportunities that I don't think you will have too much of a problem with either. The problem I have with hiring people who have used React is that there coding standard is generally not very high and very few of them have any idea how a backend works.
@@gppsoftware Correct. Don't ask a pure front end dev to work on backend.
But from my experience backend devs can do decent React, as long as its with TypeScript.
@@TedsTech True, but a developer working in .NET on the backend will find Angular easier than React because Angular is structured in a similar way to .NET (or even many other languages such as Java) and replicates many features such as forms, controllers, routing and dependency injection. React has a completely different style of coding to conventional coding and is full of 'fudges' to make it appear to implement the same features. Personally, I don't believe that React is a good choice if you want well architected, maintainable software - every organisation I have seen using React has ended up with an unmaintainable mess - they all hark on about React being 'no-opinionated' but the downside of that is that there is mass inconsistency and every app is the 'opinion' of the developer who wrote it. In the not too distant future, I predict that there is going to be a massive React tech debt problem!
@@gppsoftware Fair, maybe I need to take another look at Angular. Previously used it in the Angular 1/2 days. Thanks for the comment.
Nice video, but I must disagree on API controllers, one can start with minimal APIs without any need to learn about controllers or ViewModels and MVVM, in fact, I have junior developers who are up and running after learning, C#-->Web API with minimal API --> Blazor... no need for MVC!
Great!
Is PHP better than .NET???
As a full stack developer (in many languages and environments, including all .Net's) for many years, I cannot more agree with this wise summary!
I'm not a .NET developer (not anymore) but "Dependency Injection in .NET" is my bible-book
Mark Seemann is a god
Streaming Global
Life is great and diverse... don't mess with ms products. You only feel bad if you do. You can buy ms stock if you want, but don't touch their products.
Learn LINQ if you want to work in a legacy environment, but never use it if you want your application to actually scale under load. LINQ is not suitable for heavily used (truly) enterprise applications where you need to get every last bit of performance possible out of the database engine. LINQ is only suitable for light- or medium-use applications where performance really doesn't matter.
SQL server caches query plans, and LINQ over SQL can use pre computed / cached queries on the app side. There is a trade off to think about before moving to parameterized SQL queries or god forbid sprocs.
@@TedsTech While SQL Server caches query plans, it generates a new query plan for all dynamic SQL queries. DYNAMIC SQL QUERIES ARE VERY BAD! NEVER USE THEM IN A PRODUCTION ENVIRONMENT.
Parameterized SQL queries can be used to reduce the SQL compilations to 1.
Stored procedures have the advantage of ensuring that multiple applications which access the database use the same logic, and all optimizations are performed by someone who is typically much more knowledgeable of the database engine than the typical software developer.
I've been writing code since 1976 and have worked on various types of applications, including those having greater rates of distributed transactions than Amazon processes with simple transactions.
IMO, most software developers should not be permitted to touch a keyboard, much less to write software. The majority are little better than monkeys turned loose to pound away at keyboards in hopes of producing something useful.
even in the enterprise context, in my experience in 90% of the cases EF is more than sufficient. Especially when you know how EF works and what your linq gets translated into etc.
Entity Framework uses parameterized queries, so the query plan is cached even when using EF... It doesn't use dynamic queries / string interpolation
Learn LINQ if you want to use C#. It will make your life way easier, even if you don’t have a database. Running queries against collections of objects is extremely powerful and easy, and will reduce the amount of code that you have to write by a factor of 10x. It’s also great for querying databases. 😏
Hit like if you agree with all he said
Gotta know git these days.
well yeah
You don't need half of all that, 5 years to pick up all that, wouldn't that be a nice idea
htmx is another way to avoid JavaScript hell
Hire me 🤲🏼
Not hiring sadly!
Say NYET 🇷🇺 to Dot NYET! 😂
Username checks out lol
@@TedsTechJava 22 finally got string interpolation, time to switch 😂
.Net is dying now, there are very few new positions and those are expecting you to have a Master's degree or/and tons of other skills (DevOps, Cloud, FrontEnd, etc)
Many .NET projects are switching to the Power platform because no-code/low-code developers are way cheaper.
Bleak