Troy Wing is a fellow Kiwi who seems to be going great guns in the stateside IT industry – it’s nice to have such role models to aspire to.
In an excellent post today, Troy made some comparisons about a worker of yesterday/today and a Web2.0 empowered worker. What he says resonates completely for me, which is kind of ironic considering I just got off a flight from Auckland where I spent the day doing some consulting work which, in a 2.0 world, could have been done remotely. That said 2.0 is a journey that we’ve only just begun.
Some of the things Troy says are skewed towards the good side of the 2.0 spectrum and the bad end of the traditional spectrum – but I guess that’s just a little artistic licence!
|Time||Web 2.0 empowered Technology Worker||Traditional “On Premise” Technology Worker|
|8am to 9am||Skype with US East Coast team members, 10 minute meeting to discuss plan for the day and any urgent issues. Review any issues found by India Team. 1 Developer in NY is sick, but can continue working. Review Task/Issues List in SaaS Tracking Tool.||Sitting on Route 80E waiting for vehicle breakdown to clear.|
|9:30am to 12pm||Check out code from online Subversion and continue development, continuous IMing with other developers and project managers to assist in problem resolution. Add useful tips and hints to company wiki.||Check emails, has a question to ask India team but can’t as they have gone home.Has to wait until tomorrow. Move onto next task. Status Meetings with entire US team. Delayed by 1 hour as Project Manager is stuck in traffic still. 1 team member calls in sick.
Half an hour after meeting starts, CTO walks in and wants a recap meeting, meeting starts again.
|1pm to 5pm||Continue Development, stuck on a problem, ask social network for help. Problem resolved. Have an idea of a blog post, draft it out and post it. Decide you need to do some online shopping for the holidays. Complete development tasks for the day and decide to start on tomorrow’s tasks
to stay ahead. Think of a great UI idea, you prototype it and publish it on Dev Web Server for all to review.
|Server problem at work, development delayed by half an hour as cannot get source code from server. You begin development, stuck on a problem, send an email out to colleague. Out of office reply received back. You skip the problem and decide to surf for a little while.|
|6pm -7pm||Dinner||Stuck in Traffic|
|8pm||IM or skype with India to handover tasks for overnight processing||India reads email, can’t understand the requirements, sends an email in response. No Progress for another day.|