Control without Controlling!

An informative article by Steve Vinoski on Serendipitous Reuse, how REST and simillar architectural styles nurture it.

He concludes emphasizing that well-constrained architectural styles can be the right recipe for EA success (controll without controlling!)

It's highly ironic that many enterprise architects seek to impose centralized control over their distributed organizations. In many cases, such centralization is a sure recipe for failure. A proven framework based on a well-constrained architectural style like REST allows for decentralized development that, because of the architectural constraints, still yields consistency. The Web itself is proof that this form of "control without controlling"2 works. In the long run, this approach is far more likely to achieve what architects seek than trying to enforce collections of ad hoc governance rules.

Advice from Bruce..

Bruce Eckel has an excellent blog post based on his commencement address for Neumont University.

Some intresting points mentioned...

50-80% of programming projects fail. These numbers are so broad because people don't brag about their failures, so we have to guess. In any event, this makes the world sound pretty unreliable

5% of programmers are 20x more productive than the other 95%

You must learn continuously and teach yourself new technologies

Code is read much more than it is written. If people can't read your story, they can't improve it or fix it. Unreadable code has a real cost, and we call it 'technical debt'.

Code reviews are the most effective ways to find software defects, and yet we usually 'don't have time for them'.

Here are some more which many people have seriously believed(myths):
- Companies don't have to make a profit anymore. It's the new economy.
- Real estate always goes up, even if salaries don't.
- Or even: A university must be a traditional campus and not an office building.