Booking.com dev blog goes live!
I'm proud to echo the announcement that the Booking.com dev blog has just gone live. Quoting the announcement:
Booking.com is an online hotel reservations company founded during the hey-days of the dot com era in the 90s. The product offering was initially limited to just the Dutch market. We grew rapidly to expand our offerings to include 240,000+ accommodations in 171 countries used by millions of unique visitors every month - numbers which continue to grow every single day. With such growth come interesting problems of scalability, design and localisation which we love solving every day.
The blog is kicked off with just a quick, humble article of mine on a debugging module that I published after needing the functionality at work. In a given code location, it allows you to find where in the code base the current set of signal handlers were set up. We plan to publish new content regularly and have a few interesting stories already lined up. So stay tuned!
Physicist turned software developer. Working on Infrastructure Development at Booking.com. Apparently the only person who thinks the perl internals aren't nearly as bad as people make them.
See also: the Booking.com tech blog, CPAN.
The article is quite educational and i'd be happy to see more like that on there. On the other hand i get pretty frowny over the entire lack of commentary function. :/
Thank you! When we get the time, we plan to add Disqus or similar support. Basically, we want to avoid having to do moderation/spam checking as much as possible. Since it's a company blog, we'd also have to be a little more strict than in most personal blogs. I guess until then, answering as blog posts works (somewhat) or we could cross-post (like I did, sort of).
As for content, we have a whole bunch of conceptually similar stories (between 600 and 2000 words) lined up and are currently encouraging people to give it a shot to write about their tools and experience. We have a lot of developers, sysadmins, MySQL DBAs, and designers, all of whom could add differing facets to paint a more complete picture of the tools we work with. We hope that it'll be less of a barrier to entry to write a single article rather than having to keep up a blog entirely by themselves. Either way, feedback will always be welcome.
When I subscribed the feed, the “read on…” link ending the first entry on the blog gave me a sinking feeling at first sight, making me think I’d have to contend with a crippled summary-only feed… Thank goodness that turned out to be a false alarm. :-)
Congrats!
Pleasure to have more technical blogs, especially ones by actual companies, too.