Sorry I've not responded to messages in here for a while. I've just been bogged down with a lot of stuff at work, and as I said previously, I'm doing a presentation next week that's quite important for me, so I really need to focus on that as well.
I did say originally that this project may take a long time to work out, because we all have our own priorities and obviously nobody is getting paid for this, so it will be a longer term thing rather than a quick win. I'm also aware of the fact that I said I'd make some short Git videos and haven't yet. I'm still planning to do this, but I obviously need to priortise certain things first. I sent out an email to a bunch of people in work last week, and it really snowballed in a way I wasn't expecting. What I thought would be a presentation to 5 people or so has turned into something a bit bigger, and I really need to make sure it's quite well polished now.
In one sense though that's a good thing for everyone here, as it's a presentation on some of the details of test driven development, so it may come in handy when I go into it with you guys.
In terms of the spec as @drt_t1gg3r pointed out, we don't have one yet. What I was hoping to do is to have a conversation with @lyndsay about that at some point, and we'll start working out the details.
I'm quite a big believer in Agile development, which goes against the traditional "big design upfront" methodology that a lot of us are used to. Ideally I'd want to have a few conversations about what we should be aiming for, and then the general idea is that we focus on small incremental features, bit by bit, all the while using feedback from the stuff we've built to make sure we're on track - this way we can adapt the plan quickly at a moments notice. The idea is that you stay focused on what matters and what adds value, as opposed to creating a great big plan upfront that may not really represent what you or your users actually want or need. I'm a big believer in combining this agile methodology with test driven development, but it's really hard to explain this stuff in an abstract way, so it's best to get down to concrete examples I think.
I'd say let's all remember we're doing this for fun and we need to accept it's a long term thing. I wanted to be working on this a lot, but things do get in the way a bit. I would say though that once we're clear on the rules of TDD + Git + our Github workflow, in theory at least, other people should be able to chip in without much red tape in the way.
My presentation is a week on Friday (sounds like a long way away, but it's 1 1/2 hours long and some of the big bosses in my organisation are going to be there, so I really need to get this right), and I've also got some general work I need to do in the meantime. On the flipside, my girlfriend and daughter are going away for two weeks to visit family (I couldn't get the time off) from this weekend, so I may have some more spare time coming up that I can use for this.
I'd like to have a go at creating the short (15 minutes or so) Git video first, and then perhaps we can start talking about the next group session? I'd like it to be on github/git workflow and code reviews if possible?
Let me know what you think. I can't give a solid date right now, but early next week I should be able to start committing to some dates.
@mantis sorry for missing out on the spare time you had (I know you said until the start of Sept worked well for you) - hoping you can come along to some future group chats?
By the way guys, a lot of the purpose of this is to produce a learning exercise for all of us, including myself, so even if we don't fully get there, hopefully the stuff we cover along the way will be useful to all of us. Learning a really nice git workflow is a really valuable thing for any developer or designer in my opinion, and the test driven development stuff is sensational in my opinion. It's been nothing short of a revelation for me since I've been working in my current job for the past year. I typically hint at the stuff I do for a living, although some people on here know already, but I'll say I work on the BBC Sport website, so that gives you an idea of the scope of the work I do. I really believe in the idea of sharing knowledge and constant personal improvement, which is why I'd like to do this project with you guys. I believe I'll learn lots of stuff along the way as well. It's all good fun.
Funnily enough, I spent today, and will spend tomorrow, on an "Advanced TDD" course in work - it's been really interesting so far, and again, it's stuff that I hope I can eventually feed back to you guys. If you're willing to accept this is a long haul project, I'm sure we can all have plenty of fun along the way.
Anyway, that's my essay for tonight
Edited by citypaul, 02 September 2014 - 10:24 PM.