News for hackers. Stuff that matters.

A comment on Ego-Driven Development. Parent comment

Re:Ego-Driven Development by scottschulthess on Monday October 01, 2012 @04:33PM (#4599202)
Well usually we fix them as they come in. Continuous deployment FTW - weekly releases create a whole lot of baggage.

Other than that, I will just throw stuff in Trello, so I don't really have a bug database per say

[ Parent | on HN ]
Re:Ego-Driven Development by MartinCron on Monday October 01, 2012 @04:58PM (#4599303)
I was actually mocked at a FogBugz/Kiln event for being the only developer in the room not using a Bug Database.
[ Parent | on HN ]
Re:Ego-Driven Development by king_jester on Monday October 01, 2012 @05:50PM (#4599537)
I'm curious about this. What do you do when you encounter bugs that have a longer fix period, say several days to a couple of weeks? Do you stop new development or are you dedicating part of your team or team's time to only working on bugs?
[ Parent | on HN ]
Re:Ego-Driven Development by samspot on Monday October 01, 2012 @04:38PM (#4599223)
I consider trello to meet the minimum criteria for a bug database, I use agilezen for this purpose on one project.
[ Parent | on HN ]
Re:Ego-Driven Development by dockd on Monday October 01, 2012 @05:27PM (#4599435)
How is fixing bugs as they come in different from "fixing bugs before writing features"?
[ Parent | on HN ]