The Medical Staff office where I work purchased an expensive bit of software to help them keep track of the credentials of the physicians who work at the hospital. It's based on an MS-SQL database and works well enough for the people that use it. However, they wanted to tap into the database and make the physician information available to the entire staff of the hospital. When it came time to implement that particular piece of the project they found that it required purchasing many, many more software licenses and having a tech install it on every PC in the establishment--a large and expensive proposition. While the other analysts were standing around scratching their heads, I dabbled around with some Perl code and SQL programming and built a nice little interface that displays the information on our Intranet. It works well--people use it--and it cost the hospital exactly nothing in actual dollars for software. It's not so much the code that I'm proud of--it's the ability that Perl has of being able to do much-with-little. And the fact that while I'm considered to be a bit of an odd-duck here, I was able to pull up a solution for a problem that no one else knew how to solve.
-
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.
|
