Skip to main content

Algorithms versus Architecture

I was trying to explain to someone the other day what I did; he was in BioInformatics. It occurred to me that there was a dimension in computer science that I had not been able to articulate properly before: algorithms and architectures.

Some people who call themselves Computer Scientists of one flavor or another focus on solving what seem to be basically algorithms. For example, getting the right image processing algorithm or credit scoring algorithm. On the other hand, others who also call themselves Computer Scientists focus less on the algorithms but on the organization of the computer system. For example, ensuring that the image processing can actually be used effectively in a user's context.

I have noticed a tendency for people to clump themselves into either the algorithm class or the architecture class. I personally gravitate to the latter. I have also noticed a tendency for algorithmists (sic) to discount the contribution and relevance of the work of the architects -- and vice versa. It shows up as “I've solved the problem with this cool algorithm” on the one hand and “Apply that function here” on the other hand.

Of course, both are important. It does happen that many of the hard architecture problems are in arenas where the algorithms themselves are trivial (adding up a column of numbers anyone). Similarly, the UI for a video player is also pretty simple, even if the playback algorithm itself is not.

In the world of Service Oriented Architecture, with action at a distance to be supported in a safe and effective way, we have a situation where we need both world-class algorithms (e.g., to correctly infer the consistency of a purchase order with a vendor's Ontology) and world-class architectures (e.g., to ensure that we can actually place those orders in a reliable, safe and effective way).

Popular posts from this blog

Concept Oriented Markup

I have long been frustrated with all the different text mark up languages and word processors that I have used. There are many reasons for this; but the biggest issue is that markups (including very powerful ones like TeX) are not targeted at the kind of stuff I write.

Nowadays, it seems archaic to still be thinking in terms of sections and chapters. The world is linked and that applies to the kind of technical writing that I do.

I believe that the issue is fundamental. A concept like "section" is inherently about the structure of a document. But, what I want to focus on are concepts like "example", "definition", and "function type".

A second problem is that, in a complex environment, the range of documentation that is available to an individual reader is actually composed of multiple sources. Javadoc exemplifies this: an individual library may be documented using Javadoc into a single HTML tree. However, most programmers require access to multiple…

Robotic Wisdom

It seems to me that one of the basic questions that haunt AI researchers is 'what have we missed?' Assuming that the goal of AI is to create intelligence with similar performance to natural intelligence; what are the key ingredients to such a capability?

There is an old saw
It takes 10,000 hours to master a skill
There is a lot of truth to that; it effectively amounts to 10 years of more-or-less full-time focus. This has been demonstrated for many fields of activity from learning an instrument, learning a language or learning to program.

But it does not take 10,000 hours to figure out if it is raining outside, and to decide to carry an umbrella. What is the difference?

One informal way of distinguishing the two forms of learning is to categorize one as `muscle memory' and the other as 'declarative memory'. Typically, skills take a lot of practice to acquire, whereas declarative learning is instant. Skills are more permanent too: you tend not to forget a skill; but it is…

Comments Should be Meaningless

This is something of a counterintuitive idea:
Comments should be meaningless
What, I hear you ask, are you talking about? Comments should communicate to the reader! At least that is the received conventional wisdom handed does over the last few centuries (decades at least).

Well, certainly, if you are programming in Assembler, or C, then yes, comments should convey meaning
because the programming language cannot
So, conversely, as a comment on the programming language itself, anytime the programmer feels the imperative to write a meaningful comment it is because the language is not able to convey the intent of the programmer.

I have already noticed that I write far fewer comments in my Java programs than in my C programs.  That is because Java is able to capture more of my meaning and comments would be superfluous.

So, if a language were able to capture all of my intentions, I would never need to write a comment.

Hence the title of this blog.