This topic has been in my mind for a while now. I think I want to start a series and write down thoughts from different angles on how to deal with this issue. First thought that came to mind. DON'T DO ANYTHING DRASTIC. That's it. Just
I was telling one of my friends how our company is basically all online. Our accounting is hosted, payroll is hosted, email is hosted, documents are hosted, so even if all of our laptops all burnt down on the same day, our business goes on as usual (Mostly). So his
Sure, I sure think it's good for me. For us, every since we left the IBM camp almost 5 years ago, we were either doing Oracle/BEA, or Open-source. So Oracle and BEA becoming one company is just going to make things easier for us, actually making
So the question is, can we apply J-RAT to GUI Centric Testing? By now we all agree that having all different functional area in the same room during testing increases productivity big time when testing process centric code. Can the same be done for GUI Centric testing? The problem
Found this in my email and fee like I should repost to my blog I've been an Architect for many years and code review is always something that is difficult to do right. I have tried from formal code review meetings to reviewing CVS check-ins daily, to
During system test, it's usually very hard to gauge progress. Most teams are still using the percent complete (how much have you tested) to report progress. While that's easy, that usually does not tell you correctly where you are. Today I am starting to use the
So questison of the day over lunch is my standard: what would you do if you are rich. Most people said they have specific things they will do, like travel the world, ski, ride bike. Me? I will probably be funding other people's dreams. I think it will
After day 1, we are doing great. 3 concurrent threads of work was going on in the room. We were getting the database ready, regression testing the code, and migrating data. Remember, J-RAT's entry criteria is that System Testing is done. So we need to make sure
So there you go. I'm starting to Blog about the J-RAT process. Two days ago we started our new J-RAT process. Putting 10 people in one room (2 developers, 1 DBA, 3 Testers, 2 BAs and 1 accountant, 1 Architect) and start intensive, business centric testing.