Lately, I had a dilemma about my next course. I had two topics in mind: ASP.NET Core 2.2 and Python.
I ran a poll on Twitter to see what my followers think.
I’m having a dilemma and need your help. What do you want my next course to be? Please RT.
— Moshfegh Hamedani (@moshhamedani) September 14, 2018
ASP.NET Core 2.2 was the winner. But I decided to pick… Python. Why?
I already created an ASP.NET Core 1 course last year. ASP.NET Core 2.2 is not THAT different from ASP.NET Core 1. Anyone who took my ASP.NET Core 1 course and watched it thoroughly should have a good foundation to learn the future versions without needing me and another course.
Plus, I don’t like repetition. Teaching the same topic over and over makes me super bored and tired. And I’m not a fan of patching courses. That requires me watching an entire course and that’s the last thing I want to do (watching myself for 10 hours). Plus, I have to find the parts that are outdated, bring my editor and code environment back to the same state, record new content and stick them to the old videos. I’d rather create a brand new course with a different project and include the lessons I’ve learned since then.
So, I picked Python because it’s an entirely different topic from my existing courses and this allows me to help a completely different audience. I have quite a few .NET courses and I’ve contributed a lot to the community. It’s time to target a different group of people who need my help. That is my rationale.
Having said that, my next course after Python will certainly be ASP.NET Core 2.2 because I know some people have been waiting for it for a long time.
This course is going to be a bit different from my previous course where I built a real app using ASP.NET Core on the back-end and Angular on the front-end. In the next course, I’ll purely build an API. No more razor views. I think they’re just a waste of time. It’s one of those areas that Microsoft is years behind what is happening in the community. These days, the common practice is to build an API and consume it using a front-end built with React, Angular or Vue. So, I’ll be taking the same approach. I’ll also likely touch on Entity Framework Core and Dapper.
Hope this post clarifies any confusions you might have for my upcoming courses.
I’d love to hear your feedback. So, drop your comments below.