TIL Today I Learned...


Limpiando logs binarios de MySQL

Posted on July 26, 2017

El log binario es un log que utiliza la sincronización de MySQL/MariaDB para guardar los cambios que hay tanto en la estructura de la base de datos como en los datos de la misma. La idea es que mediante ese log los diferentes componentes de la sincronización se ponen de acuerdo en los cambios que hay. Hay mucha más información en este enlace: https://mariadb.com/kb/en/mariadb/binary-log/ .

MySQL

[MySQL logo]

Cómo he creado este sitio

Posted on July 21, 2017

Inauguro este espacio explicando cómo se ha creado. Quiero que este espacio sea un lugar para guardar mis notas personales relacionadas con la informática a modo de referencia personal compartida con el resto de la humanidad. Agradezco a toda la comunidad del software libre, Github y Jekkyl en general y en especial a Anton Khodakivskiy por la base y "a la Mari" (por enseñarme la base y el cómo hacerlo). Veamos cómo se ha montado esta web

Jekyll and Github pages

[Jekkyl and Github Pages]

Forward Declaration and Private Implementation in C++

Posted on December 11, 2012

Well... I catually learned this a long time ago, but nevertheless. Includes in C/C++ are extremely inefficient. It's not uncommon to find a system where a single change to a header file file would cause 10 minutes recompilation. I used to suffer from this a lot. I could count the number of times my code had compiled (or not) in a day by the number of tea/coffee cups consumed plus the number of articles read. There's been a lot of discussion on C++ modules recently. [These slides by Doug Gregor][dg] explain what's happening under the hood, why C++ compilation tends to be so slow, and how C++ modules can help. The bottom line is that compiling even a single source file might take a while.

It's Compiling

[XKCD #303][xkcd]

Posted on July 28, 2017

The time has come for me to venture into the blogging business. Every day I deal with various software related conecpts, ideas, and problems. I learn from these interactions a lot. What bothers me is that now, after 6 years of professional software development I realize that I don’t really remmber what I’ve been working on in the past years. There are lots of grey areas even if I sit down and revisit some of my past code. In other words the retention isn’t that great.

In this blog I’m going to regularly write on the aforementioned topics. And I hope that I will get better idea about them after formalizing my findings in writing.

For this purpose I set up this blog. It was a challenge of its own to make a platform choice. Nowardays there is a ton of different hosted blogging platforms - Wordpress, Blogger, Tubmblr to name a few. But I happened to stumble upon GiHub:Pages and Jekyll. This neat combo currently drives my blog.

Jekyll is a blow aware static site generator. It runs on a bunch of templated files and outputs static HTML which can be hosted virtually anywhere, and on GitHub:Pages in particular. GitHub:Pages will run Jekyll begind the scenes, and serve the generated site. My job was to set up all the templates and configuration. There is a few prebuilt solutions available for this purpose - Jekyll-Bootstrap or Octopress, but I wanted to go throught this process myself, and build it from scratch. Of course my implementation doesn’t have too many features, but it’s mine :)

In a few words - Jekyll grabs HTML, Markdown, or Textile files, passes them through the specified template and outputs a plain HTML file. The beauty of this approach is that I can write posts in my favorite editor - Vim and just push them to my GitHub repo. GitHub:Pages will then call Jekyll on the collection of files, regenerate the site and promptly publish it.

Such a blog is blazing fast, the hosting is free, and the amount of control over the content and markup is just incredible. And Twitter Bootstrap has everything a wannabe gloggers needs to create pretty posts.

The source code for this blog rests here

Hope that wasn’t too bad for the first time :)

  • Tags: