I actually like it because it makes me feel less dumb if I don’t get something so easily - that hasn’t happened yet (probably because I already know Rails and because Stephen’s doing a great job of explaining things) but I can see it helping those who might find some of the concepts a little difficult to grasp.
@ion - I absolutely plan to expand the course out, but I’m also hedging some risk due to Phoenix 1.3 coming out ‘Soon’. There are enough small changes to make me have to re-record all of the phoenix content I have in there already. After I get that update out, I intend to cover either some JSON API setup or OTP.
Regarding the pacing of the videos: its tough to get pacing video right in an online tutorial. Remember that for everyone who thinks the video is too slow, I have one person who thinks it is too fast :). Best policy is to move a bit slower, and let you use the ‘video speedup’ option if you want to power through it more quickly.
Can I be Goldilocks and say that the pace is ‘just right’! Seriously though, I’m enjoying the course, even though i paid $24AUD for it last week, but now the price has come down considerably. Not complaining though, very happy so far.
There are no objects in Elixir (nor methods). If they are about structs, then they should be referred to as structs (or generally as data) (and use “functions” instead of “methods”).
This is probably my biggest criticism of the course so far - one of the reasons we get books and courses like this is because we are unfamiliar with the specifics and need to know what the exact terminology is. Also José makes a good point about methods as well - I was actually going to post on the forum to ask if we should be calling them functions or methods (which I had always thought was for OOP). @StephenGrider, do you think you could re-record or voice over the instances where you refer to things with the incorrect term? It would be a massive help.
@seniorbrusko, I think most of the time it has been structs yes, but I’ve been taking it as whatever ‘thing’ he’s been talking about at the time.
@AstonJ you’re right, in the Elixir part I think @StephenGrider sometimes say objects in Tuples or Maps (maybe because his discussing JS and Ruby as comparison so he gets mixed up), but his explanations are gold. Still will recommend the course, there’s nothing like it right now. Looking at you, pragmaticstudio
I love that you take 1.3 into consideration! It’s gonna be a great update and as it should be out before the end of this year, it might be acceptable to wait for new episodes until then.
Please cover OTP, as it might be one of Elixir’s main selling points. For me, it’s not that easy to understand, and your pragmatic teaching style might help a lot
You should really cover OTP. It’d be a tragedy for Elixir/Phoenix to be full of devs who don’t know or bother learning the platform and just know phoenix_new.
I have finished the udemy course. For me, its really easy to understand because of the author like to explain the little things in details. cant wait for the update.
Also bought the course. I think its good because it explains very simply and clearly the language aspects that you need to get comfortable in order to proceed with more specific Elixir and advanced topics (ie. OPT and processes).
I was listening to the preview OO vs functional section and there is one thing I was wondering about. Isn’t it a bit confusing for people from an OO background to call functions in modules for methods? Because they are not methods. Which is what the section is about.
There is also confusion with objects/structs and a few other things iirc Robert. @StephenGrider, can you please confirm whether you will be re-recording parts of the course where these are amended please? Functional programming is a big shift for many and incorrect terminology makes things more confusing than it needs to be.
Yes, I’ll be addressing that with the Phoenix 1.3 update. I’m normally a stickler on terminology, so saying ‘object’ everywhere was uncharacteristic. Learning this stuff is hard enough already, so using precise terminology is key!