Most people that know me or have read some of the guest blogs I have written in the past know that I’m a huge advocate of grass roots events.
So I was extremely flattered to see that Heart Internet had mentioned me in their article about that very subject (pg 135) as someone heavily involved in grass roots events both speaking and promoting / organising them. Not only did they name drop me though, they also mentioned both Shropgeek and our yearly (R)Evolution conference.
I’d like to say a huge thank you to Heart Internet for including both myself and Shropgeek so heavily in their article. It means a tremendous amount to know that the hard work and effort that goes into organising and promoting these events is recognised and helps us to spread the word further!
Heart Internet were not the only ones to mention the (R)Evolution conference though, Martin Wright, a Shropgeek regular once upon a time (before he got a cool job in Oxford) and designer of this years conference website (launching very soon) was included in this months website “design off” (pg 117). When asked what he does with his spare time he told everyone about the new website in progress! Thanks Martin!
Considering this is the first time I’ve ever written anything for a major publication, this was a bold statement to make.
Needless to say, I was very nervous about it being published for this reason. I’m not normally a fan of controversy and usually stay out of any arguments that kick off on Twitter (unless I feel very strongly about whats being argued about). Talking about whether web designers should or shouldn’t be able to code is definitely a topic that causes a lot of arguments.
So why did I write this?
Simply put, because my original statement is true. I do like to work with web designers that don’t know any HTML / CSS.
Thats not to say I work exclusively with designers that can’t code. I work with both and I decide which designer would be best for the project based on the project, budget, timescales and a variety of other factors.
I’m not going to explain in depth, all of my reasons for making this statement here (you should read the article for those). But I had two main points to explain this:
- A designer that doesn’t code won’t just stick to what they know can be done. I like the challenge of being forced to think “Actually, is that possible? and if so, how would I build it?”
- I think that websites should be a team effort and no one should be a “jack of all trades”. Everyone has their speciality and its that combination of a team of specialists communicating and working well together that creates an awesome website.
The article was published on August 10th 2012 and although I did receive a lot of negative comments, I also received a lot of positive comments which I was really surprised about. I really did think that everyone would disagree with this.
Overall, this was a fantastic experience and whether positive or negative, the discussion it started was awesome!
You can read the full article here: http://www.netmagazine.com/opinions/i-working-web-designers-who-can-t-code
Some of the comments from Twitter
Some of the negative comments I received on Twitter included:
Some of the positive comments: