*sigh*
- With SQL and HTML
- Biometrics, though nametags help, if you can convince them to wear them
- Following the XHTML specification
- Figure out what you need to change, then ask the database to change it
- Preface all of your SQL with "*- mother may i -*"
Not really helpful? That's okay. You didn't say what problem you were trying to solve.
The moral of the story: there is more than one way to do things because there is more than one thing to do. You either live with that ambiguity, or you spend the rest of your life trying to fit every problem to your ONE BEST solution.
Update: ... and that's why exploring other languages, paradigms (functional, imperative), and even design techniques (UML, design patterns, use cases) is important.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|