Adding features (and a little glamour) to the Django test runner
YJ's CTO, @hugorodgerbrown, has a knack for asking the good kind of "Why can't X do Y?"questions. By the good kind, I mean the ones that challenge things others have often just slipped into accepting, even if they're non-ideal.
And, while he appears to be a very happy Django convert, he's also brought a fresh . . .
Anyone interested in an industry ski trip?
[Update: h/t to @stevejalim, as this is partly a response to a conversation we had a while back..]
I've just come back from a week's skiing in the Alps, with a group of people
that I didn't know before the trip, brought together only by a collective interest
in skiing. A lot of time was spent on the mountain, but almost as much . . .
Brief thought on the Joyent debacle
In the last couple of days a row has broken out over on Github regarding an innocuous and well-meant pull request(to replace a gender-specific pronoun ("he") with a gender-neutral version ("they")) which blew up into an almighty "is this really important" fight, which then spilt over onto Twitter and Hacker News, . . .
It's not as simple as it at first appears - some tips from the frontline.
A lot of what we do at YJ is date-dependent, and amongst our unit tests we have (as I now know) 500+ tests that rely in some sense on the value of python's
Since launching YJ we have been running on Django 1.4, and mocking out datetime.date using the technique outlined in this article:
from datetime import . . .
Notes on a recent interview with Marc Andreessen in which he discusses the nature of internet businesses
(Quotes in this post come from this article on Fortune)
There's an interview with Marc Andreessen that's been doing the rounds recently that really chimes with what we are trying to do here at YJ, and although it's not strictly tech, I wanted to do more that just retweet the quotes I liked!
The section that is most relevant to us . . .
Always have a remote backup on hand
When working on a large feature locally, there is always a conflict between pushing work-in-progress changes (WIP), so that they are backed up somewhere, and no longer only on your local machine (which will break down or get stolen the day before you are due to launch), and keeping everything to yourself so that you can rebase locally and . . .
Hot-swapping infrastructure services on-the-fly.
Earlier this week we had what could have been a catastrophic infrastructure failure - our ElasticSearch cluster went offline. Given that this powers the core functional element of our entire business, this was not a good thing to wake up to.
As I started investigating what had gone wrong, I could practically hear the sniggers from the cloud . . .