Pipes experiment
I decided to have a little play around with Pipes a few days ago for the first time. I had a little problem that I thought would be relatively easy to solve using Pipes.
First of all let me say I love pipes, I love the whole idea of feed mashing and have been fascinated with the concept for a while. Pipes however make such feed mashing child's play, no code involved (OK you can insert some regex). I was not going to go to deep in this particular session however as the problem I had set seemed simple enough. But in implementing I learnt an important lesson about taking such a high level graphical view, one I had perhaps forgotten. With all of this simple drag and drop connecting of the pipe components, my brain actually forgot to engage on the normal analysis I would undergo during even the most simple programming task. As a result I completed the design within 10 minutes and set it running. Only several days later did I realise the fundamental error in the design, one which any casual pipes user could easily make.
Bizmoding Project Management
Ok so our first workshop example is the creation of a bizmod to handle basic project management. This should be able to record the events of a given project and it's parts, it should also be able to report into other roles such as accounts and ease communication internally and externally with the project partners.
One of the most important parts of project management is communication and events. To manage the events we will use GCal and for the communication we will use a combination of feeds and email, using Google reader and GMail. many of these services can be swapped out according to your own preferences. We are working internally with a service provision package called Google web apps (GWAD) for domains, this neatly packages up the main services we require. It also marries nicely with our existing infrastructure based as it is on Google web apps.