Weekly Edition
Return to the Kernel pageSponsored link
Vyatta –
Linux & Open Source
Alternative to Cisco –
Advanced Routing,
Firewall, VPN, QoS..
Free Download ->
| |||||||||||
Quote of the week
I find that the key to understanding kernel code is to understand the data
structures and the relationships between them. Once you have that in your
head, the code tends to just fall out. Hence there is good maintainability
payoff in putting work into documenting the struct, its fields, the
relationship between this struct and other structs, and any and all locking
requirements.
-- Andrew Morton<wonders wtf "ticks" does> (Log in to post comments)
Quote of the week Posted Apr 5, 2007 9:23 UTC (Thu) by eru (subscriber, #2753) [Link] An observation that applies well to most software... I think I first saw a version of it in Niklaus Wirth's text book "Algorithms + Data Structures = Programs", but it probably is an old pearl of wisdom.
Quote of the week Posted Apr 5, 2007 12:20 UTC (Thu) by amk (subscriber, #19) [Link] Fred Brooks also said something similar (in the terminology of the time):"Show me your flowcharts and conceal your tables, and I shall continue to be mystified. Show me your tables, and I won't usually need your flowcharts; they'll be obvious."
Quote of the week Posted Apr 5, 2007 16:07 UTC (Thu) by iabervon (subscriber, #722) [Link] Are kernel announcements which are quoted in the "release status" section automatically disqualified for QotW? "Big thanks" and "like a weasel on a dead rat" in the same sentence ought to count for something.
|
|||||||||||