best way to lern is brail and arroing left to write ishan u have to understand every / . or any value audio recorde wil not help u for it
Spent some time working on this this evening.
Turns out I have a lot more to say on game design and figuring out what the game we're building is, and justifying my decisions, than I ever had considered.
I'd love to get some feedback from trusted members of the community before posting this next bit, too, as it's a bit less technical, a little more of me trying to synthesize the reading I have done on game design, as well as my intuitions.
So far I am trying to hammer home the idea that a lot of the work we have to do as game developers is not writing code, but is trying to build a coherent world with reasonable rules that can be fun for the player, as well as stressing the idea that we have an awesome heritage of sighted games to tap for inspiration.
I've also got started on part 3, which is a little more meaty, and will have you actually getting a project directory structure with its own virtual environment and will conclude with you having a window up on the screen.
I'm pretty new at any sort of long-form writing like this, and so am trying to figure out stuff like where to cut up my posts so they are easiest to digest. Forgive me for the roughness, I intend to evolve this over time until I'm actually happy with it, but that'll require feedback, which will require me actually, you know, getting it posted
We are here to help.
A good way to slice up posts is in heading form, where the headings represent subsections of the post. Go from the beginning to the end. As in, where someone can follow along with what's being read, and have the post instructions completed by the end. The first post was great, and I was able to understand it very well.
I would be happy to take a look for you, ping me on twitter (@zersiax).
I agree with steev here.
I think you should classified it heading by heading
But sooner or later who win the one who thinks he can!
I wonder if any audio tutorials might be able to be made along with the written blog for those that do better listening to audio and following along with it? I'm much better with audio tutorials myself.
I would make a few suggestions.
First, it can help to keep your goals and your audience firmly in mind. It is also a good practice to go back over what you write with those goals and audience in mind. It is likely that everything you are writing is useful, but you might realize that some of it would work better as a seperate article or tutorial of its own.
Don't fall into the trap of seeking prefection. Most writers have a sneaking suspicion that if they work on their article or tutorial or book just a bit longer, they can make it even better. If you seek to make your writing perfect, you will never post the articles. Instead, try to give yourself a timeframe to complete a piece. Certainly, you can always extend that timeline because life interferes with your writing, but be wary of extending the timeline because you think you might be able to make the content a bit better.
There is a lot of things you can do in your editing to improve an article--and it is always an extremely good idea to let others edit your articles. However, keep in mind that the critical aspect of editing is to remove mistakes amd ensure the content is clear enough to understand. You can get into all sorts of good editorial advice about grammar, spelling, word counts, etc. Those things are definitely useful, but the most critical aspect is to ensure what you write meets the goals and is appropriate for the audience--and mistakes and lack of clarity are the 2 biggest dangers in that respect.
I don't think that would be good. It would be very hard to learn programming with an audio tutorial. It's not like games, where when somebody does an audio walkthrough where you can listen and understand what's going on. You would have to listen very carefully to the code, and I don't think anyone would want to read the code out loud, line by line, letter by letter. To give you an example, on an applevis podcast, they were demonstrating how to use x-code. It was interesting, but he didn't have keyboard echo on so you couldn't hear the code, and VoiceOver didn't read it back. Now I'm not trying to be rude, it was a fine podcast, it's just unclear. Bgt had an audio tutorial, but what you were supposed to do was listen to the tutorial, and read along in the manual itself in case something in the audio tutorial was unclear. That's really no way to learn how to code. If you really want to be a programmer do the work, learn syntax and things. There are plenty of resources available to you. Read CToth's blog posts. Also read camlorn's blog blindly coding. He's always doing interesting things, and reading a blog like that will give you some familiarity with programming. You will get a really good understanding of how code works. You should read lines of code letter by letter, so you can understand what they do. This is something you will have to do anyway to catch bugs. Personally I would suggest learning python, it's syntax is easy to understand, and it's a good starting point for a beginner. Of course you can learn any programming language that you enjoy. It just all depends on your personal preference.
What are you doing! Don't think, shoot!
Can any 1 please give me the link to the BGT tutorial?\
or can some 1 please upload it on some or other survice?
never give up on what ever you are doing.
I think I still have the bgt tutorial but it's very outdated. The syntax that's in the tutorial, doesn't match up to what's in the manual itself. If you want to use bgt you should use the manual that has all the right stuff in it.
What are you doing! Don't think, shoot!