08.19.07 - 11:37pm
We developers and other nerdy folk are used to using strange and klunky applications that do something special, and we’re used to that trade-off.
Eclipse is an IDE so it’s hard to imagine it not being baroque and difficult to use, requiring weeks of effort to become productive. JBidWatcher has saved me a lot of money […]
Category: C++, Python, mobile, java, ruby, architecture, IA, articles, Linux | Tags: | 2 Comments »
08.16.07 - 05:05pm
Ruby faster than Python and Perl! cries the headline. This is based on a benchmark that tests “i = i + 1” in a loop, so it’s a particularly useless benchmark, even in a world of benchmarks designed to test unrealistic scenarios that make the benchmark author’s product look good.
Category: Python, perl, java, ruby, articles | Tags: | 1 Comment »
08.04.07 - 04:21pm
I’ve written before about tips for offshoring. One specific thing I said to watch for is the bait-and-switch of talent: during the sales process you’re shown rockstars, but the real code you get is written by clueless newbies. When you set up a project such that you’ve minimized the cost per hour of development, but […]
Category: management, java, testing, offshoring, outsourcing, sql, labor, humor | Tags: | 7 Comments »
08.02.07 - 08:37pm
From what I’ve seen, Rails’ weakest features lie in the way it prepares the test database and test data, and Ruby’s Test::Unit isn’t much better than the awful but ubuiquitous JUnit that Java developers are accustomed to. I set out this week to impose my preferences on Rails in this area, and that took some […]
Category: ruby, java, testing, ruby on rails, postgresql, databases, sql, architecture | Tags: | 5 Comments »
07.11.07 - 01:26pm
Coverage tests in Ruby (with rcov) are less strict than in Java (with EMMA), so watch out - 100% coverage is easy to attain but not as meaningful.
Category: testing, coverage, java, ruby, tools | Tags: | 3 Comments »