Java is the right answer to the wrong question, Ruby is the wrong answer to the right question
Large code bases are the problem, not the language they’re written in. Find a way to break/decompose big code bases into little ones. Can we please stop calling each other silly names over the languages we choose and move on to calling each other silly names over our choices for writing literate programs, eliminating redundancy, decoupling modules from each other, and so forth? The very next time
Public Object: Refactoring to Guice: Part 1 of N
In this N-part series, I'm attempting to document some patterns for improving your code with Guice. In each example, I'll start with sample code, explain what I don't like about it, and then show how I clean it up. The bad code They're everywhere! Static utility methods that depend on lots of stuff, which must in turn be static:public class PizzaUtilities { private static final int TIME_TO_PREPARE
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
データマイニングを利用したプログラムの改善
