Wednesday, June 30, 2010
Monday, June 28, 2010
Friday, June 25, 2010
Wednesday, June 23, 2010
- doing something and seeing what happens
- predicting future events
Tuesday, June 22, 2010
Thursday, June 17, 2010
Wednesday, June 16, 2010
- Describe what you're trying to do. Give the user some context so they don't suggest something that makes no sense. Don't take more than about three sentences to do this, at most.
- Indicate you've tried something. This does two things: (1) shows you're trying; and (2) prevents people from suggesting something you've tried.
- Ask a question. Make sure you actually ask a question. Be as specific as possible in describing what you need to move forward.
Monday, June 14, 2010
- Our login page asks for "username" but we expect you to provide an email as your username. People keep clicking "Forgot username", so we should document that your username is the email you signed up with.
- When patching the high-availability system, support must patch the passive half of the pair first. Patching the active half first leads to system downtime. We should document that for support.
- We can register our system in DNS at installation time (go us!) but only if you provide the username and password of someone with permission to do so.
Thursday, June 10, 2010
- Update a script that spit out information in rows, and I always wind up sending that information to other people in columns. I made it spit out columns. Total time saved: 30 seconds, tops, but boy was that annoying having to transpose it. No more transposing!
- Upgrade all my Rails gems. I'm just starting on a new project, and using the most current ones will be useful later on.
- Update the Abakas web site with some clearer services information.
- Install Transmit 4, which is a lot faster than the previous version.
Tuesday, June 8, 2010
- a GUI
- SOAP and REST APIs
Monday, June 7, 2010
Friday, June 4, 2010
- Makes you sound rather whiny
- Makes the person more likely to do it if only to prove that yes, they can
- Makes the person more defensive of his position
Thursday, June 3, 2010
Attend CAST 2010
The 5th annual Conference of the Association for Software Testing
August 2-4, 2010, Grand Rapids, Michigan, USA
"Skills in Testing"
CAST reflects the AST's core mission: to build community amongst scholars, practitioners, and students for the advancement of the practice of software testing. In 2010, CAST aims to leverage peer collaboration to build an enhanced understanding of how various skills influence tester effectiveness.
CAST offers a unique opportunity to learn and confer with others that simply isn’t found at other conferences. Each scheduled session allocates time for facilitated “open season” discussions that encourage participants to question and challenge the presentation. What takes place in the hallways, at receptions, and during meals and lightning talks truly sets CAST apart; for many attendees, the greatest value is derived from the opportunity to discuss and delve into the topics that matter to them.
More information and Registration: www.CAST2010.org