Mildly putting this, it has been an absolute mongrel to setup the Optus Siemens Speedstream 4200 modem to work with Apple Timecapsule. I have tried many different configurations but have finally worked out how to do it.
There are only a couple of steps:
We interact with many interfaces in our everyday life. We get used to these interfaces and how we interact with them and it takes a brave person to move from the pattern of these interfaces.
This raises some interesting hurdles for wannabe game changers:
Your new interface may have all the bells and whistles but may still find itself subsumed by an inferior interface that is closer to the norm.
If you move away from the norm, how do ensure that your new approach will get traction to become the norm.
You might want to study the new smartphone industry for a great example of how to do it, or in a lot of cases how NOT to do it.
Which leads to the next question, what interface do you want to see redesigned?
I saw a quote the other day, not really sure who said it, that stated that we need to be bored, because out of that boredom we do our best thinking.
I wonder in this age of always being entertained, whether as a people we are being robbed of many good ideas because there is always to think about, or at least robbing our attention?
Henac
need this tuesday
Quite well explained.
Use this to call a public or private method. setAccessible(true) is the missing link, ie.
Method privateStringMethod = PrivateObject.class.
getDeclaredMethod("getPrivateString", null);
privateStringMethod.setAccessible(true);
String returnValue = (String)
privateStringMethod.invoke(privateObject, null);
System.out.println("returnValue = " + returnValue);
Utility class for getting selections and the like in Handler classes.
Have you ever been involved in a corporate restructure? Well, I think I am in the third or fourth restructure in a matter of 4-5 years. It is starting to grate on me just a little.
Each time there has been the promise of a better way to work, but realistically they have all been just moving bodies around… and/or renaming team names. Don’t get me wrong, they have all been started with good intentions and with good goals in mind, but they have all failed to deliver what has been promised.
The main reason I believe they have failed is because none of them have really addressed the real cause of why the restructure is required, that is to better the “process” of how we do our work. Without trying to improve the process of how we do our work, moving people around or just renaming teams, is just going to cause disruption to the process that we currently have. It may be successful in the eyes of the managers involved because they get a big tick on their performance appraisal, ie. implement new structure… tick. but that doesn’t help the people that these managers are supposed to be helping, their subordinates/workers.
Anyhow, I had better go to bed and get some rest before heading back into the mix of another restructure tomorrow. My best advice is to get the subordinates/workers to rally together and propose a better way of doing business (a better process) and then restructure your teams, if needed, to accommodate the better process. At least this way there will be two groups of happy people, managers and workers :)
Henac
Might need to start doing this as this get more unclear with KB and more stuff for the SED
Ahh…. It can call other goals… just set sun:sync-pom as the goal
To do this properly… use the extension point
Collaboration here we come!