Now before this happened, I was already a follower of 8th light, Uncle Bob Martin, Craftsmanship, and all that Jazz. It was just a stroke of pure luck that a new CTO came in and brought in the opportunity to work with and learn form 8th light developers.
And Ironically normally, 8th light doesn't typically go to .NET shops and at the time, I was working in an all .NET shop. It was just by luck, that we got a new CTO that came in (another location) and brought in 8th light.
I was working at one of the divisions of the company, while corporate was housed in LA, CA. They brought in a couple 8th lighters to our division and a couple down in LA. I was able to pair with a couple 8th Lighters who came on site at our location day-in-day-out for 5 months straight, every day.
We got stories done with high quality. We didn't rush. We didn't take on more story points than we knew we could take on or that would rush us to complete code. We might not have whipped together and finished 10 stories per sprint, we got probably 8 points done per iteration and done well and done right.
While others rushed to get stories done, or didn't get their stories done because they rushed and got themselves into a mess, we got very small stories done and did not look back. When I say we didn't look back, it means the TDD cycle did what it was supposed to do. It guided us, it allowed us insight into code that you'd otherwise not see if you just skipped TDD and went and wrote a bunch o code without it. And I realized that it really did work, because I was guided by those who have already gone through pitfalls and have gotten Kent Beck's TDD process and intention right.
What we saw was leaner code and naturally high code coverage, just as most TDD practitioners preach. It was powerful and it was transforming to me during that time.
What's too bad is that nobody on my team was interested at the time in pairing with the guys from 8th light. They had heard the preaching of Clean Code, TDD and all that, and knew of Uncle Bob Martin and even attended a couple of his talks. But they decided to ignore the fact that 8th light was on board and continued to carry on providing "code & run business value" plagued with bugs and late night work and worse, did not yearn to learn anything new and here we had one of the rarest opportunities to do just that! Nobody wanted anything to do with TDD. I find it sad, because they really missed out. Here was our employer brining in some of the best minds in the industry and learning and being mentored by them and they wanted nothing to do with it at this division. They said 8th light was "luke warm" yet they hadn't even paired with them to take that temperature in the first place.
And because of this attitude, I didn't however get a chance to apply BDD there because the Architect at that place shot it down and told 8th light in a meeting initially that "no we aren't doing that" with no reason other than "he doesn't like it". He did not want 8th light doing this "BDD stuff" and "8th Light here". So Fitness or any kind of BDD framework or in memory database to isolate tests were both shot down immediately and basically we just shrugged and said ok nicely and continued on with the TDD because 8th light does not back down to TDD and that's a requirement with clients when they sign with them is that 8th light does TDD, that's how they do their work period. So what we ended up doing was straight TDD, and skipped the BDD stuff.
After leaving this company, I took several months off to clear my head. In that time, you tend to loose some of the stuff you learned simply because you weren't pairing anymore daily. There were hundreds of things I wrote down, and about half still stick my head. Enough that gave me confidence that I know somewhat how to do TDD right. But the other 50% that I lost, that is in my OneNote notes, are ones that are kinda hard to go back and read and remember just the situations I was in when I wrote them down when we were pairing.
Now I know the value of BDD. And I'm going back to try to practice it. It's hard when you weren't able to really understand it. Because BDD got shot down, I never got that learning process, and proper learning process through 8th light.
But what I'm here to tell you is that you can get some of these killer insights into TDD and BDD and just good architecture through Uncle Bob Martin's videos, particularly this list is what I suggest to check out first, in this order because this order really gets you into the path gradually:
- Clean Code → Episode 1, Clean Code (Remake!)
- Clean Code → Episode 7, Architecture, Use Cases, and High Level Design
- Clean Code → Episode 6, TDD - Part 1
- Clean Code → Episode 6, TDD - Part 2
- Build an App With Corey Haines → Episode 1, Where Do We Start?
- Build An App With Corey Haines → Episode 2, Finishing Our First Feature
- Java Case Study → Episode 1, Getting Nothing Done
- Java Case Study → Episode 2, Let the Testing Begin - Part 1
- Java Case Study → Episode 2, Let the Testing Begin - Part 2
Don't let the language matter. They did those case studies in Java. What's important is that you will learn proper BDD and TDD and that's what counts.
This took me back right in the chair. It was so familiar the way Uncle Bob and Micah were pairing and the stuff they are sharing in those Java Case studies are as if I was back pairing with the 8th light guys again. Because this is the approach they took with me also. It was amazing...and here I have a reference back to that, a real reference in how we kinda approached things right here in videos from cleancoders.com.
As developers I can't tell you how grateful we should be to Uncle Bob and Micah for taking the time to create these Case Study vids. I can tell you that if you watch, you will gain insight that you can't get elsewhere...unless you were to find others who know TDD well already which is very hard to find or get access to.
These are not free videos. But I can tell you they're not that much and they're well worth the cost. Don't let the word "free" prevent you from trying at least one of his videos. I believe you'll find you'll be buying the rest in my list above and possibly more. This is insight you will not get out on YouTube or other posts, trust me, these are on a league of their own.
Take the time to watch those case studies. Watch them over and over again. There are little subtleties in there that you don't wanna miss along with the explicit things they point out during those vids.
I can't express enough to developers out there the benefits you're going to gain. Buy them. I'm not here trying to sell for Uncle Bob. These vids are highly impactful and that's based on my own experience before I even saw these vids and I can clarify that these vids are definitely impactful because it's exactly what I did when I paired with 8th light. The questions they answer and techniques they bring about, a lot of times answered a shit load of questions I had when I was pairing with them and allowed me to really understand TDD better.
So go watch these videos! TDD takes practice, time, and you must slow down and not give into the thought of rushing. You have to tell your employer that hey, this is something that is worth while. To do that you need to practice and learn it as fast as possible but again that only comes through practice and forcing yourself to stick with it at work for every story you complete at work.
That usually means you will work after hours at first to bridge that gap..because you need to get the stories done but at the same time you don't know TDD. It's hard at first. And this is why I highly suggest watching these vids and coming back to them time and time again as a reference thereafter while you learn and get better at BDD and TDD.
And big thanks to Uncle Bob Martin, Micah Martin, and Corey Haines!