Esto es en respuesta a la Carta abierta de un desempleado a los entrevistadores

A veces hago entrevistas laborales. Una de nuestras oficinas está en México. En mi compañía NO hacemos pruebas psicométricas, y solicitamos currículums sin foto, edad o información personal. Mi interés principal es 1) Eres listo, puedes escribir código al nivel que requerimos?, 2) Trabajas sin tenerte que decir qué hacer a cada rato? y 3) Tienes pasión por escribir software y por ayudar a otros a escribir software?

Evidentemente, todos los candidatos van a decir que sí. La cosa es probarlo. La validez de los metos con los que probamos cualquier cosa en cuanto a reclutamiento es lo que está en cuestión aquí.

Continue reading “Reclutamiento”

Some of my thoughts on Git

Git is the version control system I am using now. I find it useful for my needs in particular since I do at least a part of my work on locations that don’t have network access. Git uses a federated model – you have all the repository history, and you can commit even while you’re not connected.

If this sounds attractive to you, read on to see how you can use git as the sandbox for your svn repository and to learn about the features of git.

Continue reading “Some of my thoughts on Git”

Agile Chronicles Blog: A few good managers

This is awesome..

Development: “You want answers?”
Marketing: “I think we are entitled to them!”
Development: “You want answers?!”
Marketing: “I want the truth!”
Development: “You can’t handle the truth!!!

Son, we live in a world that requires software. And that software must be built by people with elite skills. Who’s going to build it? You, Mr. Marketing? You, Mr. Sales? You, Mr. Finance? You, Mr. Human Resources? I don’t think so.

Agile Chronicles: A Few Good Managers

technorati tags:, ,

On the topic of assertions

Every assertion should be thought from the standpoint of

  1. What was expected
  2. What actually happened

Translation: assertTrue should always, always have a message.

Consider the following:


This will only return “assertion failed”. Which is great, but how do we know what happened? If this is buried on one of the lunt automated remote builds, how am I supposed to know what is going wrong? Which is the expected? What actually happened?

A much better version of the same looks like this:

    "Was expecting something like "
        + myController.getSuccessView() + " but was "
        + mv.getViewName(),

Same assertion, but now it tells me more specifically what’s going on and I can fix bugs with it. Once I set this on the test, it becomes easy to see what was going on.

I recently had a Saturday with some other Bay Area developers where we did a lot of thinking about testing, so expect some more advice in the future as I collect my notes.

Remember the goal of unit tests is to “find bugs” (thanks Harry!). An assertion without an associated message merely notifies you that a bug occurred but doesn’t actually “find it”. As you are writing your unit tests, make sure you find it as well.

technorati tags:, , ,

Hunting vs. Gathering – our cavemen brain

I’ve spent the last few months implementing GTD and I’m still getting used to it, although I feel I’m achieving a comfortable rythm. One of the big “ah-hah” moments in this process however is the difference between our “hunting” and our “gathering” brains. The basic premise of dividing your time in “collecting without doing” and then “doing without collecting” is what makes you feel like you’re “in the zone” when you’re doing stuff and gives you a relaxed feeling when you’re done collecting your stuff.

After doing this for a little bit and then having a small crisis on a Scrum project (where requirements for the current sprint kept changing during the sprint). I realized that one of the big sources of mental stress is precisely trying to do both at once. Our brains just don’t seem to be able to handle it.

The way I see it, our brains are pretty much still cavemen brains, used to running out and hunting deer for a very long period of time, and then going out and foraging for food for another long period of time. If you get into a “chase” mode when you’re foraging, it means you’re the one being chased, and it automatically fires our stressors.

technorati tags: