Skip to main content

Moving on....

I started a new job at the beginning of the month. I'm no longer working at the National e-Science Centre and that means that I won't be involved with Grid Computing Now!. I was granted a day from my new job to host the webinar on cloud computing with Ross Cooney, but that was my last commitment for GCN!.

It's been almost 6 years since I joined NeSC and it was about this time 4 years ago that we were writing the proposal for the Knowledge Transfer Network that became GCN!. Looking back, I the experience has taught me a lot as we evolved the KTN to be most effective. It took a lot of effort to get ourselves recognised - to "build the brand" in marketing speak - and I think the work paid off.

Now I have the chance to actually practice some of what I preached. My new position is Head of Development Services in the Information Systems Group of the University of Edinburgh, and one of our goals for the next year or so is to roll out a service-oriented architecture for the university. Other part of the ISG are deploying virtualised servers and my erstwhile colleagues at NeSC are working towards a campus grid. With good planning, we might even get these initiatives to work together.

I will post here when I have progress to report, but I will be blogging even less often than I have been until now. In the meantime, I wish everyone involved with Grid Computing Now! all the best for the future.

Comments

Ross Cooney said…
Hi Dave,

It was great to work with you over the past few months. Enjoy the new job, Talk soon,

Ross Cooney

Popular posts from this blog

Project Leadership

When I look back over recent projects that I've been involved in, it seems that one key to making a project successful is having someone on the team who really drives it forward: someone who is invested in the project as a whole and not just their own part in it. We (by which I mean the University's Applications division) have a well-defined project process, with defined roles, required milestones, deployment standards, and so forth.    All these are useful, but if the team doesn't have a leader, it seems a project can lose its way, perhaps not responding to changing circumstances, getting stuck on a technical problem, or not securing a needed resource in time to meet some external constraint. The leader can be any member of the team - it could be a developer, a project manager, or the sponsor, or someone in another role.  A team can include several people who are this committed to the project; it doesn't have to be a single person.   As an example, one of...

Business Model Canvas

A Business Model Canvas is a tool for mapping the core functions and capabilities of an organisation.  Compared to the Core Diagrams that I described in an earlier post , the business model canvas attempts to present more aspects of the business, starting with the value proposition – a statement of what the organisation offers to its users (in the business world, to its customers).  It shows the activities and resources, as Core Diagrams do, but also shows user relationships & channels, and also benefits and costs.  I’m not aware of any universities that have used this tool but you can find examples from elsewhere on the web. We are considering business model canvases as a tool for mapping the strategic capabilities of units at the University of Edinburgh.  Phil Taylor, our EA contractor, sketched an outline of what a business model canvas might begin to look like for HR: This is only intended to be suggestive: the real canvas would need to result from in-de...

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this... Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision. "I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!" The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said: "Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!" "No, no, no!", said the guru, "That's not Grid!" The guru exp...