While Elixir is becoming a popular language for web development, there is at least one topic that I still find lacking: Deploys.
One of my main focus of the past few months has been my productivity with my text editor.
This post is a follow-up to Super-powered Vim, part I: Projections.
Spoiler alert: it’s premature optimizations.
Whenever a web app has integrations with external APIs (which, let’s face, happens most of the time nowadays), there’s usually an increased complexity about it when it comes to testing.
I recently watched Greg Hurrell’s screencast about Opening files in Terminal Vim, in which he showcases an OSX-only solution for being able to open files on Vim when using Finder.
Have you ever found yourself working alone for what appears to be too damn long ?
Code golf is an interesting concept to me: to solve a programming challenge, using not the most efficient or readable code, or the most state-of-the-art solution, but with the smallest code size possible.
I have lately run into a problem with my editor of choice, vim (well, actually, it’s neovim), and the syntax highlighting in Ruby files.
I’ve been experimenting with
factory_girl lately, particularly to deal with test data that’s not necessarily tied to the database. Did you know you can use it to instantiate any Ruby object, and not only
With recent advances in front end technologies, front end developers have been going crazy, pushing CSS to its limits and doing all sorts of beautiful animations. Seriously, there are some crazy things out there.
I said it before and I’ll say it again, several times: Automation is awesome.
I try to automate all the annoying repetitive things I can. And not long ago, merging Pull Request was certainly on top of my list.
Having written and read a lot of Ruby code, I occasionally come across some not-so-well-known features. Or even just a tiny detail that, as useless as it may be, I still find interesting.
If you were ever in charge of configuring a web server, you must know how painful it can be sometimes. During your first learning days, you probably spent an awful lot of time SSH’ing into the server, trying out something you just found online. It probably ended up being a slow trial-and-error process before you got your first server up and running.