cleanup drafts

6 files changed, 0 insertions, 121 deletions

diff --git a/_drafts/a-repl-is-superior-to-a-shell.md b/_drafts/a-repl-is-superior-to-a-shell.md
deleted file mode 100644
index cda93bc..0000000
--- a/_drafts/a-repl-is-superior-to-a-shell.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-layout: post
-title: A REPL is superior to a shell
-summary: In which I show that a REPL is superior to a shell
----
diff --git a/_drafts/how-i-learned-to-stop-worrying-and-love-emacs.md b/_drafts/how-i-learned-to-stop-worrying-and-love-emacs.md
deleted file mode 100644
index 57d8944..0000000
--- a/_drafts/how-i-learned-to-stop-worrying-and-love-emacs.md
+++ /dev/null
@@ -1,13 +0,0 @@
----
-layout: post
-title: How I learned to stop worrying and love Emacs
-summary: In which I share my love for Emacs.
----
-
-Until a few years ago I was a vi user. One of my then co-worker was a heavy Emacs user and I used to make fun of him.
-
-Like many developers, I was obsessed with my configuration files, trying to improve.
-
-Now I don't care. I don't need the name of the git branch in my prompt. I almost never use the git CLI anymore, or tools like tig, I just rely on magit to give me all the information I need, to browse the changes, or to commit my work.
-
-I've stopped using zsh, either I'm in eshell, or in bash. Since I'm using both of them, instead of having a heavy and complex configuration for it, I just use bash without any extras. My bashrc only add a few things to the path and export a few environment variables needed by some tools.
diff --git a/_drafts/looking-at-chronos.md b/_drafts/looking-at-chronos.md
deleted file mode 100644
index 9c27259..0000000
--- a/_drafts/looking-at-chronos.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-layout: post
-title: Looking at Chronos
-summary: In which I take a look at Chronos
----
-
-# Looking at Chronos
-
-I've decided to look at Chronos, a cron replacement running on Mesos.
-
-Mesos
-
-## Getting an environment
-
-First I need to get an environment to play with it. Let's do that quickly with Vagrant and Ansible:
-
-```ruby
-Vagrant.configure("2") do |config|
-  config.ssh.forward_agent = true
-
-  config.vm.provision :ansible, :playbook => 'playbook.yml'
-
-  config.vm.provider :virtualbox do |vb, override|
-    override.vm.box = "precise64"
-    override.vm.box_url = "http://files.vagrantup.com/precise64.box"
-  end
-
-end
-```
-
-And the playbook for Ansible:
-
-```yaml
-  - hosts: all
-    sudo: yes
-    tasks:
-      - name: Install a bunch of packages
-        apt: pkg={{ item }} state=installed
-        with_items:
-          - autoconf
-          - make
-          - gcc
-          - cpp
-          - patch
-          - python-dev
-          - git
-          - libtool
-          - default-jdk
-          - default-jre
-          - gzip
-          - libghc-zlib-dev
-          - libcurl4-openssl-dev
-
-```
-
-Now I can run `vagrant up` and wait to get the VM build with everything I need.
diff --git a/_drafts/on-doing-a-good-job.md b/_drafts/on-doing-a-good-job.md
deleted file mode 100644
index 2f0e3ab..0000000
--- a/_drafts/on-doing-a-good-job.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-layout: post
-title: On doing a good job.
-summary: In which I share my thought on what it means to do a good job.
----
-
-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 3b1291b..0000000
--- a/_drafts/on-pair-programming.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-layout: post
-title: On pair programming
-summary: In which I share how I'm doing 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/on-trust.md b/_drafts/on-trust.md
deleted file mode 100644
index c2ae066..0000000
--- a/_drafts/on-trust.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: On trust
-layout: post
-summary: In which I talk about trust
----
-
-I've a problem: most people I know (friends, co-worker, my mum) don't trust me. Most of the time they second guess, doubt what I say. To be honest I find that really irritating. I'm sure it tells more about myself more than anything else, since trust is something you earn, but anyway.
-
-A few weeks ago I was watching Russ Olsen's talk "(To The Moon)[http://www.youtube.com/watch?v=4Sso4HtvJsw]". Take one hour to watch it, it's one of the most inspiring talk I've seen. Toward the end of the presentation, he tells the story of Neil Armstrong, and how he had to take a quick decision to make the capsule fly toward instead of down, to avoid landing in a crater. It would have been a perfect time for all the engineers in the command center to say "Hey Neil, you shouldn't do that" or "You should do it that way". But no, no one said anything, they trusted the person who was in charge.
-
-Still, I'm lucky to have a great co-worker who trust me. When we work on something, he trusts that if I don't know or understand something, I'll ask him. This is definitely a better way to work.