{"id":61,"date":"2005-06-20T11:40:59","date_gmt":"2005-06-20T11:40:59","guid":{"rendered":"http:\/\/dtrace.org\/blogs\/bmc\/2005\/06\/20\/yet-more-blog-sifting\/"},"modified":"2005-06-20T11:40:59","modified_gmt":"2005-06-20T11:40:59","slug":"yet-more-blog-sifting","status":"publish","type":"post","link":"https:\/\/bcantrill.dtrace.org\/2005\/06\/20\/yet-more-blog-sifting\/","title":{"rendered":"Yet more blog sifting…"},"content":{"rendered":"

Despite there being now four blog entries to sift through the
\nOpening Day entries<\/a>
\n(one from me<\/a>,
\none from Liane<\/a>,
\none from Claire<\/a>
\nand another from me<\/a>),
\nthere are still some great entries that have gone uncategorized. Many
\nof these entries fall into the category of “debugging war stories” —
\nengineers
\ndescribing a particularly tough or interesting bug that they nailed.
\nThe
\nproliferation of these kinds of stories among the Opening Day entries
\nis revealing: in
\nsome organizations,
\nyou’re a hero among engineers if you come up with a whizzy new app
\n(even if the implementation is a cesspool),
\nwhile in
\nothers you might gain respect among engineers by getting a
\nbig performance win
\n(even if it makes things a bit flakey),
\nbut in Solaris
\ndevelopment, nothing gains the respect of peers like debugging some
\ndiabolical bug that has plagued the operating system for years.
\nSo if you’re new to
\nOpenSolaris<\/a>
\nand you’re looking to make a name for yourself, a good place to start is
\nin the never-ending search for elusive bugs.
\nTo get a flavor for the thrill of the hunt, check out:<\/p>\n