61–70 of 73 posts
Am I the only one who thinks that courses that don't teach TDD from the start are useless? How can you write an app and not programmatically prove it is working as expected?
If its the latter, that's an approach that I've never seen before but its definitely thought provoking.
Am I the only one who thinks that courses that don't teach TDD from the start are useless? How can you write an app and not programmatically prove it is working as expected?
However, I think there's a lot of validity to the idea that every tutorial should include lessons on how to test it that new topic, and even give examples of how to implement a TDD approach. But those lessons would (IMO) have to come after the initial parts of the tutorial that taught the concept first.
The title could really be a lot better :p It's not like all the other resources cost.
Earlier quoted context omitted.
Do people actually put that kind of stuff on resumes? I've done a good handful of MOOC courses (usually not all the way through to be fair), but I can't imagine actually paying for a certificate so I can put it on my resume. If I want to show that I know React I'd rather just build something with it, throw it on github, and list it as a side-project.
I don't think Udemy has any kind of completion certificates, and I can't imagine would put "Watched video about X" on their resume.
Earlier quoted context omitted.
not saying you're taking offense to the critique, but I wouldn't. While I don't use Redux nor have experience with the docs for it, there have been some concepts that I didn't grasp from reading the docs for a topic where others had a better understanding of it coming out where after someone broke it down in a blog, it allowed me to understand it as well (at which point the docs were beneficial as a resource to come…
Right, not taking offense - just saying that it's hard to come up with actionable ways to improve things when most people say they're good, and a few people say they're not helpful, and neither group really gives much in the way of specifics :)
One size doesn't fit all, and some people don't speak for all.
Earlier quoted context omitted.
There seems to be a culture of collecting Udemy courses among fledgeling web developers.
Young web developers certainly seem to love video courses for some reason. Maybe I'm just old and crotchety, (well, one of those is certainly true), but I would much rather get my fix textually and go along at my own pace. Flipping pages or scrolling is still superior to trying to scrub through a video timeline.
However, if I get too perplexed by something and need hand-holding to understand something, I look for videos.
Also, videos help in cases with libraries whose documentations are lacking or don't have docs regarding integration with something.
Why would you even pay to learn React? The official doc is free and takes only few hours of reading.
For programming veterans who have at least some frontend experience and just want to pick up React (i.e. me) the React docs and scattered tutorials/stack overflow sites was sufficient. But I wouldn't remotely recommend this path for someone relatively new to programming.
Earlier quoted context omitted.
I'm just saying that there are more valid selling points for React than speed.
It's a valid point - if I were concerned that Jr. developers would parrot every line from the course to the ridicule of very particular Sr. developers I would have specified that the Virtual DOM makes React faster than if it were trying to directly use the actual DOM, all else being equal. But since that wasn't a concern of mine when I made that video (it is far from the main takeaway of the course), I kept it as sim…
Virtual DOM (unless I am mistaken) is a solution to the problem that React would have otherwise introduced. But surely, selling points of a framework are not how it solves its own technical problems, but rather what problems it undertakes to solve for its user.
Why would you even pay to learn React? The official doc is free and takes only few hours of reading.
For programming veterans who have at least some frontend experience and just want to pick up React (i.e. me) the React docs and scattered tutorials/stack overflow sites was sufficient. But I wouldn't remotely recommend this path for someone relatively new to programming.
Earlier quoted context omitted.
For programming veterans who have at least some frontend experience and just want to pick up React (i.e. me) the React docs and scattered tutorials/stack overflow sites was sufficient. But I wouldn't remotely recommend this path for someone relatively new to programming.
I wouldn't remotely recommend react for someone relatively new to programming.