tedogrady.blogspot.com
Ted O'Grady on Agile Development: Art in Calgary Alley
http://tedogrady.blogspot.com/2007/07/art-in-calgary-ally.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Friday, July 27, 2007. Art in Calgary Alley. Posted by Ted O'Grady at 11:52 AM. Links to this post:. Fixing one of the things that bugs me. Where have I been? Performance tuning in ernest. The Mythical Man Month. Gerard Meszaros Test Automation. Toplink In Memory on Sf. View my complete profile.
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Discussion on coupling...
http://tedogrady.blogspot.com/2006/09/discussion-on-coupling.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Tuesday, September 05, 2006. This categorized how I try to work:. Http:/ codebetter.com/blogs/david.hayden/archive/2006/08/26/Over 2D00 Architecting-Via-Pure-Fabrication-and-Indirection-to-Reduce-Coupling.aspx. Decoupling has a cost associated with it. Posted by Ted O'Grady at 4:45 PM. Links to this post:. Stepping up to the plate. Great people and Great tools.
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Smalltalkers
http://tedogrady.blogspot.com/2006/07/smalltalkers.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Wednesday, July 26, 2006. Having been reminded that I'm an old dude. Http:/ www.josephmoore.net/2006/05/visual-studio-ruby-on-rails-and-old.html. Courtesy John Duimovichs Blog. Posted by Ted O'Grady at 7:54 PM. It could be worse though, your nickname could be the 2 minute man. That guy knows Java. He's an Old Dude! Links to this post:. Its a different safety net.
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Something to try...
http://tedogrady.blogspot.com/2006/09/something-to-try.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Sunday, September 17, 2006. When I read a book that I think is good, I like to try a few things out of it that you normally wouldn't (Why did you read the book if not to learn something new? I think the question to ask is "When will x be ready for production? Where x is contracts, volumetrics or allocations. Posted by Ted O'Grady at 2:08 PM. Links to this post:.
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Ghosts in the wood
http://tedogrady.blogspot.com/2007/08/ghosts-in-wood.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Monday, August 27, 2007. Ghosts in the wood. Posted by Ted O'Grady at 10:07 AM. Links to this post:. Art in Calgary Alley. Fixing one of the things that bugs me. Where have I been? Performance tuning in ernest. Gerard Meszaros Test Automation. Toplink In Memory on Sf. View my complete profile.
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Performance tuning in ernest
http://tedogrady.blogspot.com/2006/10/performance-tuning-in-ernest.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Wednesday, October 25, 2006. Performance tuning in ernest. Up until this point we have been performance tuning for testing. Our users have been testing the application all along, and our goal has been to keep them happy with the performance of the system (not ecstatic). Production accounting has a few unique attributes to it:. Second: Accountants have four (impor...
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Usability Cobwebs
http://tedogrady.blogspot.com/2006/07/usability-cobwebs.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Wednesday, July 26, 2006. Having fun with Lu and John on the project sorting out how to make our help more usable. Building paper mock ups, figuring out our users, identifying core tasks and generally having lots o fun. Posted by Ted O'Grady at 8:02 PM. Links to this post:. Its a different safety net. Blogger is pissing me off. Vlad: On risk and performance.
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Which Profiler?
http://tedogrady.blogspot.com/2006/10/which-profiler.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Saturday, October 28, 2006. Ted,What are you guys using for a Profiler? If you have any advice on a profiler. Or, more importantly, common areas a profiler flags, I'd love to hear them.". For exploratory work (has the problem of dilation). For precise timings (basically println). For understanding the cache and gross database numbers. Math and common sense. It's ...
manodeep-researchwork.blogspot.com
A Making of Software Professional: October 2008
http://manodeep-researchwork.blogspot.com/2008_10_01_archive.html
A Making of Software Professional. Record of my journey towards a Software Professional. Tuesday, October 28, 2008. Cockburn, A. (2002). Agile Software Development. Fowler, M. (1999). Refactoring Improving the Design of Existing Code. Freeman, E., Freeman, E., Sierra, K., and Bates, B. (2004). Head First Design Patterns. Gamma E., H. R. (1995). Design Patterns Elements of Resuable Object-Oriented Software. Kerievsky, J. (2005). Refactoring to Patterns. 2), 126 - 139. Portland, Oregon, USA: ACM. Experienc...
tedogrady.blogspot.com
Ted O'Grady on Agile Development: Fixing one of the things that bugs me...
http://tedogrady.blogspot.com/2007/05/fixing-one-of-things-that-bugs-me.html
Ted O'Grady on Agile Development. The diary of an Agile team lead. Thoughts I have had about and around my projects that I need to ruminate on. Wednesday, May 30, 2007. Fixing one of the things that bugs me. One of the things that bugs me is how long it can take to set up the infrastructure for a small project. Purchase hardware, install OS, configure OS, CVS, bugzilla, webserver, cruise control, and, oh yeah, backups. Oh crap don't forget security. Why do I need to do all this work everytime?
