During this time I have learn a lot about working from anywhere, so here are my top 5 tips. Hope they help you as much as they help me.

1. Plan location times in advance. If you know that you have a long day ahead of you – find somewhere that won’t kick you out in the middle of a complex tax. Nothing worse than being 30 minutes from finishing a project and Starbucks closes in ten minutes. Use a natural break to move early and find an alternative.
2. Keep a spare. Of EVERYTHING business critical. I have 2 Macs, my old one I could have sold, but I have kept it and it serves as a back up machine. If my day to day machine dies at 9pm, with a deadline to hit, it isn’t the end of the world.
3. Use CVS/Back up everything. I use Git. In tandem with the last post, make sure that all your code is backed up, versioned and always safe. And commit every change. Even if it only serves to remind you how you did something in a month or three.
4. Talk to people. There is far too much value in talking to people, learning from them and just generally relaxing from your focussed task fro a few minutes. You may find advice, opinion and driection from the most unlikely sources.
5. Don’t work. Just because you can work remotely, doesn’t mean you always have to be on the clock. Set your own hours by all means, but if you spend all your time being available and ready to work, you’re not living your life. Remember, my favourite saying: “Work to live, don’t live to work.”

Now – I better get back to work! Or pop into my kitchen for a snack and a coffee. Life is good.

And to prove this, here is a list of random acts of kindness I have experienced, both for me personally and things I have been involved in for the community. And a list of just awesome people all over.

UPDATE: Because I have constantly been reminded of people that have been so kind to me and the community, I shall try and keep maintaining this list for the unforeseeable future, although you might not all agree with the names on the list – I really have taken something for nothing from every single person named. Keep it up!

1. Before I even knew what PHP was, Douglas Gresham taught me how to submit a form using PHP despite we’d met only once at a totally unconnected to web event.
2. Edd for turning into a cycle nerd friend as well as geeky event mate.
3. Everyone on Stack Overflow, for answering people’s questions.
4. Ross Bruniges, for generally being an excellent beer hound (add Ben and everyone from @pubstandards to this item, as a matter of fact)
5. Paul Stanton and Ryan Taylor for being extra friendly fellow northerners whenever we happen to be in the same place
6. Paul Stanton and Ryan Taylor (yes, AGAIN!) and Anna Debenham for volunteering on the BoagWorld podcast, helping me out quite a bit in the early days.
7. Kris Noble for being a random traveling buddy (or is he actually stalking me?) and general friendly face at all manner of events. And for not whinging after accidentally stealing his idea.
8. Gareth Thompson for offering business advice in running your own web stuff. And being a bloody good bloke to boot.
9. Dave Smith for feeding work and excellent advice constantly. And letting me loose on his RackSpace hosting.
10. Jake Archibald for agreeing with my views on homeopathy (and providing good web advice!). He does bloody good talks too. And is sometimes funny.
11. AlunR for organising Geek Karting (although the £1.70 profit on the last event may mean he’s not as kind hearted as I though – PS, that’s a joke…)
12. John O’Nolan for being thoroughly offensive and wrong (read as challenging my HTML structure and semantics, which is good!)
13. Rob Hawkes for Rawkets, and that book and sound advice.
14. Syd Lawrence for letting me bug him in his own house while he showed me some HTML5 Mobile App stuff.
15. Dan Knell and Kornel for always being available to drink while teaching me clever stuff.
16. Paul Adam Davis for reminding me of something I already knew, then virtually apologising for the good point he made!!
17. Antony Killeen, who organises Croydon Creatives. PS – I can’t believe he isn’t even a full time web dude yet!
18. Katskii for being everything I would expect from a Geordie lass! That *is* a good thing, honest.
19. Luke and uBelly for pointing me at interesting things that I should do and always being willing to pay for my beer!
20. Drew and Rachel for 24ways.org and providing just awesome advice and support for Perch. Rachel also posted a much more coherent post on this topic than I ever will on her own blog.
21. Chris David Mills for not only being very metal and introducing me to Steel Panther, but also giving up his time to speak at the awesome Speak the Web
22. Dan Donald and Rich Clark gave up their valuable time to organise the aforementioned Speak the Web, so they definitely need a mention.
23. Myself (!!) for volunteering at some events, manning doors and setting up chairs etc. And buying a wooden spoon prize to try and make Geek Karters smile. I know, I am too humble…
24. A thousand (literally) other people who have all become friends, colleagues or complete strangers that have helped me on my way in the web world. And long may it continue.

