Not visible without
the aid of special
instruments: subvisible

By Miguel Palhas

  1. This is the story of how we ended up with an ambitious time-frame to launch a platform, of the decisions we made along the way, and fortunately, of how it all turned out really well.

  2. While Elixir is becoming a popular language for web development, there is at least one topic that I still find lacking: Deploys.

  3. This post is a follow-up to Super-powered Vim, part I: Projections Keeping the same line of thought of the previous post, about taking the effort out of the boring tasks that come with writing code, let's now talk about a simple yet powerful concept: snippets.

  4. This post is the third of a three-part series. If you're interested, you can start by checking out: https://subvisual.co/blog/posts/133-super-powered-vim-part-i-projections and https://subvisual.co/blog/posts/134-super-powered-vim-part-ii-snippets.

  5. 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.

  6. 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.

  7. 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.

  8. 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.

  9. 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.

  10. 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.