| 1 |
On Wednesday 10 February 2010 11:38:52 Neil Bothwick wrote: |
| 2 |
> On Wed, 10 Feb 2010 02:24:36 -0600, Dale wrote: |
| 3 |
> > > hal is a classic "Second System Effect" case |
| 4 |
> > > |
| 5 |
> > > But I thought we thrashed this to death a while ago and all agreed to |
| 6 |
> > > never speak of this abomination again, while we await the Third |
| 7 |
> > > System Effect aka DeviceKit? |
| 8 |
> > |
| 9 |
> > From what I read it appears to be the same guy doing both. Maybe, |
| 10 |
> > |
| 11 |
> > just maybe, some lessons were learned and it will be a lot better. |
| 12 |
> |
| 13 |
> Isn't that the point of redoing it? It's when someone else comes along |
| 14 |
> with brand new way of doing things that we get a whole load of brand new |
| 15 |
> problems? |
| 16 |
|
| 17 |
It really is the same guy. His blog said something to the effect of: |
| 18 |
|
| 19 |
"hal is a load of crap. I knew it long ago, the other devs knew it slightly |
| 20 |
less longer ago and the users now know it too. We were trying to do too much |
| 21 |
and shoehorn too many things into the same boxes that belonged in different |
| 22 |
boxes. I'm fed up trying to maintain this steaming mess, will not be adding |
| 23 |
new features, and wash my hands of it. I'll be doing a rewrite called |
| 24 |
DeviceKit." |
| 25 |
|
| 26 |
So kudos to the man for recognizing the real problem, admitting it, and moving |
| 27 |
onto a real solution. Nothing wrong with making a mistake and fixing it - |
| 28 |
that's how we learn. |
| 29 |
|
| 30 |
Personally, my mistakes teach me MUCH more than my successes - I then know |
| 31 |
what not to do :-) |
| 32 |
|
| 33 |
-- |
| 34 |
alan dot mckinnon at gmail dot com |
Archives