News for hackers. Stuff that matters.
Re:Ultratestable Coding Style by jheriko on Tuesday June 09, 2015 @09:08AM (#9685651)
this just falls out of writing code cleanly and properly. if you are doing something so complicated with inputs and outputs thatit becomes unclear what is happening and where things need to go in and go out then you just haven't used enough functions and classes to split up the responsibilities.

if you write clean, data driven code i can't imagine this ever being a problem you need to solve.

Re:Ultratestable Coding Style by jerf on Tuesday June 09, 2015 @09:43AM (#9685812)
"If you use the solution given in the article, I can't imagine why you'd ever need the solution given in the article"?
Re:Ultratestable Coding Style by jheriko on Thursday June 11, 2015 @11:13AM (#9700179)
its more that its not about writing code to be testable. its about writing code well to start with for n reasons.
Re:Ultratestable Coding Style by Dewie3 on Tuesday June 09, 2015 @01:40PM (#9687323)
There is always that one guy who gets offended over how obvious something is to him.
Re:Ultratestable Coding Style by AnimalMuppet on Tuesday June 09, 2015 @01:58PM (#9687443)
Given the number of comments that I've seen from jerf, and the value of what he usually has to say, I don't think he's being "that one guy". I think he's commenting on what he perceives to be a genuine inconsistency in the article.
Re:Ultratestable Coding Style by Dewie3 on Tuesday June 09, 2015 @02:02PM (#9687479)
My comment was actually referring to jheriko. :-]
Re:Ultratestable Coding Style by AnimalMuppet on Tuesday June 09, 2015 @04:17PM (#9688276)
Ah, I see. My error.