1. Releasing software every day

    My vision of the software changed drastically when I started using a control version. First a bit of svn, and later git. The fact that you can create a checkpoints of your code is simply glorious. More later, when I started to feel more comfortable with git I started using…

    on workflow

  2. Synchronously asynchronous

    First of all, what's really means asynchronous? Asynchronous events are those occurring independently of the main program flow. Asynchronous actions are actions executed in a non-blocking scheme, allowing the main program flow to continue processing. By synchronous we mean a function that calls its callback on the same tick in…

    on programming workflow NodeJS

  3. UNIX for Developers

    Philosophy Small is beautiful. Make each program do one thing well. Build a prototype as soon as possible. Choose portability over efficiency. Store data in flat text files. Use software leverage to your advantage. Use shell scripts to increase leverage and portability. Avoid captive user interfaces. Make every program a…

    on programming workflow

  4. Module Driven Development

    From since a time ago, I was thinking how to write code without repeating. DRY in all its glory, and believe in me when I tell you that it isn't always easy. Think in an architecture of code so big, that's handle so many data and dispatch in different process.…

    on programming workflow

  5. Polyfill, Ponyfill and Prollyfill

    Commonly we used it, but exists a subtle difference. Normally we use it for refer browser, node or javascript features, but I understand that you can extrapolate it for another language or environment. Polyfill Replicate an API using JavaScript (or Flash or whatever) if the browser doesn't have it natively.…

    on programming