| | _V_
Account closed
Registered: Jan 2002
Posts: 124 |
One Man Army
(I wanted to post this in the LCP thread at first, but it is not really on-topic. Still, I'm interested enough to find out what you guys think, so it turned up here)
To one-man-armies and 'multi-taskers' such as Dane, Hein, Hollowman, HCL, Jeff, etc... Manfred Trenz... :
You know, I have been thinking about joining Dane's one-man-army club, but I'd rather focus on the things one does best. Spreading out your forces eventually eats the time you have available, and you can't do as much for each thing as you'd like.
You do have the advantage of being without conflict as far as the implementation of one's ideas is concerned, but I have a feeling that you get this feeling of "...if I had the freedom to only do *insert element here*, I would have had the time to go much further."
Doing two things is already 'dividing'... what's your viewpoint?
What do the other 'multi-taskers' think? Work in a small group for focussed teamwork and more time for what you like most, or multi-task for a better overview on the prod?
In your opinion, is multitasking a result of necessity, or general interest and love for the c64? Other reasons, perhaps?
Let's talk =) |
|
| | ChristopherJam
Registered: Aug 2004
Posts: 1408 |
For me, multitasking is partly about control and partly an ego thing - I want to say to the world 'hey, look what I can do!'.
I can't speak for artists in general, but I know that coders have a definite streak for not liking to use other peoples code because they think they can do better - one-man-army (OMA) just takes that pattern to the next (il)logical level :)
OMA also saves attempting to find other people who you can work well with - no "interviews", no asking to join groups, no arguments about how best to do something, or who gets to do what.
There are definite downsides; biggest is that your time pressure is multiplied by an order of magnitude. The other is it's hard to find time to keep well rounded. I haven't regularly composed in ten years, as my full time coding job was very demanding. Pixeling's also been thin on the ground for a while. Someone who only does one thing will always have more experience in that one thing than anyone who tries to do many things
Of course, that way you also lose out on the cameraderie (group good feeling) of working on a group production. You also miss out on the sort of creativity you get from bouncing ideas off people.
I like the idea that the scene seems to be becoming more fluid - more cooperation between groups, more collaboration between people who just happen to get together for a single production, and maybe do it again some time.
And if people also act as OMA inbetween working with others, then that's more demos for us all to appreciate :)
c.
|
| | Hein
Registered: Apr 2004
Posts: 947 |
For myself, I know I will never be a proper programmer, so it would be a waste of time, if that excists, to try to become one. It's always difficult to get multiple noses in the right direction, at least more difficult than my own nose. I'll always agree with myself about ideas. And, ideas that are on the edge, can become dull when a few people try to make a compromise. Ofcourse, it's a lot of work if 1 person has to do everything, which may also result in a half product.
Personally, I like teamwork, hearing different opinions, discussions going on, possibly even fights over a simple idea, but if u can stick together after a fight, you know it's been worth the black eyes and bloody noses.
Professionaly I think it's best to have all tasks divided so productivity will be quite fast, and everybody will be happy with their bankaccount, and with their freedom of exploring 1 task as deep as possible. It's boring that way, and can be annoying for instance, if a coder has a great idea about design, but the designer doesn't think it's great at all. This ideal situation can only be found in Star Trek, not in the real world.
Than again, this scene is not about profesionalism, rather about enjoying your time with what one does. So I guess a one man army attitude is just as cool as team work, but like I said, I prefer teamwork, which is good for the ego, give and take, so to say. |
| | Stryyker
Registered: Dec 2001
Posts: 468 |
I guess if the one man army decides their weakest area(s) is(are) dragging them down then maybe drop them. For myself I have wanted to have the thought patterns so I could draw - I have long wanted to make a all on my own. Too bad I just give up with gfx not even trying :( |
| | SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
I do more things that I can count, but they all lead in the same way.
Coding makes order in chaotic thoughts.
Chaotic thoughts for patterns that become music.
Seemingly non-related things, all lead to the same, they all want you to make your innermost dreams happen.
So I don't think it matters how many things you do, as long as you know what you want in the end.
As for working with others, I do like company, so I will involve others, as needed.
In some areas, teamwork is required, in others not.
Let the situation decide what is best, and always follow your inner self, then it cant go wrong. |
| | Dane
Account closed
Registered: May 2002
Posts: 421 |
Well, I do what I think is fun. I started pixeling and I enjoyed it, next I started playing around with music - but that doesn't mean I stopped pixeling really, just that I did it less often. Nowadays, I often take breaks from either music, graphics or code to focus on one thing - what I find is most fun at the moment.
And as far as coding goes it's always been about taking my graphics or music to the next level. This is why I do graphics formats and weird players. I'll never be a math guru.
As to working in a team versus doing it all yourself, I'd say my best experience so far was working in a tight team doing Cycle as a duo with Hcl. I want to be able to have a say about what things look like and sound like and what they contain. I just can't live with sending a prv to someone and say 'insert random effect' or 'insert random logo'. Sorry. I'd rather do things all by myself than with someone who I can't work with. Thankfully, it seems I've found someone. :) |
| | HCL
Registered: Feb 2003
Posts: 727 |
As i'm almost questioned, i feel i have to insert a few lines here as well.
I started with doing gfx, then i made some music, but since 10+ years i mostly code. In the beginning, the thrill of coding took overhand. But at the time i started to know how it worked, the scene started to decay. I almost had to do everything myself in order to release it. Since then i have slowly worked my way up from being a OMA, to having a whole team (2 people ;) working with me.
The pros and cons have already been mentioned, and like some others i do some gfx from time to time when i get inspired, but rarely music. To me it's a relief to have someone else helping out with music or gfx, maybe because i remember the time when i had to do everything myself. But not only for the effort, nowadays i'm totally convined that the final result will be better if i don't do it all my self.
..and yes ofcourse, Cycle is a star up in the sky. Maybe not as a demo (it's only #9 today ;), but the teamwork was really perfect. I still can't imagine how we made that demo from scratch, starting only three months before it was finished. Sometimes 1+1 is not 2, but 7. |
| | Cybernator
Registered: Jun 2002
Posts: 154 |
HCL wrote:
> Sometimes 1+1 is not 2, but 7.
And what math theory implies this? :P |
| | _V_
Account closed
Registered: Jan 2002
Posts: 124 |
Thanks for your input, everyone. It seems like OMA grows from being motivated to do something, but standing alone at the same time. Of course, there is also the motivation to learn everything about the c64. Since this is cool, OMA is cool too.
On the other hand, some feel that teamwork is better and personally, I agree. Cooperation allows you much more focus on the things you love the most (because I would find it hard to believe that someone has no preference between graphics, music and coding).
But yeah, then there are those moments where 'nothing happens'. A big project is finished, everyone takes a break, and it will take a certain amount of time before you're motivated as a group again.
This leads me to another question: During those periods, while you're waiting for the others to have time again, would it be wise to go OMA? Or would it be wiser to stick with your specialty and simply keep practising it so that you're at your best when the others come back?
I've been playing with these two ideas for a long time. I know I could be a good math coder if I would get myself to learn assembler, so OMA is a possibility. Conversely, I'd like to make some damn fine graphics and/or music, so just keeping it slow and working on those things quietly is very appealing, too.
What do you think? Is there a wiser choice, or does it really not matter?
PS: HCL - You were directly questioned, btw. =) |
| | macx
Registered: Mar 2002
Posts: 254 |
>I like the idea that the scene seems to be becoming more >fluid - more cooperation between groups, more collaboration >between people who just happen to get together for a single >production, and maybe do it again some time.
exactly!
eventually groups _may_ become obsolete as we're all individual artists trying different ways of expressing ourselves individually or in some context.
the thing is that the scene has matured and it is more contemporary. we're making demos for one another, not trying to make demos for those we were when we were 17. hence less and less nude phantasy chicks.
but also that there are nude phantasy chicks for those who like it, and coder pr0n without any design whatsoever :-)
in any way i believe these changes are for the better and it also gives me good hopes for the future demoscene. |
| | HCL
Registered: Feb 2003
Posts: 727 |
@Cybernator: > Sometimes 1+1 is not 2, but 7.
And what math theory implies this? :P
Hmm, i was hoping the text explained that.
@_V_: What do we do inbetween great releases? Philosofying at CSDB of course ;) (at least noone can question the truth in that). My intention says that you're worrying too much, do what you feel like, how can it be wrong. Or take the opportunity to just fantasize about the next demo or whatever you want to do. You know how it is, this is the short time of freedom when everything is possible. Later on reality hits you and you have some impossible demoparts to finish ;).
|
... 12 posts hidden. Click here to view all posts....
|
| Previous - 1 | 2 | 3 - Next | |
