Do you think there will ever be the kind of grants for coders that artists enjoy? I think that the open source community deserves some sort of government support for all the work that it's giving away.
it just amazes me that the author of this said the word hobbie a million times without once considering it's meaning. When I write my software I do it for the fun of doing it. I consider releasing it as a nice thing to do, just in case someone might find a use for it or one of it's routines. I don't expect people to fall all over themselves to use it, that's not why people participate in hobbies. I think the problem here is that the open source community was started by people who NEEDED something. Now we have the opposite problem, it's hard to think of something ANYONE needs and doesn't have a million solutions for. The open source community wasn't started by hobbists...it was started by professionals who needed software that didn't exist. I think we need to realize that people aren't programming for anyone but themselves now and there's almost nothing to write that hasn't already been written.
I would like to patent the no-click multi-user dimention. I would like a patent giving me exclusive rights to any text-based system where someone would be able to play, with any number of players, on a system, either paper or computer based, any sort of adventure.
This afformentioned patent would be reserved for any implementation of said system in any language.
I know that this runs against most other people's comments, but I've found that taking a few days off doesn't do me any good. I end up more stressed because I know I have a deadline to meet. I was struggling with coders block for a long time when I got into a poetry writing class. I was amazed at how much of the professors sudgestions applied to both poetry and coding. Here are some that work for me. 1. Just write anything!: If I don't know what to write I'll just start writing stuff that I know is wrong. I know I can go back and change it and the natural need for it to be right somehow kicks in and gets me going again. Soon I erase all the "babble" and I'm writing real code again. It's sometimes easier to fix something than it is to create it. 2. If you can, just work up to the problem. In writing poetry you would try by writing a related hi-ku(sp?). In coding, I usually start by writing a little program that might work along side the one I am working on. That gets me thinking about the functions of the code at hand, without pressuring me to work on it. 3. If you havn't started anything yet, just write the stubs. If you hash out the functions and get them to compile with no code in them, you've got something to work with. Also, it's like moving pieces around on a chess board, it gets you to consider your options. Anyway, these are the things that get me through a long day. I hope they work for you. Good luck!!
Slashdot Mirror
Do you think there will ever be the kind of grants for coders that artists enjoy? I think that the open source community deserves some sort of government support for all the work that it's giving away.
it just amazes me that the author of this said the word hobbie a million times without once considering it's meaning. When I write my software I do it for the fun of doing it. I consider releasing it as a nice thing to do, just in case someone might find a use for it or one of it's routines. I don't expect people to fall all over themselves to use it, that's not why people participate in hobbies. I think the problem here is that the open source community was started by people who NEEDED something. Now we have the opposite problem, it's hard to think of something ANYONE needs and doesn't have a million solutions for. The open source community wasn't started by hobbists...it was started by professionals who needed software that didn't exist. I think we need to realize that people aren't programming for anyone but themselves now and there's almost nothing to write that hasn't already been written.
I would like to patent the no-click multi-user dimention. I would like a patent giving me exclusive rights to any text-based system where someone would be able to play, with any number of players, on a system, either paper or computer based, any sort of adventure.
This afformentioned patent would be reserved for any implementation of said system in any language.
I know that this runs against most other people's comments, but I've found that taking a few days off doesn't do me any good. I end up more stressed because I know I have a deadline to meet. I was struggling with coders block for a long time when I got into a poetry writing class. I was amazed at how much of the professors sudgestions applied to both poetry and coding. Here are some that work for me. 1. Just write anything!: If I don't know what to write I'll just start writing stuff that I know is wrong. I know I can go back and change it and the natural need for it to be right somehow kicks in and gets me going again. Soon I erase all the "babble" and I'm writing real code again. It's sometimes easier to fix something than it is to create it. 2. If you can, just work up to the problem. In writing poetry you would try by writing a related hi-ku(sp?). In coding, I usually start by writing a little program that might work along side the one I am working on. That gets me thinking about the functions of the code at hand, without pressuring me to work on it. 3. If you havn't started anything yet, just write the stubs. If you hash out the functions and get them to compile with no code in them, you've got something to work with. Also, it's like moving pieces around on a chess board, it gets you to consider your options. Anyway, these are the things that get me through a long day. I hope they work for you. Good luck!!