Slashdot Mirror

> It's one thing to be working with intelligent, science-oriented people. It's better to be working for intelligent, science-oriented people.

Consider the fates of companies ran by "intelligent, science-oriented people" like ArsDigita (account #1, account #2) and The MIT Blackjack Team.

Though the Really Extreme Programming where one developer sits on another developer's lap does show some promise

If my XP partner looked like this, oh yes. But usually they look like this, so XXXP ain't too hot for me.

There have already been many things written about professionalism in programming, e.g., philg,
jwg.

As for me, I made stupid / humorous / profane remarks in real life. My code is about the same. If it's designed well, works well, and J. Random Hacker can understand it from reading the comments, why would anybody give a rat's ass what sort of shit I put in there? (My boss sure doesn't. My users sure don't.)

The Ars Digita story is a classic example of what Cringely is talking about- a company run into the ground by "professional" managers brought in by the VCs. Here's the story, as told by one of the company's founders:

http://eveander.com/arsdigita-history

Even though it's "just one side of the story," the consensus is that it's pretty close to what really happened.

In the end, the VCs cut a deal with Redhat, who hired a few of Ars' staff to make it look like the company was successfully sold. Fortunately, Ars' great products live on as open source software, OpenACS, and Redhat's CCM. Though Ars' incompetent management pushed CCM as the next, great version of their software, it was never more than vaporware. Redhat has continued to develop it, but it's still not finished.

Because it's multi-threaded. There are a bunch of strings attached when you thread stuff. For example, thread children all operate in the same memory space (as opposed to the pre-forking Apache 1.x, where each child process had it's own memory space)... that alone has a HUGE impact on how modules must be coded. In order to maintain backwards compatibility, a hybrid pre-fork / thread server setup would have to be constructed.


yes, but a proposed backwards compatibility API (which could thunk to the new API) could take care of the thread synchronization and communication BEHIND the API, without the old Apache 1.3 modules knowing the differences. As long as the old API maintains the same interface promises, then old modules should continue to run (but probably with performance problems).

I'm surprised there hasn't been more work to create something like a "mod_apache13" to ease module transition, instead of forcing module developers to break everything all at once. Someone created a mod_aolserver to allow .ADP scripted pages for AOLserver to be interpreted on Apache 1.3. I don't see why someone can't do the same for Apache 1.3 on 2.0.

I'd rather hook up with Eve Andersson in Guatemala.

http://eveander.com/cancun/images/43.jpg

Caption: You're my best sex partner

Say something clever about this pic. Go nuts, kids.

Hoochi mama! Damn I'm lonely. I fantasize about girls like that so much I could never approach one.

Damn, you're not kidding!

This may be pretty darn superficial, but what the heck. Eve, is one cute geek-chick. :)

I want to know what Eve Andersson will be doing now that ArsDigita been sold...

I suppose that hiring her as my personal masseuese isn't very realistic.

steve

I remember now.. it was from this page:

http://eveander.com/trivia/

(I think the questions are randomly generated so you won't find it every time.)

Pi rules!!

3.1415926535.....