How to Become a Hacker?

42,647 views

Published on

5 Comments
22 Likes
Statistics
Notes
No Downloads
Views
Total views
42,647
On SlideShare
0
From Embeds
0
Number of Embeds
3,507
Actions
Shares
0
Downloads
9
Comments
5
Likes
22
Embeds 0
No embeds

No notes for slide

How to Become a Hacker?

  1. How to become a hacker? (In the 21st century)
  2. Probably youre (just) a geek.
  3. But you want more, right?
  4. Story #1
  5. Lesson #1: Prepare for a long trip.
  6. Story #2
  7. Lesson #2: Find mentors.
  8. Story #3
  9. Lesson #3: Distinguish yourself.
  10. Story #4
  11. https://vimeo.com/22798433
  12. Lesson #4: Go interactive.
  13. Story #5
  14. Lesson #5: Hold your hands.
  15. Story #6
  16. Lesson #6: Play (dont comment).
  17. Story #7
  18. https://www.youtube.com/watch?v=N6HCOGj1lNI
  19. Lesson #7: Start now.
  20. Lesson #8: Restart often.
  21. ...
  22. Yet another story
  23. Bad news: your boss will not be your mentor.
  24. Good news: your hacking mentors are alive!
  25. Thats probably why you want to be a hacker.
  26. The virtuous circleand the dangerous triangle (Three inspiring hackers)
  27. Its hard to be both patient and enthusiastic
  28. Its hard to be both patient and enthusiasticIts hard to be both enthusiastic and smart
  29. Its hard to be both patient and enthusiasticIts hard to be both enthusiastic and smart Its hard to be both smart and patient
  30. Its hard to be both patient and enthusiasticIts hard to be both enthusiastic and smart Its hard to be both smart and patient Do your best!
  31. Its hard to be both patient and enthusiastic Its hard to be both enthusiastic and smart Its hard to be both smart and patient Do your best!(When dealing with yourself and with others.)
  32. We are more powerful but more impatient.
  33. ...
  34. Hands on!
  35. Fix your email setup (Demo Gnus)
  36. Marry your text editor (Demo GNU Emacs)
  37. Master your versioning system (Demo Git/magit)
  38. Have a TODO list system (Demo Emacs Org-mode)
  39. Learn how to make a bug report (Demo bad and good reports)
  40. Scratch your own itch (Start small)
  41. Scratch other peoples itches (Start small)
  42. Pick up a programming language (Cant really help on this)
  43. Understand users environments (Demo)
  44. Learn how to test (Demo)
  45. Learn how to read/write english (Demo)
  46. Postels law & robustness principle: "Be conservative in what you do... ...be liberal in what you accept from others"
  47. ...
  48. A typical free software project
  49. • A website• .zip/.tar.gz files to install• Discussion list(s) and IRC channel(s)• Documentation• A publicly accessible repository• A Bug tracker• A Community• An ecosystem (distribs, forks, [up|down]stream)
  50. Example: GNU Emacs
  51. ...
  52. Hands off!
  53. Get a computing culture (Write... and read)
  54. Get a free software culture (Read... and write)
  55. "Computer criticism" (Seymour Papert)
  56. "Learnable programming" (Brett Victor)
  57. Thanks! Bastien Guerry Jan. 18th 2012 bzg@gnu.orghttp://lumiere.ens.fr/~guerry/
  58. (Bonus tracks)
  59. How To Become a Hacker by Eric S. Raymondhttp://www.catb.org/esr/faqs/hacker-howto.html
  60. Growing the Org-mode community• Community documentation (Worg)• A mailing list for both users and developers• No roadmap• No separate bug tracker (we use the mailing list)• Attract great power users• Give as much freedom to users as you can
  61. The thrill of collaborating
  62. Free software and innovationKrzysztof Klincewicz, Innovativeness of open source software projects, August 11, 2005
  63. Free Software history• 1983: Richard Stallman starts the GNU project• 1984: RMS starts the Free Software Foundation• 1985: First free software license for GNU Emacs• 1989: GNU GPL v1.0 (v2.0 in 1991)• 1992: Linus publishes Linux under GPLv2• 1998: Project Mozilla kicks off• 2001: Wikipedia and Creative Commons kick off• 2002: Release of Firefox 1.0• 2005: First release of Git• 2007: GPL v3.0 and CC v3.0
  64. Free licenses history• 1989 : GPLv1• 1991 : GPLv2• 1999 : BSD• 2001 : CC fondé• 2002 : CC v1• 2004 : CC v2• 2005 : CC v2.5• 2007 : GPLv3 et CCv3• 2009 : Lancement CC0
  65. When you are a teenager, alone with a (programmable)computer, the universe is alive with infinite possibilities. You area god. Master of all you survey. Then you go to school, major in"Computer Science", graduate – and off to the salt mines withyou, where you will stitch silk purses out of sow’s ears in somebraindead language, building on the braindead systems createdby your predecessors, for the rest of your working life. There willbe little room for serious, deep creativity. You will be constrainedby the will of your master (whether the proverbial "pointy-hairedboss", or lemming-hordes of fickle startup customers) and by thelimitations of the many poorly-designed systems you will useonce you no longer have an unconstrained choice of task andmedium. Engelhart’s violin, http://www.loper-os.org/?p=861
  66. Software Engineer to join its close-knit, agileengineering team Candidates must be intellectuallycurious, self-driven, highly motivated andproductive. They must be problem-solvers, who arepassionate about shipping code, and buildingrobust and scalable Internet applications. Wait!... maybe your boss will be a hacker too?
  67. ~$ cd me/; git shortlog• 1986 : Some programming in LOGO and BASIC• 1984-1992 : Playing LEGO• 1995-2003 : Philosophy and cognitive sciences• 1998- .... : Free Software hacktivist• 2007- .... : Learning tomorrow (Book)• 2008- .... : One Laptop Per Child France• 2010-2011 : Wikimédia France• 2010- .... : Emacs Org-mode maintainer

×