On Wed, Jun 12, 2013, at 09:25 AM, Joseph Gentle wrote: > On Wed, Jun 12, 2013 at 12:13 AM, Bruno Gonzalez (aka stenyak) > <sten...@gmail.com> wrote: > > I agree with you on this. The other day I was about to add half a dozen new > > settings to the config files (for the email-wave bot). I thought it would > > take 5 minutes max, something like adding lines like this: > > > > value = settingsManager.get(key); > > > > But after 20 minutes traversing the code, writing each variable many times > > in different files, with different syntaxes (camel case, underscore > > separators, all-caps, and whatnot) throughout several code layers, I still > > hadn't managed to reach the point of code where I actually wanted my bot to > > use the damned settings. I'm all for future-proofing the design, but I > > think that's a bit ridiculous. I don't want to imagine the fun in debugging > > federation and ot algorithms when they fail, if it's all written like this. > > > > Ali and I half-joked about going on a killing spree to halve the amount of > > code. I'm sure no practical functionality would be lost... :-) > > Well, they say that if you want to change more than 25% of something, > its often faster to just rewrite it. > > We should chat sometime about what we want to do with the wave in a > box code. There's lots of well meaning nontechnical people on this > list - and thats lovely. But us programmers should chat about what > code we actually want to write. I don't know about other people, but I > don't contribute to WIAB anymore because of the monstrosity it has > become. I'd love to figure out a plan & get back into it. > > Although it sounds like maybe I should just hop on IRC.
It'd be great to get that conversation going. Please try to have it here, as this is an archived list that folks can participate in regardless of time-zone etc. If you do use IRC, be sure to bring decisions back to this list, to maintain an equality of participation. Don't worry about non-technical people. It'd be a great problem to have if they are swamped with all the technical discussion. If we reach that point, we'll find a solution to it (a user list, or a general@ list, or whatever). What Wave needs most right now is some serious coders ready to do some serious coding. What the rest of us should do is get out of your way so that you can do that. Upayavira
