How does Linux kernel developers handle their work with millions of rows of code? Is their a method?
I've read that the kernel has about 15 million rows of code. To me, a man working with simple scripts of usually up to 100 rows of code, 15 million rows of code sounds like something very hard to handle with. I mean, I imagine a file tree huge in a galactic scale and a confusing environment.
But of course, it's not this way, because if it was this way, no human would develop the kernel, so there must be a way to navigate in the huge file tree and working with it when it's generally not confusing, and when it is just systematic and comfortable.
Is there a formal method of work / inode organization / finding one's way in this giant inode tree?
Just like astronomers basically map their environment this way: Universe > Laniakea > Virgo Supercluster > Local group > LIC > Solar system > Earth, I believe there is a similar mapping system in the Linux kernel, that could give someone like me, a junior programmer, at least just a glimpse as of now, to the core of the nix systems I work with.