You might have read here or on other blogs that SOA isn’t a purpose. It is a means to an end. The same goes for all the technologies that we use when implementing a SOA, or an architecture, or an application in general. So I wanted to share the next video with you since I think that it – in an even broader perspective – shows this point. Technology itself is not good or bad. It all boils down to how we as people use it.
An earlier post on how cookies are used to track you, explained how tracking cookies work. This post will show you how to stop websites from tracking you using Firefox 4. This latest release has a Do-not-track feature that lets you tell websites you don’t want your browsing behavior tracked.
By turning on the Do-not-track feature, Firefox tells websites you visit that you don’t want your browsing behavior tracked. Please note that honoring this setting is voluntary. To put it differently websites are not required to respect it.
Turning on the Do-not-track feature in Firefox 4
Click the Firefox button at the top of your browser window and click options.
Make sure you’re on the Advanced panel.
Select the General tab.
In the browsing section check the Tell websites I do not want to be tracked.
Click OK to leave
Check the Tell websites I do not want to be tracked option
There is a growing number of Twitter Apps that trick you into giving them access to your account and so enabling them to send spam on your behalf. Should you (like me at least once) fall for this trap, here is an easy way to prevent further damage. Use the following url: http://twitter.com/settings/connections or click the links that are highlighted in the screen shot on the right to manage your Twitter connections.
After that you just click Revoke Access below the Application that is using your account to spam others. An example is depicted in the screen shot below (for a non spamming App):
“We strongly believe in the power of IT. Information technology makes real change possible and that does not always have to mean huge investments. We distinguish ourselves by clearly defined improvement projects, with involvement of both IT and business in which collaboration with customers is essential. Achieving Specialization is our confirmation that we are doing well. It continues our long relationship with Oracle and gives our customers the confidence to work with a qualified party. ”
Bas Diepen, senior manager of Alliances and Channels at Oracle:
Whitehorses know how to keep changes small and simple, no matter how big projects are. We are pleased that the investment they have made in gaining knowledge and Oracle skills, is now reflected in achieving this Specialized status.”
Not only is it the time of year to look back (and think about what the future might bring), I also noticed that deltalounge came to 100 blog posts. Further back in history and perspective my first post ever was on the IT-eye weblog together with people like Mike van Alst, Andrej Koelewijn, and Tom Hofte. Later on I moved to the Whitehorses blog where I joined guys like Edwin Biemond and where I’m still a regular blogger.
The agenda for the SOA Symposium 2010 has been posted. Again there are very interesting sessions during this 2 day conference. The largest and most comprehensive in the field of SOA and Cloud Computing. The Real World SOA Case Studies track offers a great opportunity to learn from the experience of others. In this track you will find:
Real-life accounts of successful and failed SOA projects discussed first-hand by those that experienced the project lifecycles and have a story to tell. These veteran practitioners will provide advice and insights regarding challenges, pitfalls, proven practices, and general project information that demonstrates the intricacies of implementing and governing service-oriented solutions in the real world.
I will be presenting the first session in this track on Using a Service Bus to Connect the Supply Chain. If you have any topics or questions in advance that you think I should address, please post them in the comments. Hope to meet you in Berlin.
Some of the RSA talks are distilled by the folks at CognitiveMedia into abridged animated versions – RSAnimate. Here is one om motivation and drive:
There are loads of examples in litterature but also in more popular books like Freakonomics that:
People respond to incentives
In the animation you’ll see the kind of incentives that work well for tasks that go beyond mechanical skills and that require rudimentary cognitive skills (like conceptual and creative thinking). These incentives include the following aspects :
Autonomy – Which demands engagement instead of management and control.
Mastery – It is great fun to learn things and sometimes even be (really) good at something!
Purpose – Humans are purpose maximizers even more than money maximizers.
Please note that money isn’t one of them. In short for organizations and managers it boils down to:
Treat people as people!
Let me know what you think on this subject in the comments….
Yesterday I attended a Lessons Learned session for a Software Development project where I’ll be involved in the upcoming phase. All participants shared their opinion on the negative and positive experiences. What went well and what needed improvement. Putting all these opinions expressed on Post-It notes in perspective I realized that the major part of the negative experience where from the early days of the project. Whereas the positive experiences seemed to be from the most recent period. This brought me back to one of the models I was taught on Group Development while taking training and coaching courses. It suddenly made sense to me that there had to be a relation with the Tuckman’s Group Development Model.
Forming: Individual roles and responsibilities are unclear. Lots of questions about the team’s purpose, objectives and external relationships. Processes are often ignored. Members test tolerance of system and leader.
Storming: Clarity of purpose increases but plenty of uncertainties persist. Cliques and factions form and there may be power struggles.
Norming: Agreement and consensus is largely forms among the team. Roles and responsibilities are clear and accepted. Commitment and unity is strong. The team may engage in fun and social activities.
Performing: The team knows clearly why it is doing what it is doing. The team has a shared vision and is able to stand on its own feet with no interference or participation from the leader. There is a focus on over-achieving goals.
More in this PDF on Forming, Storming, Norming and Performing.
So in which phase do you think the most fun, excitement and productivity is? And as you guessed this was reflected in the Lessons Learned session mentioned: The negative experiences were during the Storming, and the positive experiences during the Performing phase.
These phases are all necessary and inevitable in order for the team to grow, to face up to challenges, to tackle problems, to find solutions, to plan work, and to deliver results.
It is important to realize this because sometimes a group of people in a meeting go through these same four phases. And if your a real goal oriented person you could try to skip the first two of three steps. That in will have a severe impact on the buy in of the group / team.
The teams that don’t get out of the Storming phase usually deliver no or very low quality software…
For me it is great to see the benefits of principles like reuse outside of IT. In this post i’ll share another example. Recently I read an article (in Dutch) on the success of Audi. Audi managed to keep up it’s sales even during 2009 (Annual Report 2009 PDF Alert 16MB!). Audi delivered 949,729 (compared to 1,003,469 in 2008) cars to customers worldwide in 2009. Sales were thus only 5.4 percent down on the record level of 2008 (source).
Besides innovation it is said in the Dutch magazine Management Team that reuse is one of the driving forces. It is great to have another example of how the principles behind Service Orientation not only deliver value in IT but also – or probably mainly – for the business when applied e.g. in other engineering disciplines.
Reusable building blocks
Audi has limited the number of modules engineer are allowed to use to construct a new model. There are two main lines, based on how the engine is placed: