Are You a Hacker? 10 Signs You Might Be

  • Thread starter Thread starter saltydog
  • Start date Start date
Click For Summary

Discussion Overview

The discussion revolves around the characteristics and behaviors that might identify someone as a hacker, with a focus on technical knowledge, programming skills, and experiences related to computer systems. Participants share personal anecdotes and opinions on what constitutes hacking versus being a knowledgeable programmer or engineer.

Discussion Character

  • Debate/contested
  • Conceptual clarification
  • Exploratory

Main Points Raised

  • Some participants suggest that knowing technical details like hex dumps or having extensive manuals does not necessarily make one a hacker, but rather indicates a strong knowledge of computers.
  • Others argue that engaging in risky behaviors, such as attempting to break into secure systems or experimenting with potentially damaging software, aligns more closely with the hacker identity.
  • A participant mentions that being a good programmer does not guarantee acceptance in software development if one frequently makes mistakes or writes overly complex code.
  • There is a discussion about the balance between innovation and practicality in programming, with some emphasizing the importance of adhering to software development standards.
  • One participant humorously claims that being able to read object code faster than source code is a sign of being a hacker.

Areas of Agreement / Disagreement

Participants express differing views on what defines a hacker, with no consensus reached. Some believe that certain technical skills and experiences qualify one as a hacker, while others argue that these traits may simply reflect a deep understanding of computing without implying hacking behavior.

Contextual Notes

Participants reference personal experiences and anecdotes that illustrate their points, but these examples are subjective and may not universally apply to all individuals in the field.

saltydog
Science Advisor
Homework Helper
Messages
1,590
Reaction score
3
1. You know what a hex dump is.

2. You have a bookcase full of software manuals, hardware manuals, operating systems, PC video basics, Troubleshooting PCs, etc.

3. You've tried to break into a secure operating system like VMS.

4. You took an assembly language course and made an A.

5. You read the ACM Journal, the MSJ Journal, well, how about just PC Magazine?.

6. Your friend comes over with pirate software which states the disc drive will be erased if you load it and you tell him, "that's Ok, I can reload everything, let's try it".

7. You have the Windows XP Technical Reference Manual and actually read it.

8. You frequently lock up a sophisticated op. sys like Windows XP by running aberrant software you've written.

9. You've caused at least one serious problem before like messing up a disc drive, burning a circuit board, or destroying an entire database by messin' with the b-trees directly.

10. They no longer want you in software development.
 
Computer science news on Phys.org
1. I think you are desribing yourself (or not?)

2. This does not make you a |-|@X0Rz it means you know a lot about computers.
 
lol no it makes you a hacker, because i know how to do most of them, yet i have chosen not to
 
Hacking... VMS? Windows XP? Meh.

- Warren
 
saltydog said:
10. They no longer want you in software development.


No no no. It means you are an engineer, and probably suggested, and I quote, "tear down this whole crap you call a program and rewrite it from scratch in fortran 90"
 
eNathan said:
1. I think you are desribing yourself (or not?)

2. This does not make you a |-|@X0Rz it means you know a lot about computers.

Hello eNathan,

Just ment it as a parody nothing more. I really didn't load that pirate software; really, he wasn't a good enough friend for that. And the last one is also not true: if you're a really good programmer, then won't want to get rid of you even though you make mistakes and I made much more than those above. It's like the butcher story: you're not a good butcher unless you cut yourself every once in a while.
 
chroot said:
Hacking... VMS? Windows XP? Meh.

- Warren

Hello Warren. At the time, I was the Systems Manager. I didn't have a need to hack into it. I was taking a VMS assembly language course. When you load a program under VMS, your privilege level gets pushed to the stack. That's nice. Because having access to assembly level code you can access the stack. Soooooo... why not just "substitute" a higher privilege level there and thus when you return from the code, VMS will pop that higher level privildege. Hummmmm . . . They weren't born yesterday. It checks.

Oh yea . . . I made an A (I'm a bit head too).
 
About 10 years ago, my buddy was assembling a PC and he wired the power switch wrong, and every time he flicked the switch all the lights on that circuit went off :)
 
saltydog said:
Hello eNathan,

Just ment it as a parody nothing more. I really didn't load that pirate software; really, he wasn't a good enough friend for that. And the last one is also not true: if you're a really good programmer, then won't want to get rid of you even though you make mistakes and I made much more than those above. It's like the butcher story: you're not a good butcher unless you cut yourself every once in a while.

Some mistakes people will tolerate. However, if you always write (unintentionally) obfuscated code, or spend a lot of time optimizing the hell out of a function that only runs for two seconds every month anyway, or insist on writing everything in C because computer time is the most valuble thing in the world and we don't dare waste any of it, then there are a lot of people who won't want you in software development. Even if you are a good programmer.

Sadly, an obsession with speed and overly clever trickery can produce produce programmers who make those mistakes all the time.
 
  • #10
master_coda said:
Some mistakes people will tolerate. However, if you always write (unintentionally) obfuscated code, or spend a lot of time optimizing the hell out of a function that only runs for two seconds every month anyway, or insist on writing everything in C because computer time is the most valuble thing in the world and we don't dare waste any of it, then there are a lot of people who won't want you in software development. Even if you are a good programmer.


Yes Master_Coda. I think innovation and practicality are important: "We have a problem. How can you resolve it in a reasonable amount of time that meets our software development standards?". But you know, they have to have them first. I mean software standards. Here's another one: I began some time ago working for this "new" software company that didn't have any. Well, to make a long story short, I wrote the programming standards simultaneously with developing the code for the first project I worked on. . . sort of like that Echer picture of the hand drawing the hand . . .
 
  • #11
saltydog said:
Yes Master_Coda. I think innovation and practicality are important: "We have a problem. How can you resolve it in a reasonable amount of time that meets our software development standards?". But you know, they have to have them first. I mean software standards. Here's another one: I began some time ago working for this "new" software company that didn't have any. Well, to make a long story short, I wrote the programming standards simultaneously with developing the code for the first project I worked on. . . sort of like that Echer picture of the hand drawing the hand . . .

I'm not sure what that has to do with the comment I made; I just wanted to point out that just being a good programmer isn't enough to make people want to develop software with you. Everyone makes stupid mistakes now and then, but if being a hacker means you make them all the time, then it doesn't really matter how good you are.

Of course, everything in moderation; being a hacker isn't bad, it's just that some people take things too far.
 
  • #12
You are a hacker if you can read OCO faster than source code :biggrin:

OCO= object code only.