Drop the _drafts folder.

7 files changed, 0 insertions, 151 deletions

diff --git a/REAME.org b/REAME.org
index 50f545b..81654cf 100644
--- a/REAME.org
+++ b/REAME.org
@@ -10,7 +10,6 @@
   I don't really care about a clear history for the blog.
 
 * Write an article
-  Drafts should be in the *_drafts* folder.
 
 * Publish
   Publishing the blog is easy, you just have to run =make publish= and the site will be generated and rsync'ed to the server.
diff --git a/_drafts/emacs.md b/_drafts/emacs.md
deleted file mode 100644
index fdeb151..0000000
--- a/_drafts/emacs.md
+++ /dev/null
@@ -1,99 +0,0 @@
----
-layout: post
-category: emacs
-title:  Emacs modes
----
-
-For Christmas, I'll share a few modes for Emacs I've discovered
-lately.
-
-In the past few years, a few kit for Emacs have appears.  The first
-one was the Emacs Starter Kit (by technomancy), followed by Emacs
-Prelude and the last one is Emacs Live.  I don't use any of them,
-since I've my own configuration crafted the way I like, but from time
-to time I take a look at them to see what's new and what I can steal.
-
-I'm using Emacs on OSX, but I assume that most of the modes and
-example in this article will work at least for Linux.
-
-## Packaging
-
-Since version 24, Emacs come with a packaging system.  The official
-repository is Elpa, but you can add other repositories
-
- * [Marmalde](http://marmalade-repo.org)
- * [MELPA](http://melpa.milkbox.net)
-
-In your configuration, add the following code:
-
-..code
-(require 'package)
-
-(add-to-list 'package-archives '("marmalade" . "http://marmalade-repo.org/packages/") t)
-(add-to-list 'package-archives '("melpa" . "http://melpa.milkbox.net/packages/") t)
-
-(package-initialize)
-
-Now, if you want to install a package:  M-x package-instal {name}.  If
-you don't know what to install, a simple M-x package-list-packages
-will open a new buffer with all the packages available in the
-repositories you've selected.
-
-If you're using multiple computers and you share you're configuration
-between them, an easy solution is to list all the packages you want to
-be installed  everywhere:
-
-..code
-(defvar my-packages
-  '(magit
-    paredit
-    rainbow-delimiters
-    rainbow-mode
-    helm
-    helm-projectile
-    clojure-mode
-    diminish
-    nrepl
-    exec-path-from-shell
-    highlight-parentheses
-    auto-complete
-    markdown-mode
-    tango-2-theme
-    cyberpunk-theme
-    popwin
-    yasnippet
-    helm-c-yasnippet
-    yaml-mode
-    ruby-block
-    ruby-end
-    ruby-tools
-    inf-ruby
-    yari)
-  "A list of packages to ensure are installed at launch.")
-
-(dolist (p my-packages)
-  (when (not (package-installed-p p))
-    (package-install p)))
-
-
-## Helm mode
-
-I've been using ido for a long time now.  I knew about anything.el,
-and I've probably tried it in the past.  This project has been
-renamed to Helm, and it's much much better.  You could replace
-entirely ido with it, but I've been using it as a complement.  ido is
-good to open/find files/buffers, but if you're working on a project,
-Helm is more suited for that case.
-
-## auto-complete
-
-This one (and the next one) took me some time to decide I wanted to
-use them.  I've never been a big fan of auto completion stuff, and for
-what I want, hippie-expand is generally good enough.  But the video
-for [Overtone](http://vimeo.com/22798433) convinced me to give it a
-try, and I don't regret it.
-
-## yasnippet
-
-
-
diff --git a/_drafts/graphite-and-events.mdown b/_drafts/graphite-and-events.mdown
deleted file mode 100644
index 9442147..0000000
--- a/_drafts/graphite-and-events.mdown
+++ /dev/null
@@ -1,11 +0,0 @@
----
-layout: post
-category: devops
-title: Where we talk about graphing events in Graphite
----
-
-Graphite is thea nice tool.
-
-curl http://localhost:8090/events/ -d '{"what": "deploy_stage", "tags" : "deploy,stage"}'
-
-then by going to http://g.lumberjaph.net/graphlot/?&from=-15minute&until=-0hour&target=collectdlumberjaph_net.memory.memory-used&events=deploy# you can do correlation.
\ No newline at end of file
diff --git a/_drafts/on-doing-a-good-job.md b/_drafts/on-doing-a-good-job.md
deleted file mode 100644
index 2c1b86d..0000000
--- a/_drafts/on-doing-a-good-job.md
+++ /dev/null
@@ -1,6 +0,0 @@
-It's rarely easy to know if you're doing a good job.  There's so many point of views
-* users
-* developers
-* manager
-* yourself
-
diff --git a/_drafts/on-pair-programming.md b/_drafts/on-pair-programming.md
deleted file mode 100644
index e9684fa..0000000
--- a/_drafts/on-pair-programming.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-layout: post
-category: code
-title: On Pair Programming
----
-
-I'm working in a small team, since it's only me and Hachi.  We've been working together for about 8 months now, and we've developed an interesting way to work.  Our projects can be differents, it can be coding, experimeneting tools, deploying them, build systems around tools, etc.
-
-## Setup
-
-What we try to do during the afternoon, is to find an available meeting room with either a projector or a TV connected to a Mac Mini.  One of us "drive" the session, and either project on the wall or on the TV via AirPlay.  Since we're using our laptop and a huge external screen, it's easy for us to switch who's leading.  We tend to prefer using the projector, because that way we can walk to the wall and point stuff on it.
-
-Our current project include a lot of coding, and we've introduced a new pattern.  What we will do is to code on something during the morning, on our own, and in the afternoon we will review our different changes between merging them.  It's a more effective code review that using a tool like Gerrit, because you don't have to submit something and wait for input, you'll get it immediatly, and if you have to update your change, we do it together, that way we don't have to resubmit and wait for more input.
-
-So far it has been very effective for us.  We're able to work quickly, and it's usually fun.
-
--- TO READ
-http://www.bennorthrop.com/
-http://mwilden.blogspot.com/2009/11/why-i-dont-like-pair-programming-and.html
-http://mwilden.blogspot.com/2009/11/why-i-dont-like-pair-programming-and.html
-http://blogs.atlassian.com/2009/06/pair_programming_is_kryptonite/
-http://namcookanalytics.com/high-costs-and-negative-value-of-pair-programming/
-https://medium.com/@MarkNijhof
-http://jen20.com/
diff --git a/_drafts/preparingvmwithchef.md b/_drafts/preparingvmwithchef.md
deleted file mode 100644
index 2ddbccb..0000000
--- a/_drafts/preparingvmwithchef.md
+++ /dev/null
@@ -1,10 +0,0 @@
-Last week I've re-installed my current Linode server.  Since I wanted
-to limit the downtime, I prepared everything on a local VM using
-VirtualBox.
-
-One of the goal was to automate as much as possible this box (and in
-the process, learn a few things) I also went to use chef.
-
-This box host a few things : Jenkins, Phabricator, ...
-
-Was easy
diff --git a/_drafts/tcpdump.textile b/_drafts/tcpdump.textile
deleted file mode 100644
index e69de29..0000000
--- a/_drafts/tcpdump.textile
+++ /dev/null