葱油酥饼的做法视频:如何成为一名黑客 （中英文）

作者：Eric Raymond
翻译  waterbird [AKA]


------什么是黑客?

Jargon File中对“黑客”一词给出了很多个定义，大部分定义都涉及高超的编程
技术，强烈的解决问题和克服限制的欲望。如果你想知道如何成为一名黑客，那么
好，只有两方面是重要的。（态度和技术）

  长久以来，存在一个专家级程序员和网络高手的共享文化社群，其历史可以追溯
到几十年前第一台分时共享的小型机和最早的ARPAnet实验时期。 这个文件的参与
者们创造了“黑客”这个词。 黑客们建起了Internet。黑客们使Unix操作系统成
为今天这个样子。黑客们搭起了Usenet。黑客们让WWW正常运转。如果你是这个文
化的一部分，如果你已经为它作了些贡献，而且圈内的其他人也知道你是谁并称你
为一个黑客，那么你就是一名黑客。

  黑客精神并不仅仅局限于软件黑客文化圈中。有些人同样以黑客态度对待其它事
情如电子和音乐---事实上，你可以在任何较高级别的科学和艺术中发现它。软件
黑客们识别出这些在其他领域同类并把他们也称作黑客---有人宣称黑客实际上是
独立于他们工作领域的。 但在本文中，我们将注意力集中在软件黑客的技术和态
度，以及发明了“黑客”一词的哪个共享文化传统之上。

  另外还有一群人，他们大声嚷嚷着自己是黑客，实际上他们却不是。他们是一些
蓄意破坏计算机和电话系统的人（多数是青春期的少年）。真正的黑客把这些人叫
做“骇客”(cracker)，并不屑与之为伍。多数真正的黑客认为骇客们是些不负责
任的懒家伙，还没什么大本事。专门以破坏别人安全为目的的行为并不能使你成
为一名黑客， 正如拿根铁丝能打开汽车并不能使你成为一个汽车工程师。不幸的
是，很多记者和作家往往错把“骇客”当成黑客；这种做法激怒真正的黑客。
 
  根本的区别是：黑客们建设，而骇客们破坏。

  如果你想成为一名黑客，继续读下去。如果你想做一个骇客，去读 alt.2600 
新闻组，并在发现你并不像自己想象的那么聪明的时候去坐5到10次监狱。 关于
骇客，我只想说这么多。

------黑客的态度

黑客们解决问题，建设事物，信仰自由和双向的帮助，所谓我为人人，人人为我。
要想被认为是一名黑客，你的行为必须显示出你已经具备了这种态度。要想做的好
象你具备这种态度，你就不得不真的具备这种态度。但是如果你想靠培养黑客态度
在黑客文化中得到承认，那就大错特错了。因为成为具备这些特质的这种人对你自
己非常重要，有助于你学习，并给你提供源源不断的活力。同所有有创造性的艺术
一样，成为大师的最有效方法就是模仿大师的精神---不是仅从理智上，更要从感
情上进行模仿。

 So，如果你想做一名黑客，请重复以下事情直到你相信它们：

1  这世界充满待解决的迷人问题。

做一名黑客有很多乐趣，但却是些要费很多气力方能得到的乐趣。 这些努力需要动力。
成功的运动员从健壮体魄，挑战自我极限中汲取动力。同样，做黑客，你必须
要有从解决问题，磨练技术，锻炼智力中得到基本的热望。如果你还不是这类人又
想做黑客，你就要设法成为这样的人。否则你会发现，你的黑客热情会被其他诱惑
无情地吞噬掉---如金钱、性和社会上的虚名。

（同样你必须对你自己的学习能力建立信心---相信尽管你对某问题所知不多，但
如果你一点一点地学习、试探，你最终会掌握并解决它。）

2. 一个问题不应该被解决两次

聪明的脑瓜是宝贵的，有限的资源。当这个世界还充满其他有待解决的有趣问题之
时，他们不应该被浪费在重新发明轮子这些事情上。 作为一名黑客，你必须相信
其他黑客的思考时间是宝贵的---因此共享信息，解决问题并发布结果给其他黑客
几乎是一种道义，这样其他人就可以去解决新问题而不是重复地对付旧问题。

(你不必认为你一定要把你的发明创造公布出去，但这样做的黑客是赢得大家尊敬
最多的人。卖些钱来给自己养家糊口，买房买车买计算机甚至发大财和黑客价值也
是相容的，只要你别忘记你还是个黑客。)

3. 无聊和乏味的工作是罪恶.

黑客们应该从来不会被愚蠢的重复性劳动所困扰，因为当这种事情发生时就意味着
他们没有在做只有他们才能做的事情---解决新问题。这样的浪费伤害每一个人。
因此，无聊和乏味的工作不仅仅是令人不舒服而已，它们是极大的犯罪。 要想做
的象个黑客，你必须完全相信这点并尽可能多地将乏味的工作自动化，不仅为你自
己，也为了其他人（尤其是其他黑客们）。

(对此有一个明显的例外。黑客们有时也做一些重复性的枯燥工作以进行“脑力休
息”，或是为了某个技巧，或是获得一些除此无法获得的经验。但这是他自己的选
择---有脑子的人不应该被迫做无聊的活儿。）


4 自由就是好

黑客们是天生的反权威主义者。任何能向你发命令的人会迫使你停止解决令你着迷
的问题，同时，按照权威的一般思路，他通常会给出一些极其愚昧的理由。因此，
不论何时何地，任何权威，只要他压迫你或其他黑客，就要和他斗到底。

(这并非说任何权力都不必要。儿童需要监护，罪犯也要被看管起来。 如果服从命
令得到某种东西比起其他方式得到它更节约时间，黑客会同意接受某种形式的权威
。但这是一个有限的、特意的交易；权力想要的那种个人服从不是你的给予，而是
无条件的服从。) 

权力喜爱审查和保密。他们不信任自愿的合作和信息共享---他们只喜欢由他们控
制的合作。因此，要想做的象个黑客，你得对审查、保密，以及使用武力或欺骗去
压迫人们的做法有一种本能的反感和敌意。


5. 态度不能替代能力

要做一名黑客，你必须培养起这些态度。但只具备这些态度并不能使你成为一名黑
客，就象这并不能使你成为一个运动健将和摇滚明星一样。成为一名黑客需要花费
智力，实践，奉献和辛苦。
因此，你必须学会不相信态度，并尊重各种各样的能力。黑客们不会为那些故意装
模做样的人浪费时间，但他们却非常尊重能力---尤其是做黑客的能力，不过任何
能力总归是好的。具备很少人才能掌握的技术方面的能力尤其为好，而具备那些涉
及脑力、技巧和聚精会神的能力为最好。

如果你尊敬能力，你会享受提高自己能力的乐趣---辛苦的工作和奉献会变成一种
高度娱乐而非贱役。  要想成为一名黑客，这一点非常重要。 


------基本黑客技术

黑客态度是重要的，但技术更加重要。态度无法替代技术，在你被别的黑客称为黑
客之前，有一套基本的技术你必须掌握。 这套基本技术随着新技术的出现和老技
术的过时也随时间在缓慢改变。例如，过去包括使用机器码编程，而知道最近才包
括了HTML语言。但现在明显包括以下技术：


1 学习如何编程

这当然是最基本的黑客技术。如果你还不会任何计算机语言，我建议你从Python开
始。它设计清晰，文档齐全，对初学者很合适。尽管是一门很好的初级语言，它不
仅仅只是个玩具。它非常强大，灵活，也适合做大型项目。

但是记住，如果你只会一门语言，你将不会达到黑客所要求的技术水平，甚至也不
能达到一个普通程序员的水平---你需要学会如何以一个通用的方法思考编程问题
，独立于任何语言。要做一名真正的黑客，你需要学会如何在几天内通过一些手册
，结合你现在所知，迅速掌握一门新语言。这意味着你应该学会几种不同的语言。 

如果要做一些重要的编程，你将不得不学习C语言，Unix的核心语言。其他对黑客
而言比较重要的语言包括Perl和LISP。 Perl很实用，值得一学；它被广泛用于活
动网页和系统管理，因此即便你从不用Perl写程序，至少也应该能读懂它。 LISP
 值得学习是因为当你最终掌握了它你会得到丰富的经验；这些经验使你在以后的
日子里成为一个更好的程序员，即使你实际上可能很少使用LISP本身。

当然，实际上你最好四种都会。 (Python, C, Perl, and LISP). 除了是最重要的
四种基本语言，它们还代表了四种非常不同的编程方法，每种都会让你受益非浅。
 

这里我无法完整地教会你如何编程---这是个复杂的活儿。但我可以告诉你，书本
和课程也无济于事。几乎所有最好的黑客都是自学成材的。真正能起作用的就是
去亲自读代码和写代码。

学习如何编程就象学习用自然语言写作一样。最好的做法是读一些大师的名著，
试着自己写点东西，再读些，再写点，又读些，又写点....如此往复，直到你达
到自己在范文中看到的简洁和力量。 

过去找到好的代码去读是困难的，因为很少有大型程序的可用源代码能让新手练
手。这种状况已经得到了很大的改善；现在有很多可用的开放源码软件，编程工
具和操作系统（全都有黑客写成）。这使我们自然地来到第二个话题...


2 得到一个开放源码的Unix并学会使用、运行它。

我假设你已经拥有了一台个人计算机或者有一个可用的（ 今天的孩子们真幸福 
:-) ）。新手们最基本的一步就是得到一份Linux或BSD-Unix，安装在个人计算机
上，并运行它。
当然，这世界上除了Unix还有其他操作系统。但它们都是以二进制形式发送的---
你无法读到它的源码，更不可能修改它。尝试在DOS或Windows的机器上学习黑客技
术，就象是在腿上绑了铁块去学跳舞。

