2 ms·
author here. honest answer: there isn't much that covers the whole thing end to end, that's partly why I started writing this. but the ones I learned from: - E
by akhalilli 2mo ago
author here. honest answer: there isn't much that covers the whole thing end to end, that's partly why I started writing this.
but the ones I learned from:
- Edward Yang's "pytorch internals" post:
http://blog.ezyang.com/2019/05/pytorch-internals/ http://blog.ezyang.com/2019/05/pytorch-internals/
it's the classic, goes deep on the c++ side.
- the pytorch developer podcast, same author. short episodes, one internal topic each
- the pytorch repo's own CONTRIBUTING.md, the folder layout explained by the maintainers
- and if you want to build autograd instead of reading about it, Karpathy's micrograd / zero to hero
mine is planned as 12 parts, the list is at the end of the post.
part 1 (chapter Tensor: storage, strides, views) is in progress now.
- ayewo 2mo agoThanks for the PyTorch internals OG link and for putting together your PyTorch one-pager, if we can call it that :) Kudos. Off-topic: Some of your comments in this thread are dead, but I’ve vouched for some them as I don’t see anything wrong with what you’ve written, other than your writing here on HN sounds a little like you are using an LLM to compose each reply (or perhaps your regular use of LLMs is showing through in your comments?).
- akhalilli 2mo agothanks for the vouch, appreciated! :) and honest answer, English is not my first language, so yes, I rely on co-pilot tools when I write and it probably shows. the PyTorch content itself I can defend line by line, that part is mine.