With BeerChief due to launch tomorrow, it was typical that we’d run in to some problems. And run in to some problems we did. I’d planned on spending the day testing and tweaking more but in the end i spent most of it looking for a mysterious problem that arose – seemingly from thin air.
We got it in the end but it’s destroyed my plans for the day (well yesterday) and all of a sudden we’re under real pressure now to roll out the site on time and with as few bugs as possible. I could do with another week really but a deadline is a deadline and i’ll not back out of it now.
If i weren’t so busy with BeerChief i’d be sticking the knife in to DKIT once again as i’ve got 5 hours between classes tomorrow but all of a sudden those 5 hours become very important. Provided DKIT wireless doesn’t let me down like it’s being doing recently, things should stay on schedule for an 8pm BeerChief launch tomorrow.
Whilst i’ve done some work in college on BeerChief, the college equipment and wireless network are too unstable for me to ‘trust’ so the vast majority of BeerChief work has been completed at home where i’ve got my own set up. No downtime, no network problems, no mice with no scroll wheels, no CRT monitors or firewall, no dodgy chairs….
Anyway, tomorrow, 8pm, BeerChief.com – our dedicated server won’t know what hit it – having sat in a hammock sipping martini’s for the past few months
Also, i do realize there’s a lack of depth in my last few blog posts – don’t worry, i haven’t changed my style of writing, i’ve just been too busy to sit down and think like i normally would. Once the dust settles on BeerChief and hopefully it won’t i’ll be sure to fill you guys in on exactly what’s been happening at BeerChief, what i’ve been doing and what i’m thinking.