3 ms·
> I still think it's a useful exercise for people like me who learn best by implementing a thing. Yes, but if you implement one thing, and then TensorFlow whi
by avmich 8y ago
> I still think it's a useful exercise for people like me who learn best by implementing a thing.
Yes, but if you implement one thing, and then TensorFlow which you plan to use does something very different, what's the point? Ok, different enough to justify the warning.
> Tensorflow, Pytorch, etc introduce a lot of magic for someone who is completely unfamiliar with the area.
Exactly. It's that magic which is interesting, after you're shown how in principle - but only in principle - the thing could work.
- sgillen 8y agoI guess the point here is that in this article we implement some of the magic that the higher level frameworks use, which I think will be useful later when writing and debugging our high level code. But I see your point which is that it would be nice if the article was telling us which part of the high level library we're implementing and what that would look like. I'm still happy with the article though and would not call it almost useless. But hey if you'd rather jump right into a tensorkerastorch tutorial that's an option too!
- avmich 8y ago> I'm still happy with the article though and would not call it almost useless. I really like the article. My problem is the next step, which I look for, rather unsuccessfully. > But hey if you'd rather jump right into a tensorkerastorch tutorial that's an option too! Do you know good tutorials for that? Preferably on the level of this article, only regarding those libraries?
- sgillen 8y agoPytorch's official one is very good: https://pytorch.org/tutorials/beginner/pytorch_with_examples.html https://pytorch.org/tutorials/beginner/pytorch_with_examples... They even start with NumPy, as the article does.