WOW - Aspect-oriented development!
© Copyright Frank D. Kanu 2000-2008
From an article I just read: Aspect-oriented development lets programmers treat a feature not as a single function but as an “aspect” that cuts across all parts of an application. And later: … and another potential “aspect” is application response time.
So we have agile and extreme programming. We did that at university in 1987—but didn’t name it agile or extreme, we named it team. And now “aspect oriented”.
What happened to the most important thing in programming: Algorithms? If the algorithm is wrong—none of the new methods will help you help you in any way.
With agile programming frequent changes in business requirements, once viewed as the ultimate headache in programming are readily accepted.
Let me quote Thomas Power’s “Networking for life” here:
Recently I have seen a big change in programming from the thinker who tries to have a working algorithm to the big buzz words coder who is missing the understanding of the fundamentals.
Technorati (All Links are external): algorithm application response time business requirements buzz words encounter extreme programming frequent changes headache most important thing optimum route oriented development programmers programming algorithms road space thinker thomas power travellers business it
From an article I just read: Aspect-oriented development lets programmers treat a feature not as a single function but as an “aspect” that cuts across all parts of an application. And later: … and another potential “aspect” is application response time.
WOW!
So we have agile and extreme programming. We did that at university in 1987—but didn’t name it agile or extreme, we named it team. And now “aspect oriented”.
What happened to the most important thing in programming: Algorithms? If the algorithm is wrong—none of the new methods will help you help you in any way.
With agile programming frequent changes in business requirements, once viewed as the ultimate headache in programming are readily accepted.
Let me quote Thomas Power’s “Networking for life” here:
“Imagine that you set out to drive across a big city.
You have no particular destination in mind. But
everyone’s driving across the city, so that’s what you
do. Each time you encounter traffic at a standstill, you
turn off on the first available road. When you reach a
junction, you follow the route that looks easiest.
Where do you end up?…
Imagine instead that you have a firm idea of your
destination. You work out the optimum route before
you leave home, and you stick to it. You don’t yield
an inch in road space to anyone else. You’re going to
win this battle. You reach your goal.
Both these travellers fail.”
Recently I have seen a big change in programming from the thinker who tries to have a working algorithm to the big buzz words coder who is missing the understanding of the fundamentals.
Less quality. Lower values.
But buzz words.
But buzz words.
Tags:
algorithm application response time business requirements buzz words encounter extreme programming frequent changes headache most important thing optimum route oriented development programmers programming algorithms road space thinker thomas power travellersTechnorati (All Links are external): algorithm application response time business requirements buzz words encounter extreme programming frequent changes headache most important thing optimum route oriented development programmers programming algorithms road space thinker thomas power travellers business it
This blog-entry is protected by a digital fingerprint:785273ed81985582c8a1be62f78c9459
