Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
I dunno, I see "hacking" as poking at something without a great understanding or a strict methodology. In the case of "hacking a system", this would include probing the ports of a system to see what's open and vulnerable. In the case of "hacking away at some code", it's cutting corners and using trial and error rather than having a clear plan in mind. "Hacking code", in my mind, is about just getting it to work and worrying about finesse later.

Example:
I was doing some performance testing, and I found that the odbc.ini file on a server kept getting corrupted when the system was under heavy load. I filed a bug on it, but I didn't want to halt testing until I could get a fix. I wrote a quick perl script to check the file every second to see if it existed and replace it if it was corrupted. With this hack in place I was able to continue testing.

A few builds later, the problem had been fixed. I assumed that someone had gone into the code, found the cause, and fixed the fault that caused the file corruption. Wrong. My hack was simply rolled into the code base. That is the danger of hacking code: temporary fixes often become permanant.

-Logan
"What do I want? I'm an American. I want more."

In reply to Re: Fighting the denigration of hacking by logan
in thread Fighting the denigration of hacking by flyingmoose

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others having a coffee break in the Monastery: (6)
As of 2024-03-28 22:12 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found