Comments for Software Bloat

Comment on The Making of Watchdoggie – Part 1 (Business Development) by The Making of Watchdoggie – Part 2 (Implementation Details)

The Making of Watchdoggie – Part 2 (Implementation Details) — Sun, 14 Feb 2010 03:01:14 +0000

[...] « The Making of Watchdoggie – Part 1 (Business Development) [...]

Comment on SoftwareBloat TV – Episode 2 by Dutch Boyd

Dutch Boyd — Sat, 30 Jan 2010 09:20:57 +0000

Would like to see Software Bloat TV #3… on a side note… when did you turn into such a mac-luver-hippie? LOL. More PC-love please.

Comment on SoftwareBloat TV – Episode 1 by Dutch Boyd

Dutch Boyd — Sat, 30 Jan 2010 08:39:51 +0000

That was pretty cool!

Comment on SoftwareBloat TV – Episode 1 by Woopra » Woopra Video and Tutorials Highlights

Woopra » Woopra Video and Tutorials Highlights — Wed, 27 Jan 2010 09:28:06 +0000

[...] SoftwareBloat TV – Episode 1 – Woopra [...]

Comment on SoftwareBloat TV – Episode 2 by Dotz

Dotz — Sun, 24 Jan 2010 00:51:16 +0000

cssedit=kewl!

Comment on Continuous Integration Blueprints: How to Build an Army of Killer Robots With Hudson and Cucumber by Karl Baum

Karl Baum — Fri, 08 Jan 2010 22:02:41 +0000

Anybody able to nicely integrate cucumber output with hudson? That would be killer.

Comment on Book Report: Letters To A Young Mathematician by Russola Granola

Russola Granola — Fri, 06 Nov 2009 16:26:21 +0000

That sounds like a pretty cool read.

Comment on The Virtues of Version Control by The Virtues of Version Control — Presentation « Software Bloat

The Virtues of Version Control — Presentation « Software Bloat — Fri, 14 Aug 2009 20:48:12 +0000

[...] This is a presentation I gave at our local developers meetup. It’s based on an earlier post of mine from here. [...]

Comment on Continuous Integration Blueprints: How to Build an Army of Killer Robots With Hudson and Cucumber by stefan

stefan — Sat, 04 Jul 2009 20:27:12 +0000

Nice writeup, thx, that got me started, but what about the next step?!

The build fails the way it should be, when a feature doesn't go through. But to find out which feature failed, you have to go into the console-output. For the normal rails-tests get a decent, clickable report of the test-results - It would be nice to get a similar output for the features/cucumber: Does anyone have an idea how to set this up?!

Comment on The Virtues of Version Control — Presentation by :)

:) — Thu, 21 May 2009 16:14:45 +0000

i am now a version control master, thank you robert boyd.