life
My cat is dying. I'm sad. Kirk didn't wear a porn movie BSD shirt to class this week. More on org charts later.
life
My cat is dying. I'm sad. Kirk didn't wear a porn movie BSD shirt to class this week. More on org charts later.
Okay, dhd, I'll turn my thesis into an article. Give me a day or so though, as I'm getting busy these days.
seth's contraversial diary entries
I like your diary entries, Seth. Sometimes I read the whole thing, and sometimes I read parts. If others don't like them as much as I do, they don't have to click on the the schoen link. Choice can be good.
I am happy sitting here with my cat, coffee, and Thin Mints (TM). Girl Scout cookies are almost as good as dandelions in the spring.
More on management, org charts, and open source
Split of traditional management duties into several functions:
I may be missing some functions that are necessary. This is also just one way of doing things. This particular break out of management duties is intended for a group of about 10 employees who all get along well. In this senario, about 1/2 of the group would do some sort of management, and the other half would do only technical work. All members of the group are required to be technical and to do technical work. The people who do management duties might find it helpful to have a high level of communication both with each other and with the rest of the group. The people, budget, and project managers might all need to meet at the commencement of any large scale project.
I am interested in seeing if different sorts of groups have different experiences and respond differently to this sort of shift in management. For instance, does this work well with a Web group, does a hardware group have problems with parts of the scheme, how does a software group respond? I think that this particular management scheme will only work for specific types of groups, though I can not predict which ones.
Although traditionally organized companies might be opposed to this type of a power shift, the traditional company might realise benefits in employee satisfaction leading to higher employee retension, higher productivity which could lead to higher revenues, and in savings created by cutting operating expenses. The open source employees win by having a real voice in what happens within their group and company, by having a work environment and group that is responsive to each employee's needs, and by not having to deal with managers who lack one or more essential management skills. In the scheme mentioned above, if an employee has issues with the work place, he or she can do something tangible to change it.
I like english muffins. I like bad chinese food. I like some old movies. I do not like animation.
Do Christian companies do things that their church feels are imoral?
Still no dreams. Still no vacation planned. Too many social engagements. Not enough kernel code read. Resume done. Taxes mailed.
lilo says:
Hmm. You're going to have to hire your open source people with this in mind. Some folks have a real allergy to budgets and scheduling. Others are very focused on managing their own projects but may find time spent tracking projects other than their own not so useful. Still others may be willing to spend time on a variety of traditional management duties.
I know that some people want nothing to do with management at all. However, I believe that there are people in the open source community who have talent at managing some things. The person who is good at project management might suck at budgeting. Someone who finds purchasing is interesting might not care if his or her co-worker is happy with the projects that they are working on. To find one person who is good at management, good with people, good with estimating and tracking money, good with the community, has a deep understanding of open source and it's issues, and is technical, is difficult. To expect that there are enough of these people out there fill all of the management positions in all of these 'open source' companies that are sprouting up is not realistic. There are many options to deal with this issue. I am interested in learning about how companies who have large populations of open source employees organize themselves so that all involved are satisfied. I would like to know what works, what fails, and why.
more on org charts
Why should a group have one manager? Take a small group. Put one person in charge of tracking and planning projects. Put one person in charge of making sure that all of the people in the group can do their job, have projects to work on, are motivated to do a good amount of work, etc. Put another person in charge of budgets and purchasing. Have all people in the group do whatever sort of work the group does.
If more of the group has to do management duties, will they be more responsive to the others who do management duties? Will this break down the traditional hierarchy? I do not think that this will scale very well; I'm not so much interested in scalability.
I am interested in having open source employees who can do technical work, and who can find the parts of management that suit them. I want to spread out traditional management duties, and find ways to have employees take active roles in managing their own groups, if they wish to.
books
are worth going into debt for.
It looks like it's really time to get that resume together. But first, I'm off to get my hair dyed bright red. I can't show up to another interview with roots. It's unbecoming.
Well, since I never seem to talk about computers or open source much in here, let me say this: in kernel class tonight, Kirk McKusick wore a shirt that says, "McKusick does Oz." If that's not a title for a porn movie, I don't know what is. Let me also add that I found fork extraordinarily interesting, and exec very boring. What's up with that?
freeways
I will soon type about my theories of freeways for Nick. Don't let me forget. It's fascinating, I swear.
I have always believed that the difference between a bad work environment and a good work environment is a very small one. Some companies make the effort to understand their employees, and what it would take to make them happy, comfortable, and effective. Others don't care. In the race to make a boat load of money in this current economy, many an employee's needs have been overlooked. Brett has illustrated some of the things that he would like in his work environment. None of these things is unreasonable. I would add the following to Brett's list:
I haven't had any dreams that I remember for a few days. I also haven't planned any vacations for the near future. That said, I must add that interviewing for jobs in the Open Source space is an interesting process.
Someone once told me that to raise people who are to be trustworthy, you must first take a chance and trust them. Trust them at a young age to go to bed at a proper hour, to show up to rehearsal prepared and on time, to treat others with respect, to listen, really listen to what someone is saying when they speak.
Nick pointed out to me the other day that someone else here in this advogato community admitted to having attended Simon's Rock College. I confess that I too have gone to that college. I was reminded of that today by an article in the New York Times. Again. I miss the way that spring smells in the Berkshires.
technology, eh? right-o. i've got kernel homework to do for kernel class tomorrow night. kernel, kernel, kernel, i made it out of clay...
1:30 am
org charts
The only org charts that I have ever seen have consisted of straight lines connecting rectangular boxes. I think that employers should hire people not positions. Therefore, I would be interested in an org chart that is made up of circles that intersect other circles. In a circle there would be a group of people. Depending on the interests of the employee, parts of the circle would touch or intersect other circles. As the interests and skills of the employees changes, the employees in the intersection of the circles also change. The org chart forms around the people in the organization. The org chart illustrates the way in which employees interact to complete projects.
More on org charts later. Responsibility. Accountablilty. Etc., etc., etc.
I woke up to the answering maching taking a message for Kim Cominich. Kim is a reporter who had this phone number before me. 2 years ago. When I went to get my car stereo installed in my new car, the computer pulled up Kim's information at the prompt of my telephone number. I am used to this by now.
There is no need to sleep anymore.
In Mexico I learned restorative yoga. Slows down the brain so that the body can heal. It's better than sleep, and there are no pesky dreams. My dreams while I was in Mexico were mad: a man taking over churches, human blood in a river, an old secret society, flat earth, and a boy who wanted to stop the man, all set in the South.
6:30 pm
Stole some people this afternoon for sandwiches and ice cream. The bravest of us had advogato -- i mean avocado flavored ice cream. I will let her name herself.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!