Nepomuk

[Lindsay Mathieson]

On Sat, 17 Dec 2011 10:03:20 PM Mark Greenwood wrote:
> That's fine, and useful. But the point is that this stuff should not be in a
> release of an operating system. It does not work, and deeply affects the
> performance of the entire system. It should not be necessary to switch off
> core features just to get a useable computer. KDE really messed this one
> up, and lessons must be learned.

 
A few months back I saw a post on a nepomuk  developers blog re the fact that:

- external interfaces were poorly or not documented and frequently changed

- return codes/exceptions were undocumented and frequently changed

- errors went largely unlogged and were ignored

- logging in general was almost non-existent


I commented that this was a recipe for disaster - in the large corporate 
projects I worked on it was essential for core services to be well documented 
and *essential* for them to log every error, especially unexpected ones. It 
paid off in spades when you were trying to debug weird shit happening on the 
various remote and obscure setups we had to work with.

Sure you have to keep service specifications flexible, especially in 
development as new requirements/problem emerge, but you also have to be able 
to say  enough is enough and tie it down. And always always document and make 
it transparent.

My comment was deleted.

-- 
Lindsay