<?xml version="1.0" encoding="windows-1252"?>
<node id="339239" title="Re: &quot;how do you design your APIs?&quot;" created="2004-03-23 17:54:04" updated="2004-10-30 11:11:42">
<type id="11">
note</type>
<author id="29600">
bsb</author>
<data>
<field name="doctext">
Often you want two APIs, a comprehensive and flexible one,
and an idiomatic DWIM wrapper Blah::Simple.
&lt;p&gt;
One way to reality check your design decisions is to
compare your API to another API from a different but 
comparable domain.
&lt;p&gt;
Another test (that I need) is to return to your
design after some months.  
"What was I thinking?!" is often the result
when you lose the blinkers of your original problem.
&lt;p&gt;
I don't like API designs that second guess you,
nor those that strictly follow a non-Perlish design
(usually found in library or system wrappers)

</field>
<field name="root_node">
338941</field>
<field name="parent_node">
338941</field>
</data>
</node>
