"What's going to production?"
»Lets eat Grandma« or »Lets eat, Grandma«? It depends on whether you want to actually eat your grandmother or you want to say to her that you're going to eat.
Just a quick look at
select in Rails.
When working on old Ruby code, you'll see the old (<= 1.9) hash syntax:
So we're building this JSON API at autobutler.dk, in which we want the JSON outputted to be human readable (pretty).
Nothing is worse than trying to debug a JSON service, and always having to parse it through e.g.
At autobutler.dk we are currently developing a new flow for car owners to enter. This flow is based on a data-driven API. The new flow will be a front-end client of this API.
So TheRubyGame was just brought back from the dead. The newest challenge (Challenge #1) is about ducks and fire and ducks on fire.
I've been going crazy over that Mac OS X has a shortcut for
√ (Square root sign) but not for
✔ (Check mark).
So I took my
erubis for another spin.
I'm doing a lot of back-end work in Ruby and in Rails.
Lately we hired a full-time front-end developer, and I wanted to give him some pointers in the
index.html.erb-file in the
/app/views/home-dir (front page of our site).
I started writing some comments in the file, in a branch, which he could then take and improve on, get to know some of the models (stats shown on the front page) and view-helpers.
Previously I wrote about
aliases, however I just swtiched back to
zsh and thought I'd share some of my
.bashrc-file. I also switched from TotalTerminal to iTerm 2.
We all have those small lines of code that we write again and again and again. Why not write a script to do it for you?
I must say. Usually I swear to Rails.
"Hey, shouldn't we build this?", "Yeah, of course, lets use Rails!".
However this tends to get out of hand.
You really shouldn't build everything in Rails, just because you can, why not use some frameworks that are built with a specific application in mind, e.g.