Conversation
Lorenzo Stoakes
ljs
While there are sometimes LWN articles/posts/etc. about things I cover in the book I generally try to avoid them as I've often found them to be counterproductive because:
a. I end up taking on assumptions the author did or speaking with 'their voice' rather than seeing for myself
b. The author might have made mistakes/glossed over things
c. The author is probably talking about a kernel version other than v6.0
d. The author often has a bias towards a certain problem/point of view that isn't 'exploring mm from bottom up'
e. I might miss things the code shows.
Therefore 99% of all I do comes from the source + me banging my head against the wall
a. I end up taking on assumptions the author did or speaking with 'their voice' rather than seeing for myself
b. The author might have made mistakes/glossed over things
c. The author is probably talking about a kernel version other than v6.0
d. The author often has a bias towards a certain problem/point of view that isn't 'exploring mm from bottom up'
e. I might miss things the code shows.
Therefore 99% of all I do comes from the source + me banging my head against the wall
1
1
5
This was definitely learned the hard way. Esp. early on but occasionally along the way I've found some good material, only to find that it really didn't help in the end.
This comes back to the whole bottom up vs. top down approach, bottom up kind of leaves you on your own out there
This comes back to the whole bottom up vs. top down approach, bottom up kind of leaves you on your own out there
1
0
1
David Jaša
djasa@cztwitter.cz
@ljs I don't understand either of them but I love you you write about both of them. I mean Linux/mm and book writing. 😊
1
0
2
Lorenzo Stoakes
ljs
0
0
2