<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>billy</title>
    <link>https://ruby-china.org/billy</link>
    <description></description>
    <language>en-us</language>
    <item>
      <title>其实元编程很烦人</title>
      <description>&lt;p&gt;不少人喜欢搞元编程，搞得本来干干净净的数据和类扭曲不已。&lt;/p&gt;

&lt;p&gt;在你写下 method_missing 之前，请三思，还有别的选择吗？&lt;/p&gt;</description>
      <author>billy</author>
      <pubDate>Mon, 11 Aug 2014 21:01:30 +0800</pubDate>
      <link>https://ruby-china.org/topics/20969</link>
      <guid>https://ruby-china.org/topics/20969</guid>
    </item>
    <item>
      <title>原来 Mt Gox 没有使用任何版本控制系统，恐怖啊</title>
      <description>&lt;p&gt;Mt. Gox, he says, didn’t use any type of version control software — a standard tool in any professional software development environment. This meant that any coder could accidentally overwrite a colleague’s code if they happened to be working on the same file. According to this developer, the world’s largest bitcoin exchange had only recently introduced a test environment, meaning that, previously, untested software changes were pushed out to the exchanges customers — not the kind of thing you’d see on a professionally run financial services website. And, he says, there was only one person who could approve changes to the site’s source code: Mark Karpeles. That meant that some bug fixes — even security fixes — could languish for weeks, waiting for Karpeles to get to the code. “The source code was a complete mess,” says one insider.&lt;/p&gt;

&lt;p&gt;&lt;a href="http://www.wired.com/wiredenterprise/2014/03/bitcoin-exchange/" rel="nofollow" target="_blank"&gt;http://www.wired.com/wiredenterprise/2014/03/bitcoin-exchange/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;基本无语了。&lt;/p&gt;</description>
      <author>billy</author>
      <pubDate>Tue, 04 Mar 2014 03:24:33 +0800</pubDate>
      <link>https://ruby-china.org/topics/17643</link>
      <guid>https://ruby-china.org/topics/17643</guid>
    </item>
  </channel>
</rss>
