Yesterday I finally got around to sitting down with the Canvas and Processing.js tutorial in last month’s issue of .Net Magazine (Issue 202, page 82). I’ve been wanting to play with Canvas since the HTML5 special of the ExplicitWeb podcast we did back in March (subtle plug) and this tutorial seemed like a good way of getting started.
Recently I worked on a Wordpress site where I wanted to be able to customise the dashboard for different user roles. Wordpress by default has administrators, editors, authors, contributors and subscribers. It’s not too much to assume you might not want to show your editors or authors all the details of your blog posts etc and this short snippet will allow you to do just that.
I’ve been experimenting with developing my Twitter account for the last year or so, and this week I published 5 simple steps for getting from beginner to a successful Twitterer: Getting Started with Twitter: 5 Simple Steps. The article is aimed largely at small companies and organisations who are looking to use Twitter to drive traffic to their sites and improve their Brand’s reputation.
Last week marked the launch of the 7th ExplicitWeb podcast, complete with our second guest, Rick Nunn. The show seems to be gathering strength with each new episode and I thought it about time I shared my thoughts. If you haven’t heard the podcast yet, I recommend checking us out either at the ExplicitWeb site or our page on iTunes.
Just a quick post on the origins of the podcast, the idea behind it and why it is the way it is!
Please Note: This is the companion blog post to a section I did on Explicit Web in Episode 6. This topic is possibly easier to digest in audio form, so I highly recommend you have a listen!
Nightmare clients: We’ve all had them.
They come in all shapes & sizes: needy ones, demanding ones, ones that know too much, ones that know too little, ones that don’t call, ones that don’t pay, and all making our lives a more difficult that we’d like them to be. Using “Transactional Analysis” I’m going to help you figure out what’s going wrong and perhaps set things straight with those problematic client relationships.
When working with large and complex datasets in Symfony, there comes a point where the ORM layer (Propel or Doctrine) causes more problems than it solves. Sometimes it’s necessary to debug large SQL queries built using the ORM layer, and at other times it’s appropriate to bypass the ORM layer entirely. The following snippets come from projects using Propel, I realise a lot of folks will have moved on to Doctrine but I hope there may be one or two useful things for that here too.
