Tweets for 2010-08-25
- Reduction of complexity is not the same thing as boilerplate avoidance. #
- @codemonkeyism Correct. Brevity reduces one dimension of accidental complexity. That still may influence total complexity either way. (1/2) in reply to codemonkeyism #
- @codemonkeyism I've been alleged to make my code too complex in situations when I've attempted to make it too brief (2/2) in reply to codemonkeyism #
- @codemonkeyism Thats a great post. Wish I had seen it earlier. in reply to codemonkeyism #
- A reason to use OO+Functional than only OO languages. Easier to write pluggable functions than functors for handling most corner cases. #
- @mrkkrj I find so. eg. just a function reference instead of "new" of a functor, boilerplate of the functor etc. in reply to mrkkrj #
- @mrkkrj If your question was is it worth changing the language used ? The answer would be no. in reply to mrkkrj #
- @mrkkrj Hmm.. I was suggesting it as a reason to use one language over another, not change one already in use. in reply to mrkkrj #
- RT @markhneedham: RT @MarkDalgarno: I Lehman's 'laws' of software evolution: http://is.gd/eClVJ http://is.gd/eCm2m #
- @vdichev Unfamiliarity introduces learning complexity needing to be amortised over reduced coding/operational complexity in reply to vdichev #
- @vdichev Yes, but sometimes library/tool authors handle far bigger feature set than users leverage which can increase complexity. eg. Maven in reply to vdichev #
- @vdichev the hard part is never the actual amortisation, its selling/buying the initial fixed cost
in reply to vdichev # - @jneira Python Answer (period = 4, data = list_of_vals) is
tuple((sum(data[i:i+period])/period for i in range(len(data)-period+1))) in reply to jneira # - @jneira so I'm a little confused what the fuss is all about. in reply to jneira #
- @jneira The haskell solution seems to be the neatest (only if I could grok it better ) in reply to jneira #
- @jneira couldn't resist playing some code golf myself http://is.gd/eDCNY
in reply to jneira #