Most workers rarely get credit for doing what they're really good at. Most developers hardly ever get a chance to show what they're _really_ good at. But it's really a matter of working with people who will give you a chance sometimes.
For every pointy-haired boss who is afraid you might be smarter than s/he is, somewhere else in your company or one down the street you will find somebody who has a problem that needs to be solved. And when managers have a real problem that needs to be solved, and they can't dig a hole and hide from it, they can be amazingly open-minded.
I agree. We're all in business. Having a job means you are a business-man/woman.
IT's job is to facilitate the business activities of their company. The only measure of IT is whether or not they are helpful to everyone else. But the same is true for all employees.
It's important to see that we're all in this to make money for our employer. There is no invisible wall that divides IT from the rest of the organization. When a non-IT employee chooses to be ignorant of technology, that's a problem. And when an IT person chooses to be ignorant of business processes, that's a problem too. We all need to learn about the business we work in.
GWT was built on the idea that making a good UI using HTML and JavaScript was soooo terribly hard that you would rather use the AWT. That's a horrible solution for a problem that has a well-trained workforce already assigned to it.
Why can't we come up with a 100% abstract universal user interface description language and compile it everywhere? I don't think we have tried hard enough. We have failed, and learned some things from our mistakes, and made some cool next-generation toolkits like SWT.
Let's take it to the next level, boys and girls.
Most workers rarely get credit for doing what they're really good at. Most developers hardly ever get a chance to show what they're _really_ good at. But it's really a matter of working with people who will give you a chance sometimes. For every pointy-haired boss who is afraid you might be smarter than s/he is, somewhere else in your company or one down the street you will find somebody who has a problem that needs to be solved. And when managers have a real problem that needs to be solved, and they can't dig a hole and hide from it, they can be amazingly open-minded.
I agree. We're all in business. Having a job means you are a business-man/woman. IT's job is to facilitate the business activities of their company. The only measure of IT is whether or not they are helpful to everyone else. But the same is true for all employees. It's important to see that we're all in this to make money for our employer. There is no invisible wall that divides IT from the rest of the organization. When a non-IT employee chooses to be ignorant of technology, that's a problem. And when an IT person chooses to be ignorant of business processes, that's a problem too. We all need to learn about the business we work in.
GWT was built on the idea that making a good UI using HTML and JavaScript was soooo terribly hard that you would rather use the AWT. That's a horrible solution for a problem that has a well-trained workforce already assigned to it. Why can't we come up with a 100% abstract universal user interface description language and compile it everywhere? I don't think we have tried hard enough. We have failed, and learned some things from our mistakes, and made some cool next-generation toolkits like SWT. Let's take it to the next level, boys and girls.