and finally, thanks to @arranrp, who for his sins does organise a lot of events and through him I have met many interesting and good people (some included in the above list). And he’s a mate.

So why focus on the bad. What I would like to see is a similar list for each and everyone that is currently unhappy with the industry – you never know, it might restore some faith in your friends, colleagues and complete strangers.

Feel free to ping me – I’ll always help wherever I can, and why don’t we all try it, I actually enjoy being nice. Unless you’re Julia Hartley-Brewer, of course.

That’s what I though a few months ago and I have.  I am now full blown freelancing and contracting and generally working 15 hours a day until I get settled into a regular schedule.  Today I Should Ltd should see me good for a while. Unless other things come along (not that a pretty damn good company/start up site has been in touch to see if I am interested, well, one has which boosted my ego quite a bit last night) I see this suiting me quite well once I get evenings back to myself.

So far its going very well, aside from working far too hard and not seeing enough of anyone that I should be spending time with – but its all going to work out in the long run!

Anyway – as soon as I get the branding and such started, I’ll get a web development blog started on todayishould.com where I can keep professional head on and open this blog up to blatant whinging and bitching!

The talk focussed on what WebSockets are, how they work, and some real life cases for use. Replacing technologies like COMET and long-polling and streaming is the goal. Examples of real life use that Peter Lubbers (@peterlubbers) highlighted were things such as stock tickers, news feeds, games and many more. Some of the demos are on the Kaazing website at kaazing.me.

Then some real demos showed the possibilities of WebSockets, who knew that using HTML5 Canvas and WebSockets (plus a couple VNC servers) remotely controlling another machine would be possible. Github has given me some example code, but not tested or used this. There was of course one of my favourite canvas and WebSockets examples, Rawkets, the asteroids style massively multiplayer game. Which I am getting quite good at.

While a lot of the technologies people asked about, and some of the technical details of server stuff, were well over my head, I definitely think I can and will use websockets eventually. Probably going to continue on my learn JavaScript properly first, but looking forward to WebSockets and Canvas after that!

Dear MFC Official Direct

When seeing an advert for the 30% off sale and Boro replica kits for only £15 I was very happy and ran straight over to the store to get myself a replica home kit.

However the experience I had left me shocked, disappointed and embarrassed. Now let me say that I am a Boro fan and a front end developer (so I can understand when things aren’t perfect), but still feel the need to expose the pitfalls of this site in public.

My first issue was when I tried to update my delivery address, having moved jobs and so I couldn’t have the parcel delivered to my old place of work. However it appears I am not allowed to move companies, the company name could not be edited. ANYWHERE. Not on that form, not on my account page, not on mange addresses through my account page, nowhere. The company isn’t even called Gyro International anymore!

Following that annoyance, I thought “Fine, I’ll just add a new address. But then I couldn’t add a company name to go with that, and being in a shared building with many other companies and nowhere to add a company name and few form fields for address I thought I would have it delivered home.

I thought that would be fine, but alas no. Following selection of delivery type in step 2 I was thrown to the confirm order page. Step 4. Hold on. That’s missed step 3, and I haven’t entered my payment details yet? But I’m on the last step? Oh well. I guess this really is a good shop! That was confirmed by a nice page telling my my order has been successfully placed! Excellent, I don’t have to pay it seems. Maybe now Mido is back he is funding a shirt giveaway to try and make someone love him!

Alas no, after a second or two I was delivered and Sage Pay (formerly Protx) payment page. Now this possibly isn’t MFC Official Direct’s fault, however it is still part of a flawed process. And anyone that spends £12.7m on Alfonso Alves must have some cash somewhere to invest in a seamless checkout process. Or at least one that allows the checkout page to be on brand, not hideous and at least not be included as step 5 of 4.

So after all that and finally getting my payment details in, I notice that Sage Pay have thankfully printed my delivery address so I know its right:

Flat E
London
(They printed my postcode too, but that’s private!)

Now I know the postcode will probably mean that as a delivery address might just make it, and maybe the full address has been stored, but why print only part of the address. Thinking about it, there are quite a few flats in my area so Flat E, Putney might not make it. My address is a required 2 lines before the town and postcode so why not just show me the details so I don’t think you’ve lost half my address along the way. Same goes for invoice address. Just show it all or people (including myself) might not be confident you have managed to pass the correct delivery information and that we may never see our goods, many of which are quite expensive on the MFC Official Direct store.

