Let's face it, you are probably not documenting as much as you should. However, code is read a lot more than it is written. We often think about the computer executing the code, but how often do you think about your fellow co-workers/co-programmers when writing your code?
In this blog post, I show up to build a web application that combines the benefits of server-rendered HTML and client-side JS
A simple improvement to devise
I just wanted to start a chrome extension and figured I should check out what all the hype with the frontend tooling scene is all about. The ecosystem looks pretty amazing, however, it seemed like there wasn't a lot of content out there on how to make the chrome-extension work with require-js for modular JS, so I figured i'd write it down here.
This is a companion post to our Tale of Credport post in which I will go into further detail about the technical problems we had and decisions we made. You probably want to read that one before this one. Credport’s evolution in technical design on both the front-end and the back-end effectively coincided with our evolution from Boston/Webcred to Berlin/Credport.
In a recent project of mine I had to implement an activity feed. I have been meaning to try out the proposed solution by GiveGab which was a response to ThoughtBot's approach. I especially liked GiveGab's elegant solution to address the issues ThoughtBot had with the fan out on read approach by using Enumerations with findeachin_batches in the background to do the heavy-lifting in the database.
For quite some time now, I have seen people become more and more interested in startups and buildings products. There are many reasons why startups are becoming hip but I believe a fundemental one is the sheer reduction in resources needed to get something out of the door. I attribute a lot of my experience to the fact that I stumbled upon the powerful combination of Ruby on Rails and Heroku, so I decided to give back and give people the opportunity to be enlightened as well :)
It's this time of the year again. Every once in a while comes that twitch, that realization that maybe, I should redo my website. Said and done, you are looking at the fourth revision of it. It all started with a Wordpress Blog for Maps Offline, then a Joomla CMS for Nam's Remote, then an iWeb site, then a basic Rails site and now hopefully a slightly more polished version. Back then, I also had very modest site titles such as "Nambrot.com - Showcase of Incredibility".
I wanted to take this opportunity and talk a bit about how I have approached this redesign.
For a couple weeks, I have been working on an idea that I hope will develop into something greater in the next months. While that idea involved mainly theoretical and operational issues, I wanted to keep my practical skills inline and since I have been reading a lot about web applications and especially Backbone.js, I decided to just play around with it. I ended up writing a small prototype for a Facebook Photo Browser based on the Graph API.
How to get more out of your Heroku Dyno