Hi, I'm Ben Barden. I'm a blogger, a programmer, a composer, a music lover, and I'm always working on something. I'm married to Lauren, and we live in Australia with our dog, Polly.
Why should you read my blog?
Some people who don't do a good job of explaining things. They use jargon unnecessarily, which doesn't make it easy to understand what they're trying to explain.
I am not one of those people. I am a highly technical person, but I know exactly what it's like when you want to do something but you can't get it explained in plain English.
I often read blogs where the authors write about all sorts of things relating to blogging, sometimes for beginners, sometimes for advanced users. But many bloggers seem to forget that not everyone is technical, and not everyone understands the jargon.
That is the reason why I started this blog - to provide blogging and website tips, but without assuming you already know the jargon.
Professional experience
I started working in the IT industry in December 1998, initially at the very bottom as a trainee. Since then I have worked in a number of roles:
- Development - writing the code that drives a program. I have written software that runs in a web browser, and software specifically for Microsoft Windows.
- Testing - finding bugs, monitoring performance, and implementing procedures for an IT department of 50 staff. At one time I was in charge of testing but also did some of the testing myself.
- Support - dealing with colleagues and external customers, many of whom are not technically-minded. Troubleshooting issues with customers, analysing problems, and implementing fixes as necessary.
Who gets involved in software development?
I have been involved throughout the lifecycle of dozens of projects, and I understand the challenges that occur at various stages along the way. I have seen things from every possible perspective:
- The customer who just wants to see the end result.
- The analyst who takes the customer's requirements and documents them.
- The designer who decides how the customer's requirements will be represented in the software.
- The developer who actually writes the code.
- The tester whose job is to find the bugs and get the developer to fix them.
- The manager who coordinates the activities to get the project in on time.
Not only have I worked with people fulfilling the above roles, I have also played the part of every one of those people at some stage in my career. So I know a lot about how software development works, and I appreciate everyone's viewpoint - not just the wishes of the technical staff.
Did you like this post? Subscribe today!
Tags: ben barden, biography
Posted by Ben on July 30, 2006 15:30 / Edited: August 07, 2008 11:57
Comments
Hi Navin, thanks for the comment. If you wish to link to my blog then please go right ahead. You already have a link to your blog as you posted a comment. I don't link to many blogs from my front page - please read How to initiate a link exchange for some tips. Thanks!
Hi Ben
I think it's a great idea to avoid techno-talk. I see it all the time and it really puts the man-in-the-street off. You've taken a good stance here, to explain things when you use terminology, and I'm sure it'll serve you well in the long term as your reputation grows.
Good luck,
Paul
Thanks Paul, it's always good to hear that other people see a need for what I'm doing. Hope you find my blog useful. :)
ha ha ha ^^, the last time I've heard about you was an email confirming your 'un-subscription' from my blog. Okey, that was an auto mail form feedburner.
Incidentally, I was checking my stats at feedburner, and there it is -your blog gave me an inbound traffic, I wonder why. So, I had to satisfy my curiosity (lest you have written something about my blog ^^). What I found instead, is my blog listed with the others 'you like.' I was flattered -many thanks.
On another note, I agree with what you have laid out here. It is great to have a blogger who is so focused on helping other bloggers in their blogging activities in a non technical way. Ironically, the blogger is highly technically competent person -simply admirable Ben.
Also, I share with your sentiments that sometimes bloggers tend to digress from their original blog intents to sway with the popular motion of blogging about blogging, where more often they failed miserably. I, for one, am tempted many times to join them. But why bother? There are pros like you who can explain it better.
Kudos on your efforts Ben and I wish you well.
Hey Ronnie. I unsubscribed from every blog because I stopped using email subscriptions and moved across to Google Reader. So I'm still subscribed to your blog. :)
Thanks for the praise - it's good to know I am on the right track with what I write. :)
Hi Ben
The site looks great now! There's definitely a need for your easy explanations for all the blogging stuff - you've hit on a real winner, and I'll recommend you in my daytime job (e-learning developer/adviser). Thanks for the email - I'll send one back in a couple of days (it's half-term here in the UK so my kids are taking up most of the time!). I'll be downloading your tracks too. Good stuff!
Hi Tim, thanks for the feedback. And I really appreciate your recommendation. I hope I can help some more people out with my tips, after all that's what the blog is for. Let me know if you like the tracks. :)
Hi Ben, nice reading your words and I agree with you.
I want to link your nice techy blog without jargon to mine. Can we do that?
or what do you say??
Regards
Navin