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 . . .
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 . . .
Be very wary of using the pip '-e' flag in production!
Each time we deploy to Heroku, the platform runs the following command:
pip install -r requirements.txt
This . . .
Welcome to the new home of the YJ tech blog.
Welcome to Silvrback, the new home of the YJ tech blog.
Being a geeky bunch, having a blog on Tumblr or Wordpress was never really going to cut it for the YJ tech blog. My original requirements were very simple:
- Write in Markdown
- Store in git.
I didn't really want the hassle of picking a theme, or . . .
We publish our changelog on the site, which we extract from Heroku's release API, and push to GitHub's Gist API. Here's how we do it.
I've written a couple of posts already about our deployment process, and its creeping automation. The final step has always been updating the changelog, which we publish on the site.. . .
Demonstrating the power of the web, and the great benefit to be had in publishing something even if it's not perfect, no sooner had I hit the send button than @stevejalim (of this parish) revealed to me that if you use a dict instead of a tuple, you can access the value by name, rather than index.
Thank you Steve.