download zip of files only
Wed Dec 04 05:03:38 GMT 2013
From /weblog/software_engineering/testing
Various discussion about debugger Debuggers are a wasteful Timesink - http://www.artima.com/weblogs/viewpost.jsp?thread=23476 The Power of Debuggers - http://beust.com/weblog/archives/000055.html And a lot of links - http://www.infoq.com/news/2007/10/are-ruby-debuggers-harmful I feel the same, most of the time rely on debugger is not that nice - http://iancartwright.com/blog/2009/11/ban-debugger.html Here are the types of debuggers we cover: CLI debuggers IDE debuggers Build you own debugger Heap dumps Historical debuggers Dynamic tracing Production debugging Takipi http://www.takipiblog.com[..]a-debugger-the-definitive-list-of-tools/
(google search)
(amazon search)
Thu Oct 24 02:54:18 GMT 2013
From /weblog/software_engineering/project
Product Owner’s Rule #1: Don’t do everything alone Product Owner’s Rule #2: No rush Product Owner’s Rule #3: Spread the knowledge, use diversity, delegate Product Owner’s Rule #4: Learn and try new things http://www.targetprocess.com[..]/blog/2013/02/product-owner-retires.html How facebook manage code ownership - http://swreflections.blogspot.hk[..]/code-ownership-who-should-own-code.html Product owner checklist - http://larelekman.com/productownerchecklist/
(google search)
(amazon search)
Mon Nov 05 14:29:27 GMT 2012
From /weblog/software_engineering
The way software defects are seen on traditional vs agile projects reveals something about the differences in organizational culture. Given the following causes of defects... Type 1: Programming error Type 2: Misunderstood requirement Type 3: Requirement defined incorrectly Type 4: Discovered requirement http://www.davenicolette.net[..]/index.blog/1590120/defects-and-culture/ Some tips about reproducting bugs - http://swreflections.blogspot.com.au[..]ing-bugs-if-you-cant-reproduce-them.html
(google search)
(amazon search)
Mon Nov 14 17:38:22 GMT 2011
From /weblog/software_engineering
Complete agile from beginning to the end - http://agilewarrior.wordpress.com[..]com/2010/11/06/the-agile-inception-deck/ The methodalogic, and the development team you pick, affecting the process you have - http://www.leanessays.com[..]1/07/how-cadence-determines-process.html More process doesn't necessary solve all problems... in fact it may cause more problem - http://architects.dzone.com/news/process-not-working-must-have http://www.whattofix.com/blog/archives/2006/10/signs_you_have.php You might not be agile if. . . 1. The “Send/Receive” and “Save As” buttons initiate most team communication. 2. Your whiteboards are mostly white. 3. “Test-driven” still refers to your car. 4. You don’t yet know what PHB stands for. (It's the "pointy haired boss" in the "Dilbert" comic strip.) 5. You know that CPM stands for critical path method of project management, and continue to rely upon it. 6. You spend more time trying to manage project dependencies than remove them. 7. Someone still believes in the “Can’t Chart.” (Oops, that’s the Gantt chart.) 8. Developers only develop, testers only test, and managers just manage. 9. Simplicity is presumed to be simple. 10. A change control board meets . . . ever. http://www.versionone.net/Resources/AreYouAgile.asp http://www.jamesshore.com/Blog/Its-the-Software-Stupid.html
(google search)
(amazon search)
|