On Tuesday 09 September 2008, Aaron J. Seigo wrote: >needed in > practice. in fact, the simplicity is *THE primary feature*. > > as a team, we end up in this same sort of discussion for nearly every bit > of the API that we spend too much time with. why? we become comfortable > with the API, master it, then try and do new tricks with it that lead us to > want to make the API even more complex ... and we forget about simplicity. > we forget to challenge ourselves to accomplish our goal with the simpler > API. we forget that we're not here primarily to obsess over the framework, > but to make things with it. > > a good exercise that i've found to try and avoid this pitfall is to imagine > in my mind a new coder who pops up on the irc channel. i then imagine > myself explaining what i'm working on to them. this is often an eye > openner. indeed, didn't tought from that way :) btw, near to make clock use it, just fixed a crash in the patch and then mostly works =)
Cheers, Marco Martin > another good exercise is not allowing myself new API; i pretend that it is > Simply Not An Option. even if this means i have to go away for a day or two > and think about it all frustrated, usually i eventually come back with a > much better way to do it. sometimes it doesn't need new API at all. > sometimes we end up with a new class altogether (that's how Plasma::Service > came about). > > just some thoughts to help improve our shared design process =) _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