除此之外，Unix还是Internet的操作系统。你可以不知道Unix而学会用Internet，
但不懂它你就无法成为一名Internet黑客。因为这个原因，今天的黑客文化在很大
程度上是以Unix为中心的。（这点并不总是真的，一些很早的黑客对此很不高兴，
但Unix和Internet之间的共生关系已是如此之强，甚至连微软也无可奈何) 

So，装一个Unix---我个人喜欢Linux，不过也有其他选择。（你也可以在同一台机
器上同时运行DOS,Windows和Linux）学会它。运行它。用它跟Internet对话。读它
的代码。试着去修改他。你会得到比微软操作系统上好的多的编程工具（包括C,
Lisp, Python, and Perl），你会得到乐趣，并将学到比你想象的更多知识。

关于学习Unix的更多信息，请看 The Loginataka. 

要得到Linux，请看： 哪里能得到 Linux.

3 学会如何使用WWW和写HTML

大多黑客文化建造的东西都在你看不见的地方发挥着作用，帮助工厂、办公室和大
学正常运转，表面上很难看到它对他人的生活的影响。Web是一个大大的例外。即
便政客也同意，这个巨大而耀眼的黑客玩具正在改变整个世界。单是这个原因（
还有许多其它的）， 你就需要学习如何掌握Web。

这并不是仅仅意味着如何使用浏览器（谁都会），而是要学会如何写HTML，Web的
标记语言。如果你不会编程，写HTML会教你一些有助于学习的思考习惯。因此，先
建起自己的主页。

但仅仅建一个主页也不能使你成为一名黑客。 Web里充满了各种网页。多数是无意
义的，零信息量垃圾。

要想有价值，你的网页必须有内容---必须有趣或对其它黑客有用。这样，我们来
到下一个话题....


------黑客文化中的地位


象大部分不涉及金钱的文化一样，黑客王国的运转靠声誉维护。你设法解决有趣的
问题，但它们到底多有趣，你的解法有多好，是要有那些和你具有同样技术水平的
人或比你更牛的人去评判的。

相应地，当你在玩黑客游戏时，你知道，你的分数要靠其他黑客对你的技术的评估
给出。（这就是为什么只有在其它黑客称你为黑客是，你才算得上是一名黑客）这
个事实常会被黑客是一项孤独的工作这一印象所减弱；它也会被另一个黑客文化的
禁忌所减弱（此禁忌的效力正在减弱但仍很强大）：拒绝承认自我或外部评估是一
个人的动力。

特别地，黑客王国被人类学家们称为一种精英文化。在这里你不是凭借你对别人的
统治来建立地位和名望，也不是靠美貌，或拥有其他人想要的东西，而是靠你的奉
献。尤其是奉献你的时间，你的才智和你的技术成果。

要获得其他黑客的尊敬，你可以做以下五种事情：
 

1. 写开放源码的软件

第一个（也是最基本和传统的）是写些被其他黑客认为有趣或有用的程序，并把程
序的原代码公布给大家共享。
（过去我们称之为“自由软件-free software”，但这却使很多不知free的精确含
义的人感到不解。现在我们很多人使用“开放源码-open source”这个词）

黑客王国里最受尊敬的大牛们是那些写了大型的、具有广泛用途的软件，并把它们
公布出去，使每人都在使用他的软件的人。



2. 帮助测试并修改开放源码的软件

黑客们也尊敬也那些使用、测试开放源码软件的人。在这个并非完美的世界上，我
们不可避免地要花大量软件开发的时间在测试和抓臭虫阶段。 这就是为什么任何
开放源码的作者稍加思考后都会告诉你好的beta测试员象红宝石一样珍贵。  (他
知道如何清楚描述出错症状，很好地定位错误，能忍受快速发布的软件中的bug，
愿意使用一些简单的诊断工具) 甚至他们中的一个能判断出哪个测试阶段是延长
的、令人精疲力尽的噩梦，哪个只是一个有益健康的玩意儿。 

如果你是个新手，试着找一个赶兴趣的正在开发的程序，作一个好的beta测试员。
从帮着测试，到帮着抓臭虫，到最后帮着改程序，你会不断进步。以后你写程序时
，会有别人来帮你，你就得到了你当初善举的回报。
 


3. 公布有用的信息

另一个好事是收集整理网页上有用有趣的信息或文档如FAQ。许多主要FAQ的维护者
和其他开放源码的作者一样受到大家的尊敬。


4. 帮助维护基础设施的运转

黑客文化是靠自愿者运转的。要使Internet能正常工作，就要有大量枯燥的工作不
得不去完成----管理mail list，newsgroup，维护大量文档，开发RFC和其它技术
标准等等。做这类事情的人会得到很多人的尊敬，因为每人都知道这些事情是耗时
耗力的苦役，不象编码那样好玩。做这些事情需要毅力。

5. 为黑客文化本身服务

最后，你可以为这个文化本身服务（例如象我这样，写一个“如何成为黑客”的初
级教程 :-) ）（hehe,象我这样把它翻成中文 :-) ） 这并非一定要在你已经在这
里呆了很久，精通所有以上4点，获得一定声誉后后才能去做。

黑客文化没有领袖。精确地说，它确实有些文化英雄和部落长者和历史学家和发言
人。若你在这圈内呆的够长，你或许成为其中之一。
记住：黑客们不相信他们的部落长者的自夸的炫耀，因此很明显地去追求这种名誉
是危险的。你必须具备基本的谦虚和优雅。 

------黑客和怪人(Nerd)的联系