Anyway, after this traumatic experience it’ll be a while before I use the MFC Official Direct store again, however I also have some gripes with the Middlesbrough Football Club website itself, so this probably isn’t the last you’ll hear from me. Thankfully however, at least the agency that built the site are linked to in the footer, so it can act as a reminder to never, ever recommend Black Magic Digital of Glasgow as a digital agency. They apparently missed out on the user experience chapter of every book they ever picked up.

Yours,

Matt Bee

Boro Fan and Front End Developer

Should designers be able to code their designs?

No.

But then again it isn’t that cut and dry. I think that there are a very small number of designers that might just be able to get away with it, but they are a minority in the geek world. There’s a reason people like Andy Clarke and Elliot himself are respected so well, because they are skilled and motivated enough to keep on top of design and code. For the majority of us we should specialise in design, front end development (HTML and CSS) or back end development. I also still think there’s a place for pure JavaScript developers (reducing the reliance on jQuery and other frameworks to optimise code).

So should designers know how to code?

Yes.

Learn how designs are laid out, learn how positioning works, learn about floats, browser bugs and the deficiencies of Internet Explorer (and Safari, Chrome, Opera and Firefox for that matter). There should be no excuse for providing designs that are an absolute nightmare to build, but it doesn’t mean you have to be able to build them yourself. If you know the limitations of the technology you can both design to their limitations and think about ways to get round that and make your awesome designs work.

Which brings about an interesting point, the best way to learn HTML and CSS is just to do it, so if you ask the question again, the answer might be different.

Should designers be able to code their designs?

Yes. But don’t let them build the production site.

Why not then, if they can? The intricacies and time spent on testing and debugging is a start, but I also spend a lot of time keeping up to speed on how Google looks at my code, mobile development, I’m still getting to grips with HTML5 and CSS3, I’m work hard on optimising code, and if I had to do all of that and design sites I build I would let myself down in one area. Not to mention I am not a designer, I do code, that is my passion and so I’m sticking to it and not learning design or keeping on top of design to be able to do both.

You could well apply the same principle to the difference between a front end developer and a back end developer, but I’ve got work to do!

My review which I recorded in January made it onto the podcast number 198, and as it was the author presenting the review, it became a lot funnier than I had ever planned!

In my opinion I believe a wireframe should simple layout exactly what information should be displayed on a page and define the importance of that information, in relation to the rest of the content.

With this idea in mind, a wireframe does not necessarily have to provide any sort of guide to the actual layout of a page. There isn’t really anything wrong with this for a simple contact page wireframe:

That will provide the main information required by a wireframe, and producing this format for every page to be developed should meet the designers needs.

However one point above is always missed, producing a wireframe for every page. Without doing this you are not creating an information architecture for a designer to follow, resulting in questioning why wirframes for any pages were created at all.

The same problem applies to wireframes that incorporate some form of layout:

Example wireframe - courtesy of http://totheweb.com

Creating a wireframe for every page becomes even more important with this wireframe style, in my opinion. Creating this type of wireframe for only a small number of pages during the information architecture stage of a web site process results in designers feeling restricted to make all pages following the same layout. Often the content will lend itself to a completely different layout, which means it needs its own wireframe and if not it should be easy to create another wireframe based on what has already been created.

One other thing I often find missing from wireframes are annotations. Visual representation is fine, but if you really want to let a client or designer know what you plan for the page, it needs to be annotated well. The annotations let the wireframe make sense and are vital to communicating the user experience. A poorly annoted wireframe wil result in poorly communicated ideas and will very probably hinder the final user experience.

So that’s what I think about wireframes, feel free to correct me if you think I’m wrong, or to add to this because wireframes are such an important part of the web development process that I think anyone involved in the industry should input into how wireframes can help ease the pressure on project management, information architecture, design and development.

So here it is, the blog on the dreaded subject of email marketing from a my point of view, why we hate it, how we can make it work, what people can do to make our lives easier and campaigns more efficient and effective.

Why don’t I like building emails?

