Comments on: When should you test?

By: kindohm

kindohm — Wed, 20 Mar 2013 21:58:00 +0000

AND naked. Don’t forget naked.

By: dotnetchris

dotnetchris — Wed, 20 Mar 2013 16:04:00 +0000

I think not testing is more like driving a car blindfolded.

AND without a seatbelt.

By: Stephen Balkum » Blog Archive » Some good reading

Stephen Balkum » Blog Archive » Some good reading — Mon, 18 Mar 2013 21:46:59 +0000

[...] Bailey’s post, On Testing “Trivial Code,” spawned further reading from Jimmy Bogard (When should you test?) and Uncle Bob (The pragmatics of TDD.) For the record, I lean more toward Uncle Bob’s [...]

By: On Testing “Trivia Code” | ThoughtStream.new :derick_bailey

On Testing “Trivia Code” | ThoughtStream.new :derick_bailey — Mon, 11 Mar 2013 17:05:12 +0000

[...] wrote a post that I think was unrelated, but happens to fit perfectly in to the conversation. In that post he [...]

By: kindohm

kindohm — Mon, 11 Mar 2013 15:35:00 +0000

I agree. Hard-core, high-coverage developers often say that writing tests is like wearing a seat belt. Would you drive a car without a seat belt? I think this is a terrible analogy. Testing isn’t an On or Off setting. Testing is more like wearing clothing. How much do you need to feel secure and/or protect yourself? Sometimes full body armor is required. Sometimes you just need jeans and a t-shirt. Sometimes running naked is ok.

By: Peter Moberg

Peter Moberg — Sat, 09 Mar 2013 00:34:00 +0000

Programming will just move to another higher level of programming. But at the speed we are moving at the moment (not like object oriented or functional programming is something new), i think it will be much longer than 10 years

By: Nathan Alden

Nathan Alden — Fri, 08 Mar 2013 16:26:00 +0000

Who woulda thunk it! Everything old is new again, like calculating ROI for business activities!

By: Karlkim Suwanmongkol

Karlkim Suwanmongkol — Fri, 08 Mar 2013 15:42:00 +0000

I couldn’t agree more. Although “it depends” answer can get you frustrated, we are not building software for free. Someone is paying us and hope we will build something that adds business value. If “testing” does add business value (e.g., make design or documentation better) and reduce technical debt that we have to pay in the future, then we should always test.

By: Gene Hughson

Gene Hughson — Thu, 07 Mar 2013 21:57:00 +0000

The death of programming has been 10 years out for at least 30 years now.

Automation of practices like medicine is still in its infancy and the materials there change on a much slower schedule.

By: dotnetchris

dotnetchris — Thu, 07 Mar 2013 21:23:00 +0000

Actually, software will likely be moving that direction. Perhaps still a long ways off from taking a word doc a business person can write and making working software. But software is going to evolve out of moving bits around and instead be about plumbing architecture and architects choosing levels of consistency. The demand for programmers won’t last a decade.