Re: Learning path

Maurizio Brilli wrote:

> Hi everybody,
> while struggling with a million new subjects, I had an inspiration...
> Say you have a grown-up child, let's say fourteen-fifteen. Say he 
> comes to you and asks: "Daddy, what are you working at?"
> I suppose you won't answer "a meta-framework for integrating vendor, 
> framework, and platform independent services with enterprise 
> applications", or he'd probably run away disgusted (...)
> Let's say he likes what you explain: "Nice, I'd like to learn." "I'd 
> love to teach you, but I'm very busy." "Well, where can I find what I 
> need to learn?"
>
> Wouldn't anyone attempt to draw a basic learning path (not too 
> detailed, but not even too generic) for anyone else (including myself, 
> though I'm definitely not 14, I almost have children of that age) to 
> follow? If  something nice comes out, we might put it on the wiki, for 
> others to use and improve over time.
> Let me know what you think about it.

First time we did this it came out as "a highly extensible backbone for 
integrating Java projects.Fleshed out and ready to use. As a keel to a 
ship, Keel Framework stabilizes the waters of open source development."

That represented a lot of work, but even then it was not satisfactory, 
too long. So we then came up with Any Component, Any Service, Any 
Deployment. Apparently that has not done us much better, but lots and 
lots of us worked on it over a period of weeks to get that out.

Currently, I would currently charachterize it as a group of loosely knit 
guys sharing a common application framework using some fairly advanced 
designs and implementations. That is about as much as you could get your 
kid to understand, in one setting anyway.

Then later, if the kid was interested in actually using such a 
framework,  there would be the competition issue. How would he chose us 
over other groups of guys, or other kinds of frameworks, or even other 
frameworks of a similar kind. Then, and only then would you suggest that 
he become familiar with various feature sets. Many of Keel's best 
features are not even understood because the problems that they solve 
are not even recognized as problems.

Poor kid. Lot of stuff to digest for a 14 year old. My 16 year old seems 
quite bright, and I don't know if I would put him up to the test....

> Ciao
> Maurizio
> _______________________________________________
> User mailing list
> [email protected]
> http://lists.keelframework.org/listinfo.cgi/user-keelframework.org
>