This is simple. We love accessible, semantic, standards based code. We do not like going back to techniques used over 10 years ago. We have to use out of date layout techniques and the code is long winded, complicated and boring to produce. It wouldn’t be so bad if we could use the same HTML and CSS standards we use for web sites, but unfortunately it isn’t an option. Not if you want your campaigns to include the creative idea that you are so sure will work, at least. And this doesn’t look like changing anytime soon.

If you haven’t seen the problems with Microsoft Outlook 2007 using Microsft Word to render emails, then the internet is full of disgruntled people. Actually, I’ll help you with that. Don’t get me started on Lotus Notes.

It isn’t our fault animated gifs don’t always work. Flash can’t be used. Hell, even background images don’t work. These points ARE NOT OUR FAULT. But it still provides a hot topic of discussion between designers/concept teams and us developers. Trust my judgement, look at how long I’ve been doing this, we do actually know what we are doing, although maybe you and your great idea are more important than everyone seeing it as intended. Or doesn’t that defy the point altogether.

There are hundreds of different software, webmail and operating system combinations for us to work to. If you want your campaign to work in even 80% of them. Please listen to my advice, not just try to replicate your print campaign in an email. They are completely different mediums.

What works?

Again, simple things.

Keep your text to standard web fonts. Don’t rely on background images. Don’t ask for Flash or an animation. Keep the layout simple. The fewer images the better. Yes we can code so things will degrade gracefully, but if the client views the email in their inbox (compared to the signed off HTML file they viewed in a browser) with missing design elements they liked, it won’t be your fault, it will be mine. So please just make the designs possible in all clients.

Unless of course you have stats showing 100% of your recipients use an email client that supports animated gifs or background images – but first of all that is unlikely to be available, let alone likely to ever happen!

Even so what people don’t seem to understand is that everything doesn’t have to happen in an email. We have awesome tools in jQuery, Flash, and even simple HTML/CSS that can impress and prompt customer action better than an email. So a well thought out simple email to get people to somewhere showcasing the creative concept and getting customers interacting will work better than trying to contain everything in someone’s inbox. I find that a simple concept to understand. Why can’t others!

In the words of Columbo…

Just one more thing, if I can get on with building sites because I don’t have complicated email discussions going back and forwards, I will be happier. Of course sites are what I love, so if emails could disappear completely I’d appreciate it.

Resources

Finally, here are some good email resources, not that you’ll probably read them anyway. All are from Campaign Monitor, because they are good.

• Microsoft takes email back 5 years
• CSS support in emails
• Designing the Campaign monitor newsletter

• Front End Developer
• Web Author
• Client Side Developer
• Web Designer
• Web Producer
• Web Programmer
• User Interface Developer
• Digital Strategist
• Web Manager
• Digital Developer

What do any of these mean? For my part, I believe that Front End Developer covers all the bases. Web developer will cover front and back end work and server side (or back end) developer will work for,  you guessed it, server side developer.

I don’t know if it is because of the young age of the industry, or if people are trying to create the most impressive sounding titles for themselves or their staff, or if it is HR not understanding what somebody does.

Why would this worry me? I worry because I currently have the title Senior Web Author. What I don’t want is people to read that who has a different definition of the role and immediately discount me from anything that I may suit. If I were offered the role today I wouldn’t expect to be heavily involved in HTML/CSS and Javascript development, but I would think that an author would be more involved in content authoring.

The same works the other way, I may be looking for a role and find that I completely miss my perfect job because it was advertised as a “web designer” role. Would I expect designers to build code? Not nowadays.

This specificity us geeks now show may be a direct contributor to the current job title confusion. Back in the early days a web designer will probably have had to build the site they design, but with technologies needing such attention, people really need to specialise as early as possible. The old saying “jack of all trades and master of none” applies a great deal in our industry.

Of course a lot of companies (including my employers GyroHSR*) are still trying to determine the best structure for their digital department, the job title situation may get worse rather than better, but I hope that anywhere I have influence we can set the following roles, all that should be needed in a web site development process, especially the small to medium builds I am involved with:

• Project Manager
• User Experience/Information Architect
• Web Designer
• Front End Developer
• Server Side Developer

And User Experience/Information Architect and Front End developer roles are the ones I look out for. How better to start trying to select something new when you know the organisation has similar structure ideas to mine.

Please comment if you have any job titles I missed, or any suggestions for jobs I might look out for I would normally skip in the listings!

* I had NOTHING to do with our terrible web site, by the way