Farls: Hackers in the Bazaar

I completely understand nerding out about stuff. I feel like everyone has about something or other at some point in their life. When I was younger, it was Nintendo. I thought I was so cool because I knew all of the history and could recite all of this info about the different console generations and stuff, always finding myself reading books and watching YouTube videos to learn more. Nowadays, it's a cappella. Since I'm music directing for my group this year, I've become fixated on music theory, watching other groups' arrangements to try and incorporate some of those ideas into my own. I feel like it's important to be passionate about something , especially a hobby that gives you a creative outlet as a distraction from work. "This is after the divorce. Dad lives in another part of Helsinki. He thinks his kids should have more than one interest, so he signs you up for basketball, his favorite sport." I try my best to never be quick to judge people I meet be...

I'm so washed. It's so joever. Every morning I wake up and tell myself that I have all of this free time to work on a personal project or read a few articles about a new release, and every night I lie awake in bed hating myself for attempting neither. While I do keep my schedule pretty busy, I always wonder how hackers have motivation, and time, outside of school or work to contribute to projects for fun. "What we see implied in hacker ownership customs is a Lockean theory of property rights in one subset of the noosphere, the space of all programs. Hence `homesteading the noosphere', which is what every founder of a new open-source project does." While I've never really contributed to an open-source project, I never would think to do so just so I can claim partial "ownership" of the service. I don't think this is what ESR was getting at, either, but I was interested in how much of this essay was dedicated to defining this concept. I have always ...

  The first question that comes to mind: why not both? I'm assuming this is probably a popular take, as each model is appropriate for different scenarios, but I think it's healthy to understand and respect both concepts  and where their application is most effective. " It may well turn out that one of the most important effects of open source's success will be to teach us that play is the most economically efficient mode of creative work." Over my past two internships (same company) I worked with a small team of about four developers, including myself. Our work was very bazaar-style: code being passed around with no real structure. We followed the Agile methodology, but relatively loosely. It was the perfect situation for our team. Since there were only a few of us working on a much larger project, it would not have made sense to implement a top-down approach. Especially since our Project Manager had no real development experience (a former IT employee internally ...