The question above was prompted by a Skype Coaching session I held a couple of days ago. A new tester contacted me and asked me how they might get started with software testing, and what should they do first.
Almost immediately the person who contacted me (I haven't asked their permission to share all the details, or their name, so I won't) asked me questions about automation tools, and what programming languages they should know and work on. I asked them to stop, and I shared my philosophy with them about testing, which should have as little to do with programming as possible. Don't get me wrong, programming is a perfectly wonderful skill, and I dabble in it at times, but I think we do a dis-service to those who want to be testers when we put at the primary requirement "must be a programmer with these skills and history". What I want to know is "how does a person think? What kind of avenues do they follow? Are the random, or do they hand things on a structure that others can examine, review, and comment/critique?"
It was at this point that I decided to ask about something I believe every tester should know, and that's "what do you know about the scientific method?" Yes, for those who have followed me for awhile, you already know that that is one of the topics we are developing for SummerQAmp, but one of the things I wondered was "how could someone actually demonstrate they understand this?" To that end, the question popped into my head, and I figured I might as well run with it.
"What Force Would it take to Shatter an Ice Cube?"
It's a random question, and that's what I wanted, something random and mostly removed from software testing. It's often too difficult to step in and think about making a science experiment out of software, because it feels so intangible. Physical objects, though, are perfect for these though experiments, so I figured we'd use an ice cube as a starting point for the conversation.
What Force Would it take to Shatter an Ice Cube?
How would someone answer that?
They could make a guess.
They could throw an ice cube at a wall and say "that much force"... and they'd be right.... sort of ;).
But if we really wanted to know, at what point, with actual data, could I determine where an ice cube shatters...
We'd probably set up an experiment. right?
What would we want our experiment to tell us?
Could we determine the point where it happens?
How would we do so?
What would we need to make the experiment happen?
How would we make measurements? Do we actually need measurements?
What will our feedback be? What will tell how we are doing?
How are we gathering data?
How would we explain our results?
Can we "defend" our methodology?
What if new information came our way; could we account for that?
Would we need to repeat or redesign the experiment?
I explained that the process of thinking this through, or even setting up an experiment and actually doing it, would inform them more about their own understanding and curiosity of things than any primer on testing I could give them.
I remember last year discussing this for the first time with James Pulley,and how he said that the Scientific Method has to be Lesson Zero for any potential software tester. The more I consider this, the more I agree. Time will tell if the person who started this conversation follows up, but I think if they actually do this, and really think about this process in depth, as well as do some reading on the scientific Method and why it matters (and that it's not helpful for everything), then we'll be quite a ways down the road to understanding some of the foundations of what it takes to even start a conversation on what makes a good tester.
Agree? Disagree? Better experiments to suggest? I'm all ears :).
It's almost Saturday, and it's the end of week three of the current BBST Foundations class being offered by AST. Yeah, I know, I've done this lots of times, but this class is a bit different. First, I think this is the first time a class has run without any input from Cem Kaner, Becky Fiedler or Doug Hoffman, at least that I am aware of. Second, this is the first stint where I'll be taking the reins of the entire monster that is BBST via AST, and from March 31st, 2012, it'll be all mine. That though is both exhilarating, and at the same time, absolutely terrifying.
Let me back up a bit here. For those who are familiar, the Black Box Software Testing classes were a joint effort developed by Cem Kaner and James Bach. The material that is presented was initially written by them and compiled over several years. It's been well researched, field tested, and run regularly for the past several years, always under Cem's watchful eye. Cem recorded all of the videos for the course, a huge undertaking and tremendously time consuming. In short, BBST has been shepherded by Cem and Becky for years. Both Cem and Becky have solid academic credentials, doctorates in different disciplines, and lots of background in academic circles. Still, after so many years, they decided it was time for someone else to handle the AST commitment to the BBST courses. That's where I come in, a guy who took twenty years to cobble together a bachelors degree, who has no higher credentials beyond that, and who, frankly, is much more comfortable speaking "dude" than he ever will be discussing or interacting with academia. Yet AST seems to believe that I'm a good bet for running this initiative, so I'm giving it my all.
Before anyone considers throwing a pity party for me (and really, I ain't asking ;) ), I have to say I've had a great staff this time around. Adriano Comai, Mohamed Lahrech and Ray Oei have been my partners in crime for this go around, and they have done a fantastic job keeping on top of everything, and sometimes that includes telling me when I'm forgetting something. Yeah, I'm their Lead Instructor, but they hardly need me there, to be frank. The group of participants this time around has been great. Sometimes there are challenges and clashes of personality (testers being difficult and nit picky?! Perish the thought (LOL!) ). Seriously, it's been a great group, and they've really been great.
Tomorrow at midnight, our final exam will be posted, and then we'll see if I and my band of brothers have pulled this off. It's scary to know you are taking over something that has been run by a man that's considered a legend in the testing community. For those about to head into the final exam, I wish you good vibes and I look forward to seeing your answers and commenting on them. For everyone else considering if they want to take any of the BBST classes, I of course hope you will. While I can't promise to be your instructor (though there's about four times this year that will be a good bet ;) ), I believe the volunteers who teach these classes are great, and I think your being involved with them will make for a very worthwhile month of your time. We may not be perfect, but we give it our all, and I think you'll see that.
It's amazing to think that 2011 is almost over, and yes, while last year I lamented writing the obligatory "year that was" letters and somewhat lampooned them with my post last year titled "Well, How Did I Get Here?", that post resonated with many people. It is to date my most read and my most commented on article here on TESTHEAD, depending on which metrics you believe. Based on the response to that post, I decided this year to just let it be known, this is a recap of the World of TESTHEAD, and the world of "Michael Larsen, Tester" for the year of 2011. The title this year is indeed, again, in homage to the seminal 1980 Talking Heads classic "Once in a Lifetime".
2011 was a year of transition for me personally. I took many leaps of faith this year, and as the title says, I willingly jumped into new areas and new responsibilities. Early in the year, I ended my employment with Tracker Corp, bringing to an end six years of learning, camaraderie and a focus on the .NET world of software development and testing. In exchange, I came to Sidereel, and a world of learning, camaraderie and Rails software development. This is telling, because I'd never worked with Rails before, and my involvement with Ruby prior had been from recommendations from co-workers that it would be fun to learn. Well, now it was more than "fun to learn", it was an occupational hazard (and necessity :) ).
With that, I started mapping out and learning a new site, a new programming language, a new model, a new way of storing data, and very different approach to developing software. I was no longer just a tester, I was to integrate with a fully Agile development team and work with and alongside of them. Oh, and I traded in a daily diet of Windows and PC's for a daily diet of Mac OS X and Darwin UNIX all sleekly wrapped in a Macbook Pro. Oh UNIX, how I have missed you!!! There was just something comforting about leaving behind the world of MSI and EXE files and embracing tools such as ruby gems, homebrew and other options for installing software. Scriptable, customizable, and where Test Driven Development and Continuous Integration were not obscure buzzwords but actual practices that were, well, practiced! It's also been telling, humbling, and intriguing to learn about and use tools like Ruby, RSpec, Cucumber, Capybara, Selenium Web Driver and other areas of automating testing. I can safely say I have written more code this year than I have in the past 17 years prior!
2011 also saw the process of Weekend Testers Americas come into its own. What could have been a few experimental and jerky first few sessions got smoother, cleaner, and better understood, and we had some great successes during the year. While I'm not sure how much others have learned, I know that I learned a great deal from this process. What was great to see was that this initiative was embraced by people all over the world, and our participants reflected this fact, including testers who would come into our sessions at 12:30 AM (yes, after midnight) from India to participate. First off, that's dedication, and my hats off to everyone who did that, but more to the point, it spoke volumes about the service we were offering and the fact that people wanted to come in and participate, even at those insane hours. We had some help from some heavy hitters, too. Michael Bolton and James Bach both came in to guest host some of our sessions ("Domain Testing" and "Creating Testing Charters"), and Jonathan Bach helped me craft one of my breakaway favorite test ideas of this year, that of "Testing Vacations". In all, it was a banner year for Weekend Testing Americas, and I am so thankful for all of the participants that helped make it possible. I'm especially thankful for Albert Gareev, who in addition to being a regular participant, stepped up to become my partner in crime for this enterprise, and frequently helping me develop new ideas or take the process in different directions than I probably would have had I been left to my own devices.
2011 was a year of meeting and developing relationships with other testers. In January, I met Matt Heusser in person for the first time. As many of you know, one of my most involved and enduring professional relationships was with (and continues to be with) Matt. I produce the "This Week in Software Testing" podcast with him. I helped write a chapter for a book he was the principal editor for (more on that in a bit). I also was a sounding board for other ideas and offered several of my own in return. I had a chance to meet my fellow Weekend Testing Compatriots Marlena Compton, Markus Gaertner, and Ajay Balamurugadas in various places. Marlena and I had the pleasure of live blogging the entirety of the Selenium Conference from San Francisco, with our comments getting us branded as the "Table of Trouble" from the other participants. That was a fun memory, and it helped to set the stage for liveblogging other events throughout the year. Geting the chance to meet so many testers during this year in various capacities was a real highlight and much enjoyed aspect.
2011 also saw my commitment to being published. I made a decision that I wanted to write beyond the scope of TESTHEAD. As will probably come as no surprise, my first few articles were Weekend Testing based. However, I had the opportunity to venture into other topics as well, including two cover stories for ST& QA magazine; one being my article about "Being the Lone Tester" and another an excerpt of my chapter from "How to Reduce the Cost of Software Testing". Speaking of that, 2011 saw me and 20 other authors get our names in print and become book authors. It was a pleasure to have the chance to write a chapter for "how to Reduce the Cost of Software Testing". A later development, one in which I, literally, just got word about and accepted, was a potential new book that discusses "The Best Writing in Software Testing". I have agreed to be a junior editor for this project, and we are aiming for a 2012 release of this title. In addition, I also published articles with sites like Techwell, the Testing Planet and Tea Time With Testers. As of now, I have eleven articles that have been published external to TESTHEAD, and it is my hope that I'll be able to write more in the coming years.
2010 was a first in that I attended my first testing conference. I made the commitment then that 2011 would be the year I would present at a testing conference. I received my opportunity to do exactly that. My first ever conference presentation was just 20 minutes, and it was at CAST 2011. I presented in the "Emerging Topics" track and discussed Stages of Team Development lessons I had learned from Scouting, and how they could apply to Testers. All in all, it went well, and even today, I still hear from people who said they appreciated the topic and liked my presentation. In addition, I also gave another full track session at CAST called Weekend Testing 3-D, where not only did i discuss how to facilitate Weekend Testing style sessions, we actually held a live session with participants from all over the world, and processed it in real time (this was the earlier mentioned "Testing Vacations" session that Jonathan Bach helped me develop. In addition, I proposed a track talk and paper for the Pacific Northwest Software Quality Conference titled "Delivering Quality One Weekend at a Time: Lessons Learned in Weekend Testing" and after writing the paper and having it reviewed several times, received the nod to present it. However, fate struck, and I broke both bones in my lower leg (tibia and fibula), thus preventing me from delivering the talk (the organizers of PNSQC, however, still included my paper with the proceedings). Additionally, a friend who felt bad that I couldn't present at PNSQC forwarded my paper to Lee Copeland, the organizer of the STAR conferences. Lee liked the paper and asked if I'd be willing to present it at STAREast in April, 2012. I of course said YES! So I will get my chance to present this paper yet :)!
There is no question that I learned a great deal from the TWiST podcast, both as a producer and as an active listener, but 2011 will be even more memorable in that I graduated from editing the show and as an occasional guest to being one of a handful of rotating regular contributors on the mic. It's been interesting to have people email me and say "hey, I heard your interview last week, that was a great show and a great topic, thanks for your comments and explanations". I thought it was especially cool when I had someone say that they felt that I'd make a great game show host (LOL!).
2011 saw my continued focus on working with the Miagi-do School of Software Testing. At CAST 2011, a number of us Miagi-do Ka, including Markus Gaertner, Ajay Balamurugadas, and Elena Hauser worked along with Matt Heusser at the CAST testing challenge. During that competition, I had the chance to show Matt and the other testers there what I was able to do, and due to that experience, Ajay, Elena and I were awarded our Black Belts. While the experience itself was great, it also came with the expectation that I be willing to mentor and teach other testers, an opportunity that I have gladly taken on and look forward to doing more of in 2012.
One of my most active projects for the year of 2011 was helping to teach the Black Box Software Testing courses for the Association for Software Testing. I had the opportunity this year to instruct, as either an Assistant or as a Lead Instructor, all three courses offered in the BBST series (Foundation, Bug Advocacy and we just completed the pilot program for Test Design on December 10th). I was in this capacity that I was also nominated to run for the Board of Directors for the Association For Software Testing. I never envisioned myself being a Director of anything, much less an international software testing organization! Still, someone in the organization felt I deserved a shot, and nominated me. What's more, someone else seconded it. Even more amazingly, a lot of people (perhaps many of you readers) thought I'd be a good fit for the position as well, since I was indeed elected to serve on the board. My two year term began in October. While daunting, it is also exciting to think that I may actually help shape the future of this organization in the coming years, and to help represent my fellow testers. Believe me, it's not something I take lightly.
Quite possibly the biggest "Into the Blue Again" moment of the year, though, happened at our first AST board meeting in October. It was at that meeting that Cem Kaner and Becky Fiedler announced their desire to have someone take over as the Chairman of Education Special Interest Group. While a part of me felt I was wholly inadequate for the task, another part of me felt that this was something essential and that it needed someone to spearhead it so that the education opportunities within the organization could be championed and further developed, while allowing Cem and Becky the opportunity to do what they really wanted to do, which was develop more and better testing courses. With that, I offered to chair the Education Special Interest Group. I'm not sure what was more surprising, the fact that I offered, or that the rest of the board took me up on it! Two years ago, Cem Kaner was a man whose books I had read and whose presence loomed large as a "testing guru" on high. The thought I would ever meet him seemed remote. The thought I'd actually take over for him and spearhead an initiative he championed never even crossed my mind!!! Still, that's what has happened, and I guess 2012 and beyond will tell us what I actually did with it. I'm hoping, and working towards doing, all I can to prove worthy and up to the task.
2011 was, really, a year where I took leaps of faith, lots of them, and discovered that I could do even more than I ever imagined I could. I've shared may of those journeys in TESTHEAD posts, and I thank each and every one of you who are actively reading this blog for your help in motivating me to take these leaps of faith. It's been another banner year for me, both in learning and opportunities. Overall, the experiences of the past year have given me confirmation that, if I were to jump "Into the Bue Again", that it would be a great chance to learn and grow, regardless of whether or not the outcome were necessarily successful, lucrative or advantageous. Granted, most of them have been, and those that haven't been, well, I'd like to think I failed quickly and early enough to learn from those experiences and correct my trajectory. Time will tell if that's true, of course. As in all things, there were many people that helped make 2011 a banner year for me.
Thanking a bunch of people is always fraught with danger, because invariably someone gets left out, and there have been hundreds of people who have been instrumental in making this a banner year for me. Still, there are many that stand out, so to that, my heartfelt thanks to Adam Yuret, Ajay Balamurugadas, Albert Gareev, Alex Forbes, Anne-Marie Charrett, Ashley Wilson, Becky Fiedler, Benjamin Yaroch, Bill Gilmore, Cem Kaner, James Bach, Janette Rovansek, Jason Huggins, Jon Bach, Lalitkumar Bhamare, Lee Copeland, Lynn McKee, Markus Gaertner, Marlena Compton, Matt Heusser, Orian Auld, Rick Baucom, Selena Delesie, Shmuel Gershon, Terri Moore, Thomas Ponnet, Timothy Coulter, Will Usher and Zach Larson. Thank you all for helping me make those leaps of faith. More to the point, thank you for having the faith in me that I'd be able to actually do what you believed I could do! Thank you for what has honestly been, at least as far as software testing is concerned, my greatest year (and remember, last year was pretty awesome, too. I didn't think I'd be able to top that!).
Here's to an every bit as exciting and fun-filled 2012. I'm looking forward to seeing where I might leap next :).
Well, now that it's been announced to the students in the current AST Instructor's Course, I guess their's no reason to not mention it here. While I was in Madison a couple of weeks ago for the AST Board Meeting, one of the orders of business was the need for someone to take over as the Chair of the Education Special Interest Group (EdSIG) within AST. I'd heard of this need for quite some time, but I kept my mouth shut, because, really, what do I now about Education? I'm not a teacher (well, not really), I certainly don't have any academic credentials, or any fancy title to go with my name. I certainly don't have much in the way of academiese in my vocabulary; I'm much more comfortable speaking "dude".
Yes as I kept think about the situation and the needs, I realized that I may actually have more of an understanding of these things than I gave my credit for. I finished my Bachelors degree, my last two years, entirely online via distance learning courses. I went through 22 online courses of varying quality levels and went through a total immersion process to get the most out of them. Were they exactly like university classes held on campus? Nope, but they had their own interesting challenges, and I'll dare say I learned quite a bit from all of them. I realized that this experience dovetailed well into the way that AST delivers the BBST Classes through online facilitation.
What's more, I was one of the few people who has taught Foundations and Bug Advocacy, and was participating in the pilot program of the Test Design class (which starts next week, btw, and yes, I'm excited to be participating in it :) ), plus I'm scheduled to help teach the March session of the Test Design class. Who else could say they've been teaching all three of the classes (well, OK there's a couple others, but I was one of them)?
As I mulled these over in my head, I decided to do something brave or crazy... time will tell on that one :). By the time we reached the end of the discussion, I decided that there needed to be a Chair for the EdSIG... and if no one was going to step up to the plate, well why shouldn't I throw my hat in the ring? So that's exactly what I did, an for better or worse, the board accepted my offer :).
So over the next few months, I will be learning the ropes of what the EdSIG entails, but most specifically how to administer and run the BBST course series for AST's members and participants. That's a big chunk of where my involvement will be, and due to that, it means my direct involvement as a regular instructor will likely diminish (though I'll still be involved with all of the classes). What this does mean is that there will be a need for more instructors to help teach. We have a fresh cadre of newly minted Certified Instructors for courses, and it's my hope that they will step into the role of helping teach the upcoming classes in 2012. It's also my hope that many of you out there will consider taking the classes if you haven't already, and help me to deliver the best software testing training to be found anywhere on the planet (that's a bold boast, I know, but I happen to believe it :) ).
So by Midnight Pacific time tonight, the last official actions of the Association for Software Testing's Black Box Software Testing Foundations class (well, this one in any event) will conclude, and with it, my second voyage as a lead instructor.
In some ways, this was a more challenging class than the last time I was in this position, not the least of which was the fact that I watched and worked with this class from the confines of my bed for the first three weeks. Only this past week have I been up and about enough to be more active and involved. Thus, I have to say up front to my participants, if I was not as involved as you would have liked or expected, I do apologize.
This is now the sixth time I've worked with the Foundations class. Once as a regular participant, three times as an assistant instructor, and two times now as lead instructor. Every class is different, and every class has different challenges and different surprises. The fun part is to see which participants just go along with the class and the flow, and which ones really get involved and just tear it up. The other interesting aspect is that, as I've participated in the courses over time, and in the broader testing community, I am having more participants come in that I have either a correspondent relationship through sites like Twitter or Facebook, or those that actually work with me on endeavors like Weekend Testing. Usually it goes the other way around, where participants come and take part in Weekend Testing. This time the tables were turned, and I got to have my cohort and fellow WTA facilitator Albert Gareev in my class. I think this is the closest I've yet come to someone I regularly interact with on a peer level actually being a "student" of mine, and in a way... it's odd (LOL!). I've been told by other instructors that as times goes, this actually becomes more and more common, so I guess I better get used to it :).
This was a lively group, and there have been some great participants. I've learned a lot from them and their enthusiasm and energy, as well as their areas and places where they struggled or had questions. I know, I say the same thing at the end of every class, so I know I run the risk of sounding trite, but really, each class gives me a new lens to view the course material. I come out with another insight on subjects that some might consider to be "rote". At least for me, it doesn't become rote because I get different perspectives and different impassioned comments from participants, and that helps to keep it all fresh.
I've been taking notes, and I see a number of people in the course that I think might well be good instructors later (I'll not name names, but it's no secret that we often find instructors from the ranks of the participants... heck, that's how I got involved :) ).
So what's next for me? Well, the Instructor's Course is next...wait, what?! Yep, it's true. Because of varying factors, each time the Instructor's Course has been offered, I've either been unavailable or it had to be canceled. Normally, to be a Lead Instructor, you have to have gone through the class, so I'm an outlier, but I committed to get that resolved as soon as possible. For others who are interested, there may well still be room, so if you want to join me in the class, head over the the main site and sign up :). This will also be the last Foundations class for this calendar year. The next one will be held in February of 2012, and as of right now, I'm scheduled to teach it!
I've had a great time being the Lead Instructor for this Foundations class, even with my challenges this time around, and I'm hoping my participants have likewise enjoyed the experience. Thanks for teaching me a lot more than I probably taught you :). Also, my thanks to my co-instructors Selena Delesie and Brian Osman, and as always, much thanks to Cem Kaner and Becky Fiedler for their support, encouragement and guidance when I needed it. It's been a fun ride!
So last Saturday, I had the chance to bring to a close my first AST BBST Foundations class with me as the Lead Instructor. This was a cool experience in the sense that, while I've been part of this class for five iterations, this was the first time where I was setting the pace and the expectations.
It's a strange feeling. On one hand, after five times through Foundations, I figured this would be easy to do, but the truth is, there's a lot to keep track of and try to keep everything on track. For those who've taken the class, this may seem obvious, but for those who haven't, this is not an easy class. There's a lot to learn, to accomplish, and to encourage other students to work together over a surprisingly short period of time. It's a month long, but that month flies by very fast.
Each class is different, in the sense that each group of participants brings their own experiences to the course, and as such, each sees things a little bit differently. Each class, it seems a different set of questions develop as people determine the answers for the questions in the class. Oftentimes, I feel inadequate to answer those questions. Not because I don't understand the questions, but because I understand the questions as they relate to me and my experiences. My breakthroughs are mine, and other people's breakthroughs are theirs and come in their own time. My frustration is that, try as hard as I might, I can't teach someone anything they themselves aren't ready or willing to learn.
I remember as a kid reading Guitar Player magazine. Back in 1980, when I was 12 years old, I read an interview with Lesie West (legendary blues rock guitar player in the 70's who went on to teach guitar in New York years later). Leslie said something that I have been thinking a lot about lately... he said "I can't teach you how to play guitar. I can show you how to play guitar, but that's it. I can teach you how to teach yourself!" I had that experience during this class.
Now, don't get me wrong, it's not like we had a bunch of people who were not already good at testing (yes, there were many different levels of experience, some long time practitioners balanced out by some junior testers, as always). What was clear, though, was that the class offers a framework for testing and understanding testing, and each person approached that framework a little bit differently. Were I to take the idea that I would teach them, then I would be teaching them my understanding of it. That's not the point, though, as the challenges I face are not the same ones they will face. The tools and the approaches are context driven, and understanding the context (I believe) is important.
I deal with a podcast each week, and literally each one I produce, I learn some new trick or method that helps make that one better than the week before (subjectively speaking, of course). After more than 40 podcasts, I find it interesting that I still learn some new trick each time I do it, often when I'm doing something I've done dozens of times. Why is that? Is it because I've suddenly become aware of something that was obvious before, or is it because I experimented with something, saw the results, and finally put 1+1+1+1+1 together? I think it's more of the latter, because we are learning at our rate, and often that rate will be different for different people, because they will focus on what is relevant to them over everything else. The other details are nice and interesting, but they will not be at the forefront of my mind if I'm not actually doing something with it beyond curiosity.
This is a long winded way for me to say that I've had a great time being the Lead Instructor for Foundations, and I'm happy that my participants enjoyed and learned through the experience. Whether it was because of me or in spite of me will remain to be seen (and is ultimately irrelevant, really). I think you all were awesome, and it was a pleasure and a privilege to lead your class. I hope to see you in future classes, and thanks for teaching me a lot more than I probably taught you :).
This Saturday, in addition to a session of Weekend Testing Americas, another session of the Association for Software Testing'sBlack Box Software TestingFoundations class will begin. It will be another four weeks of all volunteer effort, with a number of dedicated instructors helping to teach the class. It will be challenging, it will be fun, it will be a chance to learn even more than I already have from this great class, and this time I will probably learn more than all other times combined. Why you might ask? Because I'm going to be the Lead Instructor for this course!
I am excited and anxious about this turn of events. Excited because I want to see how well I can do in this environment, but anxious because I'm going to be the guy in the driver's seat this time. there's a lot that goes on behind the scenes for these classes to run smoothly, and a lot of the details associated with the class running smoothly are because the lead instructor makes sure to take care of many of those pieces. In previous classes, those responsibilities belonged to someone else. This time, they belong to ME!
However, I am not alone in this endeavor. I have two great assistants this time around (Mimi Mendenhall and Doug Hoffman). Mimi will be doing it for the first time, and Doug has been around since the courses were first offered, and could probably teach this class in his sleep (LOL!).
Registration is still open until Wednesday, 3/30/2011, so if you are interested in seeing if you can still get into the class, please follow the link to register and take part. If the class is over-booked, you can of course sign up for the next one. I may not be teaching that go-around, but it will still be a great class with whoever is teaching it. If, however, you can get in, I'll look forward to having you be a part of my class :).
