Several times I’ve tried to get to know Vim better: understand it, use it, become fluent at it and productive. It has not been easy.

But on my recent visit to Bristol to meet the CookiesHQ team, Nicolas Alpi gave us a crash course and introduced us to his Vim Configuration Directory, and although I am still veeeery far from being a Vim-guru, I think I’m set on the right path, which is definitely a step forward.

You can read about getting started in Vim and our CookiesHQ Vim Config on the post I’ve just published at the CookiesHQ blog.

After two months working with CookiesHQ, this March they decided to fly me over to Bristol, know the team and work from their office for a week. Working remotely is a challenge, and also is knowing each other in person!

We did a couple of blogposts recollecting our views in the experience. Here is the ‘company view’ of the visit, by the company director Nathalie Alpi, and this is how I experienced it.

All in all, it was a great experience, and if you work remotely or employ remote workers, you should try to do something similar!

Yesterday I published an article on the CookiesHQ website, talking about the integration of ElasticSearch on a Ruby on Rails application that uses MongoDB.

Check it out!

Right now I find myself working on a porject that uses MongoDB, and sometimes I work on projects with PostgreSQL and other times on projects that use MySQL. The difference is that I have to manually load both MongoDB (mongod) and PostgreSQL (I use the Heroku app) when I want to use them, but MySQL is loaded in my system by default.

Thinking on an all-or-none solution, I decided to convert MySQL in a service run on demand, instead of a resident one. I have installed MariaDB via Homebrew, so:

  ➜  julitrows.gitlab.com git:(master) ✗ brew info mariadb
  mariadb: stable 5.5.34, devel 10.0.7
  http://mariadb.org/
  ...
  **BLAH BLAH BLAH **
  ...
  To load mariadb after an update
      launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.mariadb.plist
      launchctl load ~/Library/LaunchAgents/homebrew.mxcl.mariadb.plist

So the second to last line is what we are looking for. By running:

launchctl unload ~/Library/LaunchAgents/homebrew.mxcl.mariadb.plist

We’ll remove mysql from being run at startup.

And when we want to use mysql, just do mysql.server start, and mysql.server stop

Easy!

DISCLAIMER: This post is in Spanish as its potential target are Spanish freelancers struggling with the Electronic Administration. Feel free to use Google Translator to know what the fuss is about.

Algunas declaraciones de la AEAT, creo que las que se ahcen a través de aplicaciones instaladas en el disco duro tipo P.A.D.R.E., requieren una carpeta llamada aeat en la carepeta /Usuarios/fulanito con los siguientes permisos:

• Usuario: Leer y escribir
• Staff: Sólo leer
• Everyone: Leer y escribir <– este hay que ponerlo así, por defecto está en “Sólo leer”

Pero otras gestiones, como por ejemplo el modelo 037 que he tenido que hacer hoy mismo, requieren que la carpeta aeat exista en el DIRECTORIO RAIZ DEL SISTEMA, es decir, para poder hacer todas las gestiones (o al menos a las que yo me he enfrentado por ahora), necesitaremos estas dos carpetas en nuestro sistema:

Macintosh HD/aeat
Macintosh HD/Usuarios/fulanito/aeat

O hablando en términos de consola:

/aeat
/Users/fulanito/aeat <-- cambia *Users* por *home* si estás en GNU/Linux

Los permisos con chmod creo que serían 757, es decir rwxr-xrwx

Francamente, no sé como de seguro es tener una carpeta con permisos de escritura para todo dios en el directorio raíz del sistema, pero tener que dar permisos de escritura en el directorio raíz a una aplicación que se ejecuta en el espacio de aplicaciones del usuario me huele a chapuza gorda. Estaría bien que unificaran los criterios de escritura y todo fuera a parar a la carpeta personal del usuario.

Lo más absurdo de todo es que he averiguado el error de escritura en el raíz a base de mirar el log que el applet de la AEAT escribe en… tachán tachán… la carpeta aeat de mi espacio de usuario, sin ningún tipo de problema. Que alguien me lo explique.