...more recent posts
I'm not getting much traction on the server project. Since I really know almost nothing, its hard to pick an approach route. I guess the point is that it doesn't really matter, just jump in, and eventually you'll figure out what the best way would have been to approach the problem. Or another way of saying this is: just pick one small thing and start there, then move on to another small thing, and eventually a bigger picture will emerge. I guess there has to be some wasted motion when you are trying to blindly find your way. But if that's the case, are those motions still wasted?
Actually this sort of thinking is the real problem. Stop writing and fire that beast up.
Those "Real Good Plumbers" have managed to break the heating system. The last 24+ hours have been cold. Like I need an excuse to stay in bed.
Alpine is a file-sharing network getting a lot of mentions.
Here's an interview with Wilfredo Sanchez, an interesting programmer who was, until last week, the lead open source developer on Apple's Darwin project, and who is now the "open source program manager" at knownow (a just out of stealth mode p2p/2-way-web sort of thingie.) Basically the interview is talking about open source development in general. W.S. has a nice middle of the road (to me) attitude that seems very reasonable (unlike some voices in the open source world.) It's not about the license, or the code per se, it's about the community of people that can form around such projects.
"The way I think about it, a community is a group of people with some interest in a given problem space and a vision for how to tackle it and what to do with the result. They tend to rally around some code, because code sets some nice boundaries for the scope of that problem space, but the code might be tossed out and re-written or otherwise modified and extended to reflect the vision of the group, which evolves the members discover new ideas, or the membership changes. The successful communities I know about have some common characteristics: They tend to have a core group of some manageable size, which is generally comprised of the most active developers, but also of other people who are known to understand the problem space well. The core group and the code are what provide continuity and direction, and they roughly represent the vision of the whole group."