Last week I finally got around to coaching at Brighton Code Bar, something I’ve been meaning to do for at least a year or so now (and apologies for taking so long).
If, like me, you’ve been considering this but have worried about what you can contribute, then please just volunteer and don’t worry. The sessions are really well organised and the students either looking for help with following the tutorials or feedback/advice with their own projects. The organisers make sure that every student is matched to a coach with relevant experience/confidence to be able to help. For my first session, I was helping someone just starting out with Javascript, take a look at the Javascript first lesson. If that looks too scary there are usually students also looking for help starting out with HTML (this is the first HTML tutorial).
Personally, I’m looking forward to helping out with a few more sessions (I’ve signed up to coach at the session this Tuesday) following the tutorials and maybe then see if I can help people with their own projects, as I love to see what people are working on and their approach to problems. Who knows, in the process, I might learn a little more Python or actually get around to finally learning Ruby.
Last week, Wednesday 20th Feb, I presented at the Brighton Web Development Meet-up. My talk was an introduction on using Selenium WeDriver, starting out with the basics, leading into introducing the page object model and finishing with an example on how to use a single suite of tests on multiple websites. The demo code and slide deck can be found on my GitHub account. The room was pretty packed with about 25-30 people and a . . .
Firstly, I’m a bit late to the party with my blog article, both Steve (the event organiser) and Dave / Dan (a couple of the attendees) have written great articles that can be found here: Steve Gordon Dave Mateer Dan Clarke So back to my story regarding the event. I first heard about the codeathon from Steve via the .NET South East Meetup, which he also organises. Steve’s a prolific contributor to the HTBox Allready . . .