dmgbrn

This, absolutely.

Communities can be healthy without a CoC, or unhealthy with one. But having a CoC sends a big, clear message to women and other groups frequently marginalized in the tech scene that your project is healthy and welcoming.

Here's why that's a big deal: joining an open source project is an investment. If you are a woman, or black, or trans, or god forbid, some combination thereof in tech, you really don't want to become invested in a community that will at some point treat you like shit. And let's be real guys, many, many communities do treat women and minorities like shit.

A CoC, and just as importantly, the discussion surrounding one, is a simple sign that a community is a place where you can be a woman or a minority and contribute to open source without fear of harassment, abuse, marginalization, and other dangers faced by non-white-dudes in tech.

I'm not sure why you are so vehement in attacking AA. Members (such as myself) who have access to other forms of treatment (medication, therapy, and sober housing) use them. What AA gives me is a powerful source of support. Let me offer a recent example:

A couple of days ago, I stepped off my back porch wrong and broke my ankle pretty badly. I was in a lot of pain, and I definitely needed to go to the hospital. A part of me was actually quite excited at the possibility of obtaining a "legitimate" supply of opiate painkillers. Luckily, I called a friend from AA and took his much more reasonable advice not to take the chance. Once I'd made that decision I realized that I'd been greatly exaggerating the pain to myself, and that it was nothing OTC painkillers couldn't handle.

Scary stuff, right? I had come up with a way to convince myself that it'd be ok to take score some drugs, which could very easily have sent me off into a relapse. It's when things like that happen that you need to listen to a "higher power": someone who isn't having your crazy addict thoughts and can assess your behavior rationally and objectively.

Since I'm laid up, AA people have been helping me get groceries, rides to meetings, and just stopping by to say hi. I can't really see a recovery professional doing that.

This article attacks a straw man AA. I could go on, but suffice to say, if what you know about recovery consists entirely of this article, you don't know much.

Just a suggestion, but if you ended up with a caffeine problem, you're very likely to end up with a Ritalin problem. I don't know exactly what the laws are like where you live, but running out of Ritalin is a much harder problem to solve than running out of coffee.

In the recovery community we call this state of being "dry", as in "dry drunk". The concept is that while she's managed to stop taking the pills, she hasn't addressed the underlying problems. It's especially likely when someone is getting clean in order to accomplish something (getting one's kids back, for example) other than freeing themselves from addiction.

As a recovering alcoholic, I can confidently say that this is not correct. Although many alcoholics get in trouble by drinking too much too fast (this seems like an acceptable definition of binge drinking that takes tolerance into account), the key feature of alcoholism is addiction -- that in the face of the consequences, alcoholics do not stop. At the height of my drinking, I was going through about two liters of vodka a day. Despite this, I tried and usually succeeded not to lose control of my behavior. After all, getting in trouble jeopardizes your ability to get drunk, and as an addict, every action I took and decision I made was driven by a simple principle: don't let anything come between me and booze.

> Machine: to find out what happens when we get to the planet earth .

Something tells me the entirety of BSG was included in the training set.

Ah, the seventeenth century. A fuckfest before the word existed.

I have to disagree with you on this.

A language should be expressive enough that it can easily support correct concurrent programming, and readily expose runtimes (OTP is a great example) that have support for concurrency and distributed programming.

However, patterns like message passing instead of shared memory are not a panacea. Deadlocks and non-deterministic behavior can still happen in such systems if programmers do something stupid.

Enforcing these patterns at the language level smells of the old "let's make a language that doesn't allow programmers to write bugs!" trap.

This is all true, and it's wonderful!

I fired my previous employer for unethical behavior. They told me to settle down and act my age, so I responded with my two weeks notice, at which point the asked me to leave immediately.

The following job search consisted of one phone call to a friend who was working on a promising startup. The job search was a bit of luck of course. It usually takes me at least a day or two and multiple phone calls, emails, and messages to find a new position.

I'm curious as to why? It sounds like an exciting experiment!

Incidentally, when the startup I work for reached a size where most companies would have started hiring managers, we reached a consensus as a company to give the holocracy thing a try. It's been working very well for us, but we're still < 100 people, so we'll see if it sticks as we grow. Me, I might bail if we turn into a big boring manager having company.