I don't agree that the Australian tax sites are good or clear. They are frustrating, hard to use and their support is appalling - i.e. about 4 months ago I had some problem with the client software, I sent an email to the address recommended and I have YET TO receive a reply!
The funny thing is I've been working with the web (i.e. developing web-based applications for about 6 years) but my non-tech friends say the same thing.
AOL TimeWarner do not (yet) own EMI and since EMI owns Capitol and Virgin records.
Of course EMI is looking for a buyer, but the EU quashed attempts of both Warner Music and BMG to merge with EMI.
There is an early access edition of the next release, so download it and give it a go. You'll be pleased you did. Among its fans are Martin Fowler (author of well regarded books on UML and code refactoring)
I'm not sure if I agree with your analysis of "evangalists". To my mind loving Amazon is indicative of someone having a clue - Amazon are one of the few companies who understand the unique nature of the Internet and don't waste everyone's time trying to slavishly recreate "old media" experiences online.
For more on this, see this article on "Amazoning the news". Most informed commentators point to Amazon as a model - how many times does Jakob pour praise on Amazon on useit.com? Derek Powazeck similarly praises Amazon in his excellent new book.
The clueless ones are the advocates of Boo and talk about developing "interactive applications" which are no more than 1MB Flash movies that have you itching for the Skip Intro button. If these people learnt to think and/or actually used the Internet we'd all be better off.
This article by Clay Shirky also covered the problems with "m-commerce" a while back. People are more interested in emailing their buds than struggling with an unusable device.
Unfortunately, according to the story I read on my.netscape.com (which proves impossible to find whilst surfing around home.netscape.com), the device only allows for one-way sychronisation (ie. download from PC).
Design Patterns Explained: A New Perspective on Object-Oriented Design
by Alan Shalloway, James R. Trott
This book is excellent.
It talks about the use design patterns as a key OO technique in a very easy-to-read manner.
The book also explains the differences in meanings of terms used in Gamma et al's "Design Patterns" and Martin Fowler's "UML Distilled" ("Design Patterns" was written before UML was developed).
And while "Design Patterns" says things in a prescriptive manner: "favour composition over inheritance" this book gives examples as to why over-use of inheritance is bad.
The concept of design patterns introduce a "new" way of thinking about OO design and programming. Older books and techniques tended to promote inheritance.
Several people have mentioned people skills and I would have to agree. The problem is where or how do you learn people skills? Specifically where do you learn the kinda people skills you would need for such a role.
In my previous role I had people skills in the sense of getting along with people famously, but not in the sense of being able to persuade other members of my team of the strength of my ideas (even though I arguably had the most relevant experience to the problems we were trying to solve).
Yes, the organisational structure contributed (I was in a team that comprised 3 people who were in different departments, on differnt floors who didn't talk to each other enough), but my lack of skills in this area was also an issue.
One of the other team members, by contrast, was a very good poltician, having the ability to steer people around to her ideas and her way of thinking easily.
Any ideas, advice on how to develop these kinds of people skills?
Slashdot Mirror
..ah dammit - i meant to say "say the same thing as you" - they think they're easy to use.
I don't agree that the Australian tax sites are good or clear. They are frustrating, hard to use and their support is appalling - i.e. about 4 months ago I had some problem with the client software, I sent an email to the address recommended and I have YET TO receive a reply! The funny thing is I've been working with the web (i.e. developing web-based applications for about 6 years) but my non-tech friends say the same thing.
AOL TimeWarner do not (yet) own EMI and since EMI owns Capitol and Virgin records. Of course EMI is looking for a buyer, but the EU quashed attempts of both Warner Music and BMG to merge with EMI.
Mod this up!!!! Informative AND funny (and also... sadly much too true).
My recommendation is IDEA from Intellij.
http://www.intellij.com/
There is an early access edition of the next release, so download it and give it a go. You'll be pleased you did. Among its fans are Martin Fowler (author of well regarded books on UML and code refactoring)
I'm not sure if I agree with your analysis of "evangalists". To my mind loving Amazon is indicative of someone having a clue - Amazon are one of the few companies who understand the unique nature of the Internet and don't waste everyone's time trying to slavishly recreate "old media" experiences online.
For more on this, see this article on "Amazoning the news". Most informed commentators point to Amazon as a model - how many times does Jakob pour praise on Amazon on useit.com? Derek Powazeck similarly praises Amazon in his excellent new book.
The clueless ones are the advocates of Boo and talk about developing "interactive applications" which are no more than 1MB Flash movies that have you itching for the Skip Intro button. If these people learnt to think and/or actually used the Internet we'd all be better off.
This article by Clay Shirky also covered the problems with "m-commerce" a while back. People are more interested in emailing their buds than struggling with an unusable device.
Unfortunately, according to the story I read on my.netscape.com (which proves impossible to find whilst surfing around home.netscape.com), the device only allows for one-way sychronisation (ie. download from PC).
Design Patterns Explained: A New Perspective on Object-Oriented Design by Alan Shalloway, James R. Trott This book is excellent. It talks about the use design patterns as a key OO technique in a very easy-to-read manner. The book also explains the differences in meanings of terms used in Gamma et al's "Design Patterns" and Martin Fowler's "UML Distilled" ("Design Patterns" was written before UML was developed). And while "Design Patterns" says things in a prescriptive manner: "favour composition over inheritance" this book gives examples as to why over-use of inheritance is bad. The concept of design patterns introduce a "new" way of thinking about OO design and programming. Older books and techniques tended to promote inheritance.
Several people have mentioned people skills and I would have to agree. The problem is where or how do you learn people skills? Specifically where do you learn the kinda people skills you would need for such a role.
In my previous role I had people skills in the sense of getting along with people famously, but not in the sense of being able to persuade other members of my team of the strength of my ideas (even though I arguably had the most relevant experience to the problems we were trying to solve).
Yes, the organisational structure contributed (I was in a team that comprised 3 people who were in different departments, on differnt floors who didn't talk to each other enough), but my lack of skills in this area was also an issue.
One of the other team members, by contrast, was a very good poltician, having the ability to steer people around to her ideas and her way of thinking easily.
Any ideas, advice on how to develop these kinds of people skills?