Faceted searches with MongoDB and mongoose
Some people in Latin-America may remember an old Yupi ad where a woman was complaining on how difficult using the internet was. “It’s so difficult. So complicated! There must be something better.” (In Spanish, of course.) Cheesy as it sounds, Händel Messiah’s “Hallelujah” sonorously invaded the screen. Don’t believe me? See for yourself.
That’s how I felt when I was investigating what’s the best approach to achieve faceted searches in MongoDB. But I found something better. Let me show it to you.
Write it down!
Not sure if this has happened to you, but sometimes there’s just too much going on at the same time. Pretty much more that we can handle in our head.
This happens to me quite a bit: I’ll in the middle of an important meeting when suddenly someone comes in Skype saying “would you mind to code review this, please? It’s kind of urgent”. Then somebody will reach out to me saying “hey, I think the server’s down”. Then somebody will say “I think this issue is actually a server configuration thing, we’re blocked”, and somebody else will say “I cannot get the tests to run, it says undefined is not a function”. It’s like it’s raining urgent issues! This a way I found to handle the situation.
Google Inbox and Inbox Zero
I recently received a Google Inbox invitation, after requesting it three weeks ago. And after trying it out… boy, I love it.
Here I’m going to tell you why I love it so much, why it suits perfectly into my inbox management technique, and why I think it’d be useful for other people too. Also, a little bit of what it could have to make it even better.
CommonJobs: el fin de una etapa
tardis.js
StackOverflow me hizo replantear mis actitudes
Hace unos días me ocurrió algo genial: fui evaluado y mi evaluación fue mala. Como producto de eso tuve una pequeña epifanía. ¿Cómo puede ser?
Lo que no se sabe que no se sabe
Temo por cualquiera atrapado entre lo que sabe y lo que todavía no sabe que no sabe.
– Cecil, Pilot (Welcome to Night Vale)
Ember.js: queueHttpResponder
Hace un tiempo encontré una incompatibilidad bastante grande entre los sistemas de Ember.Testing y httpRespond, que impedían a muchos programadores testear sus sistemas de forma automática sin necesidad de un servidor de pruebas. Más adelante explicaré qué fue lo que generó este problema, por qué es un problema grave y el workaround que trabajamos con algunos colegas y algunos miembros del equipo de Ember.