同流行的传说相反，做一名黑客并不一定要你是个怪人。然而，很多黑客都是怪
人。做一个出世者有助于你集中精力进行更重要的事情，如思考和编程。
因此，很多黑客都愿意接受“怪人”这个标签，更有甚者愿意使用“傻子(geek)”
一词并自以为豪---这是宣布他们与主流社会不合作的声明。

如果你能集中足够的精力来做好黑客同时还能有正常的生活，这很好。今天作到这
一点比我在1970年代是个新手是要容易的多。今天主流文化对技术怪人要友善的多
。甚至有更多的人意识到黑客通常更富爱心，是块很好的做恋人和配偶的材料。 
更多信息见 Girl's Guide to Geek Guys. 

如果你因为生活上不如意而为做黑客而吸引，那也没什么---至少你不会分神了。
或许以后你会找到自己的另一半。



------风格的意义

重申一下，做一名黑客，你必须进入黑客精神之中。当你不在计算机边上时，你仍
然有很多事情可做。它们并不能替代真正的编程（没有什么能替代编程），但很多
黑客都那么做，并感到它们与黑客精神存在一种本质的关联。

阅读科幻小说。参加科幻小说讨论会。（一个很好的寻找黑客的场合）
研究禅宗，或练功习武。
练就一双精确的耳朵，学会鉴赏特别的音乐。学会玩某种乐器，或唱歌。
提高对双关语的鉴赏。
学会流畅地用母语写作。（令人惊讶的时，我所知道的所有最棒的黑客，都是很不
错的作家）

这些事情，你做的越多，你就越适合做黑客。至于为什么偏偏是这些事情，原因并
不很清楚，但它们都涉及到了左-右脑的综合技巧，这似乎是关键所在。（黑客们
既需要清晰的逻辑思维，有时也需要强烈的跳出逻辑之外的直觉） 

最后，还有一些不要去做的事情。

不要使用愚蠢的，过于哗众取宠的ID。
不要自称为网络崩客(punk) ，也不要对那些人浪费时间
不要寄出充满拼写和语法错误的email，或张贴错误百出的文章 

做以上的事情，会使大大损害你的声誉。黑客们个个记忆超群---你将需要数年的
时间让他们忘记你的愚蠢。

------其它资源

Peter Seebach为那些不知如何同黑客打交道的经理们维护了一个非常精彩的黑客
FAQ。
 
The Loginataka 有许多关于如何正确培养一个Unix黑客的态度的材料。

我也曾写过一篇“黑客文化简史”。

我还写过另一篇文章，“大教堂与集市”，解释了许多Linux和开放源码文化的运
做原理。我还在它的续集“开拓智力疆域”一文中有更直接的论述。

------FAQ（常问问题解答）

问：你会教我如何做黑客吗？

自从第一次发布此页，我每周都会得到一些请求，要我“教会他如何做黑客”；遗
憾的是，我没有足够的时间和精力来做这个；我自己的编程项目已经占用了我110%
的时间。
甚至即便我想教你也不可能，黑客基本上是一项需要你自行修炼的的态度和技术。
你会发现即使真正的黑客想帮助你，如果你乞求他们填鸭一样教你的话，你不会赢
得他们的尊敬。
首先去学习。显示你在尝试，你能靠自己去学习。然后再去向黑客们请教问题。


问：你会帮我“黑”掉一个站点吗？或者教我怎么黑它？

No. 任何在读完FAQ后还问此问题人，都是愚不可及的家伙，即使有时间我也不会
理睬。 任何发给我的此类mail都会被忽略或被痛斥。

问：哪里能找到真正的可以与之交流的黑客？

最佳办法是就近参加一个Unix或Linux的用户组，参加他们的会议。

问：我该先学哪种语言？

HTML, 如果你还不会的话. 
但它不是一个真正的编程语言。当你准备编程时，我建议你从 Python开始. 会有
很多人向你推荐Perl，它比Python还受欢迎，但却难学一些。

C 是非常重要的，但它却是最难学的。不要一开始就尝试学C。

问：开放源码的自由软件不会使程序员饿肚子吗？

这似乎不大可能---到目前，开放源码软件产业创造了而不是消灭了大量工作机会。
如果写一个程序比不写一个程序只是个纯粹经济上的收益的话，无论它是否免费，
只要它被完成，程序员都会从中得到回报。而且，无论软件是由多么的free的方法
开发的，对更新的软件应用的需求总是会有的。

问：我从何学起？哪里有免费的Unix?

本页的其他地方指向最常用的免费Unix。要做一名黑客，你需要自立自强，以及自
我教育的能力。
现在开始吧...... 

英文原版：

How To Become A Hacker
by Eric Steven Raymond

Table of Contents
Why This Document?
What Is a Hacker?
The Hacker Attitude
1. The world is full of fascinating problems waiting to be solved.
2. No problem should ever have to be solved twice.
3. Boredom and drudgery are evil.
4. Freedom is good.
5. Attitude is no substitute for competence.
Basic Hacking Skills
1. Learn how to program.
2. Get one of the open-source Unixes and learn to use and run it.
3. Learn how to use the World Wide Web and write HTML.
4. If you don't have functional English, learn it.
Status in the Hacker Culture
1. Write open-source software
2. Help test and debug open-source software
3. Publish useful information
4. Help keep the infrastructure working
5. Serve the hacker culture itself
The Hacker/Nerd Connection
Points For Style
Historical Note: Hacking, Open Source, and Free Software
Other Resources
Frequently Asked Questions
Why This Document?
As editor of the Jargon File and author of a few other well-known documents of similar nature, I often get email requests from enthusiastic network newbies asking (in effect) "how can I learn to be a wizardly hacker?". Back in 1996 I noticed that there didn't seem to be any other FAQs or web documents that addressed this vital question, so I started this one. A lot of hackers now consider it definitive, and I suppose that means it is. Still, I don't claim to be the exclusive authority on this topic; if you don't like what you read here, write your own.
If you are reading a snapshot of this document offline, the current version lives at http://catb.org/~esr/faqs/hacker-howto.html.
Note: there is a list of Frequently Asked Questions at the end of this document. Please read these—twice—before mailing me any questions about this document.
Numerous translations of this document are available: Arabic Bulgarian, Catalan, Chinese (Simplified), Danish, Dutch,Estonian, Farsi, Finnish, German, Greek Hebrew, Italian Japanese, Norwegian, Polish, Portuguese (Brazilian), RomanianRussian Spanish, Turkish, and Swedish. Note that since this document changes occasionally, they may be out of date to varying degrees.
The five-dots-in-nine-squares diagram that decorates this document is called a glider. It is a simple pattern with some surprising properties in a mathematical simulation called Life that has fascinated hackers for many years. I think it makes a good visual emblem for what hackers are like — abstract, at first a bit mysterious-seeming, but a gateway to a whole world with an intricate logic of its own. Read more about the glider emblem here.
What Is a Hacker?
The Jargon File contains a bunch of definitions of the term ‘hacker’, most having to do with technical adeptness and a delight in solving problems and overcoming limits. If you want to know how to become a hacker, though, only two are really relevant.
There is a community, a shared culture, of expert programmers and networking wizards that traces its history back through decades to the first time-sharing minicomputers and the earliest ARPAnet experiments. The members of this culture originated the term ‘hacker’. Hackers built the Internet. Hackers made the Unix operating system what it is today. Hackers run Usenet. Hackers make the World Wide Web work. If you are part of this culture, if you have contributed to it and other people in it know who you are and call you a hacker, you're a hacker.
The hacker mind-set is not confined to this software-hacker culture. There are people who apply the hacker attitude to other things, like electronics or music — actually, you can find it at the highest levels of any science or art. Software hackers recognize these kindred spirits elsewhere and may call them ‘hackers’ too — and some claim that the hacker nature is really independent of the particular medium the hacker works in. But in the rest of this document we will focus on the skills and attitudes of software hackers, and the traditions of the shared culture that originated the term ‘hacker’.
There is another group of people who loudly call themselves hackers, but aren't. These are people (mainly adolescent males) who get a kick out of breaking into computers and phreaking the phone system. Real hackers call these people ‘crackers’ and want nothing to do with them. Real hackers mostly think crackers are lazy, irresponsible, and not very bright, and object that being able to break security doesn't make you a hacker any more than being able to hotwire cars makes you an automotive engineer. Unfortunately, many journalists and writers have been fooled into using the word ‘hacker’ to describe crackers; this irritates real hackers no end.
The basic difference is this: hackers build things, crackers break them.
If you want to be a hacker, keep reading. If you want to be a cracker, go read the alt.2600 newsgroup and get ready to do five to ten in the slammer after finding out you aren't as smart as you think you are. And that's all I'm going to say about crackers.
The Hacker Attitude
1. The world is full of fascinating problems waiting to be solved.
2. No problem should ever have to be solved twice.
3. Boredom and drudgery are evil.
4. Freedom is good.
5. Attitude is no substitute for competence.
Hackers solve problems and build things, and they believe in freedom and voluntary mutual help. To be accepted as a hacker, you have to behave as though you have this kind of attitude yourself. And to behave as though you have the attitude, you have to really believe the attitude.
But if you think of cultivating hacker attitudes as just a way to gain acceptance in the culture, you'll miss the point. Becoming the kind of person who believes these things is important for you — for helping you learn and keeping you motivated. As with all creative arts, the most effective way to become a master is to imitate the mind-set of masters — not just intellectually but emotionally as well.
Or, as the following modern Zen poem has it:

    To follow the path:
    look to the master,
    follow the master,
    walk with the master,
    see through the master,
    become the master.
So, if you want to be a hacker, repeat the following things until you believe them:
1. The world is full of fascinating problems waiting to be solved.
Being a hacker is lots of fun, but it's a kind of fun that takes lots of effort. The effort takes motivation. Successful athletes get their motivation from a kind of physical delight in making their bodies perform, in pushing themselves past their own physical limits. Similarly, to be a hacker you have to get a basic thrill from solving problems, sharpening your skills, and exercising your intelligence.
If you aren't the kind of person that feels this way naturally, you'll need to become one in order to make it as a hacker. Otherwise you'll find your hacking energy is sapped by distractions like sex, money, and social approval.
(You also have to develop a kind of faith in your own learning capacity — a belief that even though you may not know all of what you need to solve a problem, if you tackle just a piece of it and learn from that, you'll learn enough to solve the next piece — and so on, until you're done.)
2. No problem should ever have to be solved twice.
Creative brains are a valuable, limited resource. They shouldn't be wasted on re-inventing the wheel when there are so many fascinating new problems waiting out there.
To behave like a hacker, you have to believe that the thinking time of other hackers is precious — so much so that it's almost a moral duty for you to share information, solve problems and then give the solutions away just so other hackers can solve new problems instead of having to perpetually re-address old ones.
Note, however, that "No problem should ever have to be solved twice." does not imply that you have to consider all existing solutions sacred, or that there is only one right solution to any given problem. Often, we learn a lot about the problem that we didn't know before by studying the first cut at a solution. It's OK, and often necessary, to decide that we can do better. What's not OK is artificial technical, legal, or institutional barriers (like closed-source code) that prevent a good solution from being re-used and force people to re-invent wheels.
(You don't have to believe that you're obligated to give all your creative product away, though the hackers that do are the ones that get most respect from other hackers. It's consistent with hacker values to sell enough of it to keep you in food and rent and computers. It's fine to use your hacking skills to support a family or even get rich, as long as you don't forget your loyalty to your art and your fellow hackers while doing it.)
3. Boredom and drudgery are evil.
Hackers (and creative people in general) should never be bored or have to drudge at stupid repetitive work, because when this happens it means they aren't doing what only they can do — solve new problems. This wastefulness hurts everybody. Therefore boredom and drudgery are not just unpleasant but actually evil.
To behave like a hacker, you have to believe this enough to want to automate away the boring bits as much as possible, not just for yourself but for everybody else (especially other hackers).
(There is one apparent exception to this. Hackers will sometimes do things that may seem repetitive or boring to an observer as a mind-clearing exercise, or in order to acquire a skill or have some particular kind of experience you can't have otherwise. But this is by choice — nobody who can think should ever be forced into a situation that bores them.)
4. Freedom is good.
Hackers are naturally anti-authoritarian. Anyone who can give you orders can stop you from solving whatever problem you're being fascinated by — and, given the way authoritarian minds work, will generally find some appallingly stupid reason to do so. So the authoritarian attitude has to be fought wherever you find it, lest it smother you and other hackers.
(This isn't the same as fighting all authority. Children need to be guided and criminals restrained. A hacker may agree to accept some kinds of authority in order to get something he wants more than the time he spends following orders. But that's a limited, conscious bargain; the kind of personal surrender authoritarians want is not on offer.)
Authoritarians thrive on censorship and secrecy. And they distrust voluntary cooperation and information-sharing — they only like ‘cooperation’ that they control. So to behave like a hacker, you have to develop an instinctive hostility to censorship, secrecy, and the use of force or deception to compel responsible adults. And you have to be willing to act on that belief.
5. Attitude is no substitute for competence.
To be a hacker, you have to develop some of these attitudes. But copping an attitude alone won't make you a hacker, any more than it will make you a champion athlete or a rock star. Becoming a hacker will take intelligence, practice, dedication, and hard work.
Therefore, you have to learn to distrust attitude and respect competence of every kind. Hackers won't let posers waste their time, but they worship competence — especially competence at hacking, but competence at anything is valued. Competence at demanding skills that few can master is especially good, and competence at demanding skills that involve mental acuteness, craft, and concentration is best.
If you revere competence, you'll enjoy developing it in yourself — the hard work and dedication will become a kind of intense play rather than drudgery. That attitude is vital to becoming a hacker.
Basic Hacking Skills
1. Learn how to program.
2. Get one of the open-source Unixes and learn to use and run it.
3. Learn how to use the World Wide Web and write HTML.
4. If you don't have functional English, learn it.
The hacker attitude is vital, but skills are even more vital. Attitude is no substitute for competence, and there's a certain basic toolkit of skills which you have to have before any hacker will dream of calling you one.
This toolkit changes slowly over time as technology creates new skills and makes old ones obsolete. For example, it used to include programming in machine language, and didn't until recently involve HTML. But right now it pretty clearly includes the following:
1. Learn how to program.
This, of course, is the fundamental hacking skill. If you don't know any computer languages, I recommend starting with Python. It is cleanly designed, well documented, and relatively kind to beginners. Despite being a good first language, it is not just a toy; it is very powerful and flexible and well suited for large projects. I have written a more detailedevaluation of Python. Good tutorials are available at the Python web site.
I used to recommend Java as a good language to learn early, but this critique has changed my mind (search for “The Pitfalls of Java as a First Programming Language” within it). A hacker cannot, as they devastatingly put it “approach problem-solving like a plumber in a hardware store”; you have to know what the components actually do. Now I think it is probably best to learn C and Lisp first, then Java.
There is perhaps a more general point here. If a language does too much for you, it may be simultaneously a good tool for production and a bad one for learning. It's not only languages that have this problem; web application frameworks like RubyOnRails, CakePHP, Django may make it too easy to reach a superficial sort of understanding that will leave you without resources when you have to tackle a hard problem, or even just debug the solution to an easy one.
If you get into serious programming, you will have to learn C, the core language of Unix. C++ is very closely related to C; if you know one, learning the other will not be difficult. Neither language is a good one to try learning as your first, however. And, actually, the more you can avoid programming in C the more productive you will be.
C is very efficient, and very sparing of your machine's resources. Unfortunately, C gets that efficiency by requiring you to do a lot of low-level management of resources (like memory) by hand. All that low-level code is complex and bug-prone, and will soak up huge amounts of your time on debugging. With today's machines as powerful as they are, this is usually a bad tradeoff — it's smarter to use a language that uses the machine's time less efficiently, but your time much moreefficiently. Thus, Python.
Other languages of particular importance to hackers include Perl and LISP. Perl is worth learning for practical reasons; it's very widely used for active web pages and system administration, so that even if you never write Perl you should learn to read it. Many people use Perl in the way I suggest you should use Python, to avoid C programming on jobs that don't require C's machine efficiency. You will need to be able to understand their code.
LISP is worth learning for a different reason — the profound enlightenment experience you will have when you finally get it. That experience will make you a better programmer for the rest of your days, even if you never actually use LISP itself a lot. (You can get some beginning experience with LISP fairly easily by writing and modifying editing modes for the Emacs text editor, or Script-Fu plugins for the GIMP.)
It's best, actually, to learn all five of Python, C/C++, Java, Perl, and LISP. Besides being the most important hacking languages, they represent very different approaches to programming, and each will educate you in valuable ways.
But be aware that you won't reach the skill level of a hacker or even merely a programmer simply by accumulating languages — you need to learn how to think about programming problems in a general way, independent of any one language. To be a real hacker, you need to get to the point where you can learn a new language in days by relating what's in the manual to what you already know. This means you should learn several very different languages.
I can't give complete instructions on how to learn to program here — it's a complex skill. But I can tell you that books and courses won't do it — many, maybe most of the best hackers are self-taught. You can learn language features — bits of knowledge — from books, but the mind-set that makes that knowledge into living skill can be learned only by practice and apprenticeship. What will do it is (a) reading code and (b) writing code.
Peter Norvig, who is one of Google's top hackers and the co-author of the most widely used textbook on AI, has written an excellent essay called Teach Yourself Programming in Ten Years. His "recipe for programming success" is worth careful attention.
Learning to program is like learning to write good natural language. The best way to do it is to read some stuff written by masters of the form, write some things yourself, read a lot more, write a little more, read a lot more, write some more ... and repeat until your writing begins to develop the kind of strength and economy you see in your models.
Finding good code to read used to be hard, because there were few large programs available in source for fledgeling hackers to read and tinker with. This has changed dramatically; open-source software, programming tools, and operating systems (all built by hackers) are now widely available. Which brings me neatly to our next topic...
2. Get one of the open-source Unixes and learn to use and run it.
I'll assume you have a personal computer or can get access to one. (Take a moment to appreciate how much that means. The hacker culture originally evolved back when computers were so expensive that individuals could not own them.) The single most important step any newbie can take toward acquiring hacker skills is to get a copy of Linux or one of the BSD-Unixes or OpenSolaris, install it on a personal machine, and run it.
Yes, there are other operating systems in the world besides Unix. But they're distributed in binary — you can't read the code, and you can't modify it. Trying to learn to hack on a Microsoft Windows machine or under any other closed-source system is like trying to learn to dance while wearing a body cast.
Under Mac OS X it's possible, but only part of the system is open source — you're likely to hit a lot of walls, and you have to be careful not to develop the bad habit of depending on Apple's proprietary code. If you concentrate on the Unix under the hood you can learn some useful things.
Unix is the operating system of the Internet. While you can learn to use the Internet without knowing Unix, you can't be an Internet hacker without understanding Unix. For this reason, the hacker culture today is pretty strongly Unix-centered. (This wasn't always true, and some old-time hackers still aren't happy about it, but the symbiosis between Unix and the Internet has become strong enough that even Microsoft's muscle doesn't seem able to seriously dent it.)
So, bring up a Unix — I like Linux myself but there are other ways (and yes, you can run both Linux and Microsoft Windows on the same machine). Learn it. Run it. Tinker with it. Talk to the Internet with it. Read the code. Modify the code. You'll get better programming tools (including C, LISP, Python, and Perl) than any Microsoft operating system can dream of hosting, you'll have fun, and you'll soak up more knowledge than you realize you're learning until you look back on it as a master hacker.
For more about learning Unix, see The Loginataka. You might also want to have a look at The Art Of Unix Programming.
To get your hands on a Linux, see the Linux Online! site; you can download from there or (better idea) find a local Linux user group to help you with installation.
During the first ten years of this HOWTO's life, I reported that from a new user's point of view, all Linux distributions are almost equivalent. But in 2006-2007, an actual best choice emerged: Ubuntu. While other distros have their own areas of strength, Ubuntu is far and away the most accessible to Linux newbies.
You can find BSD Unix help and resources at www.bsd.org.
A good way to dip your toes in the water is to boot up what Linux fans call a live CD, a distribution that runs entirely off a CD without having to modify your hard disk. This will be slow, because CDs are slow, but it's a way to get a look at the possibilities without having to do anything drastic.
I have written a primer on the basics of Unix and the Internet.
I used to recommend against installing either Linux or BSD as a solo project if you're a newbie. Nowadays the installers have gotten good enough that doing it entirely on your own is possible, even for a newbie. Nevertheless, I still recommend making contact with your local Linux user's group and asking for help. It can't hurt, and may smooth the process.
3. Learn how to use the World Wide Web and write HTML.
Most of the things the hacker culture has built do their work out of sight, helping run factories and offices and universities without any obvious impact on how non-hackers live. The Web is the one big exception, the huge shiny hacker toy that even politicians admit has changed the world. For this reason alone (and a lot of other good ones as well) you need to learn how to work the Web.
This doesn't just mean learning how to drive a browser (anyone can do that), but learning how to write HTML, the Web's markup language. If you don't know how to program, writing HTML will teach you some mental habits that will help you learn. So build a home page. Try to stick to XHTML, which is a cleaner language than classic HTML. (There are good beginner tutorials on the Web; here's one.)
But just having a home page isn't anywhere near good enough to make you a hacker. The Web is full of home pages. Most of them are pointless, zero-content sludge — very snazzy-looking sludge, mind you, but sludge all the same (for more on this see The HTML Hell Page).
To be worthwhile, your page must have content — it must be interesting and/or useful to other hackers. And that brings us to the next topic...
4. If you don't have functional English, learn it.
As an American and native English-speaker myself, I have previously been reluctant to suggest this, lest it be taken as a sort of cultural imperialism. But several native speakers of other languages have urged me to point out that English is the working language of the hacker culture and the Internet, and that you will need to know it to function in the hacker community.
Back around 1991 I learned that many hackers who have English as a second language use it in technical discussions even when they share a birth tongue; it was reported to me at the time that English has a richer technical vocabulary than any other language and is therefore simply a better tool for the job. For similar reasons, translations of technical books written in English are often unsatisfactory (when they get done at all).
Linus Torvalds, a Finn, comments his code in English (it apparently never occurred to him to do otherwise). His fluency in English has been an important factor in his ability to recruit a worldwide community of developers for Linux. It's an example worth following.
Being a native English-speaker does not guarantee that you have language skills good enough to function as a hacker. If your writing is semi-literate, ungrammatical, and riddled with misspellings, many hackers (including myself) will tend to ignore you. While sloppy writing does not invariably mean sloppy thinking, we've generally found the correlation to be strong — and we have no use for sloppy thinkers. If you can't yet write competently, learn to.
Status in the Hacker Culture
1. Write open-source software
2. Help test and debug open-source software
3. Publish useful information
4. Help keep the infrastructure working
5. Serve the hacker culture itself
Like most cultures without a money economy, hackerdom runs on reputation. You're trying to solve interesting problems, but how interesting they are, and whether your solutions are really good, is something that only your technical peers or superiors are normally equipped to judge.
Accordingly, when you play the hacker game, you learn to keep score primarily by what other hackers think of your skill (this is why you aren't really a hacker until other hackers consistently call you one). This fact is obscured by the image of hacking as solitary work; also by a hacker-cultural taboo (gradually decaying since the late 1990s but still potent) against admitting that ego or external validation are involved in one's motivation at all.
Specifically, hackerdom is what anthropologists call a gift culture. You gain status and reputation in it not by dominating other people, nor by being beautiful, nor by having things other people want, but rather by giving things away. Specifically, by giving away your time, your creativity, and the results of your skill.
There are basically five kinds of things you can do to be respected by hackers:
1. Write open-source software
The first (the most central and most traditional) is to write programs that other hackers think are fun or useful, and give the program sources away to the whole hacker culture to use.
(We used to call these works “free software”, but this confused too many people who weren't sure exactly what “free” was supposed to mean. Most of us now prefer the term “open-source” software).
Hackerdom's most revered demigods are people who have written large, capable programs that met a widespread need and given them away, so that now everyone uses them.
But there's a bit of a fine historical point here. While hackers have always looked up to the open-source developers among them as our community's hardest core, before the mid-1990s most hackers most of the time worked on closed source. This was still true when I wrote the first version of this HOWTO in 1996; it took the mainstreaming of open-source software after 1997 to change things. Today, "the hacker community" and "open-source developers" are two descriptions for what is essentially the same culture and population — but it is worth remembering that this was not always so. (For more on this, see the section called “Historical Note: Hacking, Open Source, and Free Software”.)
2. Help test and debug open-source software
They also serve who stand and debug open-source software. In this imperfect world, we will inevitably spend most of our software development time in the debugging phase. That's why any open-source author who's thinking will tell you that good beta-testers (who know how to describe symptoms clearly, localize problems well, can tolerate bugs in a quickie release, and are willing to apply a few simple diagnostic routines) are worth their weight in rubies. Even one of these can make the difference between a debugging phase that's a protracted, exhausting nightmare and one that's merely a salutary nuisance.
If you're a newbie, try to find a program under development that you're interested in and be a good beta-tester. There's a natural progression from helping test programs to helping debug them to helping modify them. You'll learn a lot this way, and generate good karma with people who will help you later on.
3. Publish useful information
Another good thing is to collect and filter useful and interesting information into web pages or documents like Frequently Asked Questions (FAQ) lists, and make those generally available.
Maintainers of major technical FAQs get almost as much respect as open-source authors.
4. Help keep the infrastructure working
The hacker culture (and the engineering development of the Internet, for that matter) is run by volunteers. There's a lot of necessary but unglamorous work that needs done to keep it going — administering mailing lists, moderating newsgroups, maintaining large software archive sites, developing RFCs and other technical standards.
People who do this sort of thing well get a lot of respect, because everybody knows these jobs are huge time sinks and not as much fun as playing with code. Doing them shows dedication.
5. Serve the hacker culture itself
Finally, you can serve and propagate the culture itself (by, for example, writing an accurate primer on how to become a hacker :-)). This is not something you'll be positioned to do until you've been around for while and become well-known for one of the first four things.
The hacker culture doesn't have leaders, exactly, but it does have culture heroes and tribal elders and historians and spokespeople. When you've been in the trenches long enough, you may grow into one of these. Beware: hackers distrust blatant ego in their tribal elders, so visibly reaching for this kind of fame is dangerous. Rather than striving for it, you have to sort of position yourself so it drops in your lap, and then be modest and gracious about your status.
The Hacker/Nerd Connection
Contrary to popular myth, you don't have to be a nerd to be a hacker. It does help, however, and many hackers are in fact nerds. Being something of a social outcast helps you stay concentrated on the really important things, like thinking and hacking.
For this reason, many hackers have adopted the label ‘geek’ as a badge of pride — it's a way of declaring their independence from normal social expectations (as well as a fondness for other things like science fiction and strategy games that often go with being a hacker). The term 'nerd' used to be used this way back in the 1990s, back when 'nerd' was a mild pejorative and 'geek' a rather harsher one; sometime after 2000 they switched places, at least in U.S. popular culture, and there is now even a significant geek-pride culture among people who aren't techies.
If you can manage to concentrate enough on hacking to be good at it and still have a life, that's fine. This is a lot easier today than it was when I was a newbie in the 1970s; mainstream culture is much friendlier to techno-nerds now. There are even growing numbers of people who realize that hackers are often high-quality lover and spouse material.
If you're attracted to hacking because you don't have a life, that's OK too — at least you won't have trouble concentrating. Maybe you'll get a life later on.
Points For Style
Again, to be a hacker, you have to enter the hacker mindset. There are some things you can do when you're not at a computer that seem to help. They're not substitutes for hacking (nothing is) but many hackers do them, and feel that they connect in some basic way with the essence of hacking.
Learn to write your native language well. Though it's a common stereotype that programmers can't write, a surprising number of hackers (including all the most accomplished ones I know of) are very able writers.
Read science fiction. Go to science fiction conventions (a good way to meet hackers and proto-hackers).
Train in a martial-arts form. The kind of mental discipline required for martial arts seems to be similar in important ways to what hackers do. The most popular forms among hackers are definitely Asian empty-hand arts such as Tae Kwon Do, various forms of Karate, Kung Fu, Aikido, or Ju Jitsu. Western fencing and Asian sword arts also have visible followings. In places where it's legal, pistol shooting has been rising in popularity since the late 1990s. The most hackerly martial arts are those which emphasize mental discipline, relaxed awareness, and control, rather than raw strength, athleticism, or physical toughness.
Study an actual meditation discipline. The perennial favorite among hackers is Zen (importantly, it is possible to benefit from Zen without acquiring a religion or discarding one you already have). Other styles may work as well, but be careful to choose one that doesn't require you to believe crazy things.
Develop an analytical ear for music. Learn to appreciate peculiar kinds of music. Learn to play some musical instrument well, or how to sing.
Develop your appreciation of puns and wordplay.
The more of these things you already do, the more likely it is that you are natural hacker material. Why these things in particular is not completely clear, but they're connected with a mix of left- and right-brain skills that seems to be important; hackers need to be able to both reason logically and step outside the apparent logic of a problem at a moment's notice.
Work as intensely as you play and play as intensely as you work. For true hackers, the boundaries between "play", "work", "science" and "art" all tend to disappear, or to merge into a high-level creative playfulness. Also, don't be content with a narrow range of skills. Though most hackers self-describe as programmers, they are very likely to be more than competent in several related skills — system administration, web design, and PC hardware troubleshooting are common ones. A hacker who's a system administrator, on the other hand, is likely to be quite skilled at script programming and web design. Hackers don't do things by halves; if they invest in a skill at all, they tend to get very good at it.
Finally, a few things not to do.
Don't use a silly, grandiose user ID or screen name.
Don't get in flame wars on Usenet (or anywhere else).
Don't call yourself a ‘cyberpunk’, and don't waste your time on anybody who does.
Don't post or email writing that's full of spelling errors and bad grammar.
The only reputation you'll make doing any of these things is as a twit. Hackers have long memories — it could take you years to live your early blunders down enough to be accepted.
The problem with screen names or handles deserves some amplification. Concealing your identity behind a handle is a juvenile and silly behavior characteristic of crackers, warez d00dz, and other lower life forms. Hackers don't do this; they're proud of what they do and want it associated with their real names. So if you have a handle, drop it. In the hacker culture it will only mark you as a loser.
Historical Note: Hacking, Open Source, and Free Software
When I originally wrote this how-to in late 1996, some of the conditions around it were very different from the way they look today. A few words about these changes may help clarify matters for people who are confused about the relationship of open source, free software, and Linux to the hacker community. If you are not curious about this, you can skip straight to the FAQ and bibliography from here.
The hacker ethos and community as I have described it here long predates the emergence of Linux after 1990; I first became involved with it around 1976, and, its roots are readily traceable back to the early 1960s. But before Linux, most hacking was done on either proprietary operating systems or a handful of quasi-experimental homegrown systems like MIT's ITS that were never deployed outside of their original academic niches. While there had been some earlier (pre-Linux) attempts to change this situation, their impact was at best very marginal and confined to communities of dedicated true believers which were tiny minorities even within the hacker community, let alone with respect to the larger world of software in general.
What is now called "open source" goes back as far as the hacker community does, but until 1985 it was an unnamed folk practice rather than a conscious movement with theories and manifestos attached to it. This prehistory ended when, in 1985, arch-hacker Richard Stallman ("RMS") tried to give it a name — "free software". But his act of naming was also an act of claiming; he attached ideological baggage to the "free software" label which much of the existing hacker community never accepted. As a result, the "free software" label was loudly rejected by a substantial minority of the hacker community (especially among those associated with BSD Unix), and used with serious but silent reservations by a majority of the remainder (including myself).
Despite these reservations, RMS's claim to define and lead the hacker community under the "free software" banner broadly held until the mid-1990s. It was seriously challenged only by the rise of Linux. Linux gave open-source development a natural home. Many projects issued under terms we would now call open-source migrated from proprietary Unixes to Linux. The community around Linux grew explosively, becoming far larger and more heterogenous than the pre-Linux hacker culture. RMS determinedly attempted to co-opt all this activity into his "free software" movement, but was thwarted by both the exploding diversity of the Linux community and the public skepticism of its founder, Linus Torvalds. Torvalds continued to use the term "free software" for lack of any alternative, but publicly rejected RMS's ideological baggage. Many younger hackers followed suit.
In 1996, when I first published this Hacker HOWTO, the hacker community was rapidly reorganizing around Linux and a handful of other open-source operating systems (notably those descended from BSD Unix). Community memory of the fact that most of us had spent decades developing closed-source software on closed-source operating systems had not yet begun to fade, but that fact was already beginning to seem like part of a dead past; hackers were, increasingly, defining themselves as hackers by their attachments to open-source projects such as Linux or Apache.
The term "open source", however, had not yet emerged; it would not do so until early 1998. When it did, most of hacker community adopted it within the following six months; the exceptions were a minority ideologically attached to the term "free software". Since 1998, and especially after about 2003, the identification of 'hacking' with 'open-source (and free software) development' has become extremely close. Today there is little point in attempting to distinguish between these categories, and it seems unlikely that will change in the future.
It is worth remembering, however, that this was not always so.
Other Resources
Paul Graham has written an essay called Great Hackers, and another on Undergraduation, in which he speaks much wisdom.
There is a document called How To Be A Programmer that is an excellent complement to this one. It has valuable advice not just about coding and skillsets, but about how to function on a programming team.
I have also written A Brief History Of Hackerdom.
I have written a paper, The Cathedral and the Bazaar, which explains a lot about how the Linux and open-source cultures work. I have addressed this topic even more directly in its sequel Homesteading the Noosphere.
Rick Moen has written an excellent document on how to run a Linux user group.
Rick Moen and I have collaborated on another document on How To Ask Smart Questions. This will help you seek assistance in a way that makes it more likely that you will actually get it.
If you need instruction in the basics of how personal computers, Unix, and the Internet work, see The Unix and Internet Fundamentals HOWTO.
When you release software or write patches for software, try to follow the guidelines in the Software Release Practice HOWTO.
If you enjoyed the Zen poem, you might also like Rootless Root: The Unix Koans of Master Foo.
Frequently Asked Questions
Q: How do I tell if I am already a hacker?
Q: Will you teach me how to hack?
Q: How can I get started, then?
Q: When do you have to start? Is it too late for me to learn?
Q: How long will it take me to learn to hack?
Q: Is Visual Basic a good language to start with?
Q: Would you help me to crack a system, or teach me how to crack?
Q: How can I get the password for someone else's account?
Q: How can I break into/read/monitor someone else's email?
Q: How can I steal channel op privileges on IRC?
Q: I've been cracked. Will you help me fend off further attacks?
Q: I'm having problems with my Windows software. Will you help me?
Q: Where can I find some real hackers to talk with?
Q: Can you recommend useful books about hacking-related subjects?
Q: Do I need to be good at math to become a hacker?
Q: What language should I learn first?
Q: What kind of hardware do I need?
Q: I want to contribute. Can you help me pick a problem to work on?
Q: Do I need to hate and bash Microsoft?
Q: But won't open-source software leave programmers unable to make a living?
Q: Where can I get a free Unix?
Q:
How do I tell if I am already a hacker?
A:
Ask yourself the following three questions:
Do you speak code, fluently?
Do you identify with the goals and values of the hacker community?
Has a well-established member of the hacker community ever called you a hacker?
If you can answer yes to all three of these questions, you are already a hacker. No two alone are sufficient.
The first test is about skills. You probably pass it if you have the minimum technical skills described earlier in this document. You blow right through it if you have had a substantial amount of code accepted by an open-source development project.
The second test is about attitude. If the five principles of the hacker mindset seemed obvious to you, more like a description of the way you already live than anything novel, you are already halfway to passing it. That's the inward half; the other, outward half is the degree to which you identify with the hacker community's long-term projects.
Here is an incomplete but indicative list of some of those projects: Does it matter to you that Linux improve and spread? Are you passionate about software freedom? Hostile to monopolies? Do you act on the belief that computers can be instruments of empowerment that make the world a richer and more humane place?
But a note of caution is in order here. The hacker community has some specific, primarily defensive political interests — two of them are defending free-speech rights and fending off "intellectual-property" power grabs that would make open source illegal. Some of those long-term projects are civil-liberties organizations like the Electronic Frontier Foundation, and the outward attitude properly includes support of them. But beyond that, most hackers view attempts to systematize the hacker attitude into an explicit political program with suspicion; we've learned, the hard way, that these attempts are divisive and distracting. If someone tries to recruit you to march on your capitol in the name of the hacker attitude, they've missed the point. The right response is probably “Shut up and show them the code.”
The third test has a tricky element of recursiveness about it. I observed in the section called “What Is a Hacker?”that being a hacker is partly a matter of belonging to a particular subculture or social network with a shared history, an inside and an outside. In the far past, hackers were a much less cohesive and self-aware group than they are today. But the importance of the social-network aspect has increased over the last thirty years as the Internet has made connections with the core of the hacker subculture easier to develop and maintain. One easy behavioral index of the change is that, in this century, we have our own T-shirts.
Sociologists, who study networks like those of the hacker culture under the general rubric of "invisible colleges", have noted that one characteristic of such networks is that they have gatekeepers — core members with the social authority to endorse new members into the network. Because the "invisible college" that is hacker culture is a loose and informal one, the role of gatekeeper is informal too. But one thing that all hackers understand in their bones is that not every hacker is a gatekeeper. Gatekeepers have to have a certain degree of seniority and accomplishment before they can bestow the title. How much is hard to quantify, but every hacker knows it when they see it.
Q:
Will you teach me how to hack?
A:
Since first publishing this page, I've gotten several requests a week (often several a day) from people to "teach me all about hacking". Unfortunately, I don't have the time or energy to do this; my own hacking projects, and working as an open-source advocate, take up 110% of my time.
Even if I did, hacking is an attitude and skill you basically have to teach yourself. You'll find that while real hackers want to help you, they won't respect you if you beg to be spoon-fed everything they know.
Learn a few things first. Show that you're trying, that you're capable of learning on your own. Then go to the hackers you meet with specific questions.
If you do email a hacker asking for advice, here are two things to know up front. First, we've found that people who are lazy or careless in their writing are usually too lazy and careless in their thinking to make good hackers — so take care to spell correctly, and use good grammar and punctuation, otherwise you'll probably be ignored. Secondly, don'tdare ask for a reply to an ISP account that's different from the account you're sending from; we find people who do that are usually thieves using stolen accounts, and we have no interest in rewarding or assisting thievery.
Q:
How can I get started, then?
A:
The best way for you to get started would probably be to go to a LUG (Linux user group) meeting. You can find such groups on the LDP General Linux Information Page; there is probably one near you, possibly associated with a college or university. LUG members will probably give you a Linux if you ask, and will certainly help you install one and get started.
Q:
When do you have to start? Is it too late for me to learn?
A:
Any age at which you are motivated to start is a good age. Most people seem to get interested between ages 15 and 20, but I know of exceptions in both directions.
Q:
How long will it take me to learn to hack?
A:
That depends on how talented you are and how hard you work at it. Most people who try can acquire a respectable skill set in eighteen months to two years, if they concentrate. Don't think it ends there, though; in hacking (as in many other fields) it takes about ten years to achieve mastery. And if you are a real hacker, you will spend the rest of your life learning and perfecting your craft.
Q:
Is Visual Basic a good language to start with?
A:
If you're asking this question, it almost certainly means you're thinking about trying to hack under Microsoft Windows. This is a bad idea in itself. When I compared trying to learn to hack under Windows to trying to learn to dance while wearing a body cast, I wasn't kidding. Don't go there. It's ugly, and it never stops being ugly.
There is a specific problem with Visual Basic; mainly that it's not portable. Though there is a prototype open-source implementations of Visual Basic, the applicable ECMA standards don't cover more than a small set of its programming interfaces. On Windows most of its library support is proprietary to a single vendor (Microsoft); if you aren'textremely careful about which features you use — more careful than any newbie is really capable of being — you'll end up locked into only those platforms Microsoft chooses to support. If you're starting on a Unix, much better languages with better libraries are available. Python, for example.
Also, like other Basics, Visual Basic is a poorly-designed language that will teach you bad programming habits. No,don't ask me to describe them in detail; that explanation would fill a book. Learn a well-designed language instead.
One of those bad habits is becoming dependent on a single vendor's libraries, widgets, and development tools. In general, any language that isn't fully supported under at least Linux or one of the BSDs, and/or at least three different vendors' operating systems, is a poor one to learn to hack in.
Q:
Would you help me to crack a system, or teach me how to crack?
A:
No. Anyone who can still ask such a question after reading this FAQ is too stupid to be educable even if I had the time for tutoring. Any emailed requests of this kind that I get will be ignored or answered with extreme rudeness.
Q:
How can I get the password for someone else's account?
A:
This is cracking. Go away, idiot.
Q:
How can I break into/read/monitor someone else's email?
A:
This is cracking. Get lost, moron.
Q:
How can I steal channel op privileges on IRC?
A:
This is cracking. Begone, cretin.
Q:
I've been cracked. Will you help me fend off further attacks?
A:
No. Every time I've been asked this question so far, it's been from some poor sap running Microsoft Windows. It is not possible to effectively secure Windows systems against crack attacks; the code and architecture simply have too many flaws, which makes securing Windows like trying to bail out a boat with a sieve. The only reliable prevention starts with switching to Linux or some other operating system that is designed to at least be capable of security.
Q:
I'm having problems with my Windows software. Will you help me?
A:
Yes. Go to a DOS prompt and type "format c:". Any problems you are experiencing will cease within a few minutes.
Q:
Where can I find some real hackers to talk with?
A:
The best way is to find a Unix or Linux user's group local to you and go to their meetings (you can find links to several lists of user groups on the LDP site at ibiblio).
(I used to say here that you wouldn't find any real hackers on IRC, but I'm given to understand this is changing. Apparently some real hacker communities, attached to things like GIMP and Perl, have IRC channels now.)
Q:
Can you recommend useful books about hacking-related subjects?
A:
I maintain a Linux Reading List HOWTO that you may find helpful. The Loginataka may also be interesting.
For an introduction to Python, see the tutorial on the Python site.
Q:
Do I need to be good at math to become a hacker?
A:
No. Hacking uses very little formal mathematics or arithmetic. In particular, you won't usually need trigonometry, calculus or analysis (there are exceptions to this in a handful of specific application areas like 3-D computer graphics). Knowing some formal logic and Boolean algebra is good. Some grounding in finite mathematics (including finite-set theory, combinatorics, and graph theory) can be helpful.
Much more importantly: you need to be able to think logically and follow chains of exact reasoning, the way mathematicians do. While the content of most mathematics won't help you, you will need the discipline and intelligence to handle mathematics. If you lack the intelligence, there is little hope for you as a hacker; if you lack the discipline, you'd better grow it.
I think a good way to find out if you have what it takes is to pick up a copy of Raymond Smullyan's book What Is The Name Of This Book?. Smullyan's playful logical conundrums are very much in the hacker spirit. Being able to solve them is a good sign; enjoying solving them is an even better one.
Q:
What language should I learn first?
A:
XHTML (the latest dialect of HTML) if you don't already know it. There are a lot of glossy, hype-intensive bad HTML books out there, and distressingly few good ones. The one I like best is HTML: The Definitive Guide.
But HTML is not a full programming language. When you're ready to start programming, I would recommend starting withPython. You will hear a lot of people recommending Perl, and Perl is still more popular than Python, but it's harder to learn and (in my opinion) less well designed.
C is really important, but it's also much more difficult than either Python or Perl. Don't try to learn it first.
Windows users, do not settle for Visual Basic. It will teach you bad habits, and it's not portable off Windows. Avoid.
Q:
What kind of hardware do I need?
A:
It used to be that personal computers were rather underpowered and memory-poor, enough so that they placed artificial limits on a hacker's learning process. This stopped being true in the mid-1990s; any machine from an Intel 486DX50 up is more than powerful enough for development work, X, and Internet communications, and the smallest disks you can buy today are plenty big enough.
The important thing in choosing a machine on which to learn is whether its hardware is Linux-compatible (or BSD-compatible, should you choose to go that route). Again, this will be true for almost all modern machines. The only really sticky areas are modems and wireless cards; some machines have Windows-specific hardware that won't work with Linux.
There's a FAQ on hardware compatibility; the latest version is here.
Q:
I want to contribute. Can you help me pick a problem to work on?
A:
No, because I don't know your talents or interests. You have to be self-motivated or you won't stick, which is why having other people choose your direction almost never works.
Try this. Watch the project announcements scroll by on Freshmeat for a few days. When you see one that makes you think "Cool! I'd like to work on that!", join it.
Q:
Do I need to hate and bash Microsoft?
A:
No, you don't. Not that Microsoft isn't loathsome, but there was a hacker culture long before Microsoft and there will still be one long after Microsoft is history. Any energy you spend hating Microsoft would be better spent on loving your craft. Write good code — that will bash Microsoft quite sufficiently without polluting your karma.
Q:
But won't open-source software leave programmers unable to make a living?
A:
This seems unlikely — so far, the open-source software industry seems to be creating jobs rather than taking them away. If having a program written is a net economic gain over not having it written, a programmer will get paid whether or not the program is going to be open-source after it's done. And, no matter how much "free" software gets written, there always seems to be more demand for new and customized applications. I've written more about this at the Open Sourcepages.
Q:
Where can I get a free Unix?
A:
If you don't have a Unix installed on your machine yet, elsewhere on this page I include pointers to where to get the most commonly used free Unix. To be a hacker you need motivation and initiative and the ability to educate yourself. Start now...