Is a main programer bottleneck?

What electric title! This is a title of the session in CEDEC 2007.

This session gave interesting hints. The thing OSS should do is not keeping authority (self-presevation), but developing software. To a such purpose, the session presented the important conclusion. OSS may refer the conclusion very much.

Like eating endless meals
The session said; A main programer has certainly higher skills and higher speed than those of company workers. So a main programer has to concentrate on writing programs, not do others. PolygonMagic which spoke in the session bans main programers from the following tasks:

• The “eternal” teller to data.
• Manage the build.
• Director to release.
• Update library, driver and hardware.
• Update In-House Tools.
• And more.

In other words, “A main programer has the most skill, so make him work on code more and more!”. It’s wastefulness that the brilliant programer performs odd jobs which are able to be executed forward by anyone. Code! Code! Code! A main programer has to consider about only code, has to work on only code, and has to fight with only code! Much, Speedy, Powerful, Excellently and Certainly.

Here is an interesting allegorical story. “Wankosoba” is a kind of Soba. Waiters keep bringing Soba until we give up. That’s endless meals. A main programer should only keep eating Wankosoba, not prepare Wankosoba and Japanese teas.

Wankosoba:

Discussion: “This” is in XOOPS Cube
That’s simple strategy known as “Agile software development”, but is difficult way. If someone takes a lead as the main worker, he has to treat many many things. Since XOOPS Cube was forked, I was shocked to have to receive amazing various tasks. Unluckily, most members who were listed on “Core Team” didn’t share tasks and didn’t have good team play, because they were in each circumstances — but I don’t know a detail of them. Anyway it means that “Team System” is unhappy concept for everybody.

But, now, we’re in new freedom concept without bloody team system. Contributors can do anything to the project. By that, program contributors may be able to concentrate into programing. When we consider about this agenda “Is a main programer bottleneck?”, we’ll get the powerful development. The XOOPS Cube community has many powerful programers!

Now what?
That said, the OSS project can’t put in practice. Because we aren’t employees of the project, programers have to do some odd jobs. Non-tech contributors can not steal all of odd jobs from programers.

But, this agenda is worth for us. We’ll discuss it in the XOOPS Cube Developer Meeting.