00:46 <dkubb> mbj: hey

00:47 <dkubb> mbj: are you thinking about making a simple object to track the keys for validation?

05:42 <travis-ci> [travis-ci] Build details : http://travis-ci.org/dkubb/memoizable/builds/14124548

05:42 <travis-ci> [travis-ci] Change view : https://github.com/dkubb/memoizable/compare/93d4ea35d189...7cefb5e82bf8

05:42 <travis-ci> [travis-ci] dkubb/memoizable#31 (wip-interface - 7cefb5e : Dan Kubb): The build has errored.

09:56 <travis-ci> [travis-ci] dkubb/memoizable#46 (master - f3a8a34 : Erik Michaels-Ober): The build has errored.

09:56 <travis-ci> [travis-ci] Build details : http://travis-ci.org/dkubb/memoizable/builds/14131262

09:56 <travis-ci> [travis-ci] Change view : https://github.com/dkubb/memoizable/compare/34cb380bf1f1...f3a8a3469e69

15:18 <mbj> snusnu: https://twitter.com/_m_b_j_/status/402426690862714880

15:19 <snusnu> mbj: cool!

16:41 <dkubb> good morning

18:27 <cored> hi

20:08 <cored> after finishing a program

20:08 <cored> now I'm going to add devtools

20:09 <cored> and see where can I improve it

20:09 <cored> https://gist.github.com/cored/1025fc9cbbb35d0d3e3b

20:09 <cored> what do you think guys ?

20:45 <cored> what does not informative module means?

20:46 <cored> from a reek point of view

20:46 <cored> can I just omit that using devtools

20:46 <cored> ?

20:49 <mbj> cored: via the reek config file

20:52 <cored> got it

20:53 <cored> let's see what mutant says about my code

20:54 <mbj> cored: hint mutant does also work "without" devtools.

20:55 <cored> mbj: I just install devtools because I want to get my code in rom shape

20:55 <cored> wow a lot of duplication from flay

20:55 <cored> expecting 0 but I have 29

21:17 <mbj> cored: flay score is only 0 if you have "no" code ;)

21:18 <mbj> cored: The default config ships all "0" metrics to make sure you do the initial adjustment.

21:18 <cored> mbj: oh ok

21:18 <cored> mbj: let me switch that

21:18 <cored> mbj: but mutant just hit me hard

21:18 <mbj> cored: its his job ;)

21:19 <mbj> cored: After doing mutant constrainted dev for some month: You'll proactively avoid traps.

21:19 <cored> well I did not start metrics first development

21:20 <cored> I just wrote my code as always and then added devtools

21:20 <cored> to get it in better shape

21:22 <cored> mbj: so regarding mutant

21:22 <cored> mbj: what am I looking here, I have to add tests for each line mutant remove or add, right ?

21:25 <mbj> cored: not only

21:25 <mbj> cored: but also ;)

21:32 <cored> oh

21:32 <cored> well I added my own set of specs

21:32 <cored> but totally found some stuffs taht mutant is adding that my code can't handle

21:32 <cored> good stuff

21:44 <cored> mbj: found something interesting

21:44 <cored> mbj: .each_with_object returns the initial value mutated

21:44 <cored> mbj: but never returns nil in any context

21:44 <cored> mbj: mutant added a nil return value from a method using .each_with_object impliying that could happen

21:44 <cored> but I can't see the edge case

21:44 <cored> let me show you some code

21:45 <cored> https://gist.github.com/cored/7535915

21:47 <micho> hi! I am updating an attribute of my Datamapper object - it works only if some conditions are fulfilled (simple if). In another case it returns false, and doesn't update. I want to put it together with default update method, so: if in update method that specific parameter will be updated, I want to check the condition and update or not. As far as I did now, I can rewrite setter to myvalue (update calls setters for every param). Is it p

21:47 <micho> ossible to return false value to update, if "my" updating will fail? The return value of setter is obviously not a good idea...

21:55 <mbj> cored: so you have an unkillable mutation?

22:08 <cored> mbj: that's what I think

22:08 <cored> mbj: not sure if that's the case, did you look the code?

22:14 <micho> http://pastebin.com/CmuCQgHC - "true if resource and storage state match" - what does it mean?