Comment on

I pick DBI for improving interface documentation!

I've worked with a lot of structured programmers, and as much as they dislike working with my OO code, they never seem to have a problem using DBI. Part of that is probably inertia...everyone uses it, that's just what you do. But I also think DBI's documentation has a lot to do with it.

Learn to write code people don't have to read to use. As for modules to read the source to learn from, sorry, not much in the way of ideas there.

--Dave

In reply to Re^2: Improving your skills by reading module sources by armstd
in thread Improving your skills by reading module sources by unlinker

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.


We don't bite newbies here... much
	PerlMonks