Yo!

[Greyth]

Heya folks. Been lurking for a couple of weeks, so tonight I'm sticking my neck out and making a few posts.

I'm a developer, and I've been working on my game shogunwars.com for a couple of years now.

It's crazy that I never ran into this forum before. If I had, perhaps I wouldn't be quite so near development-invoked insanity now. An oasis to discuss game issues with people who actually understand beyond a player or layman's perspective... simply outstanding.

It makes me want to do a herkie, but I've been a programmer too long and the effort of that would break me.

So instead, I'll just leave this intro. Glad to meet you all.

++++ EDIT

Bah!... and now I see I posted this in the wrong place. Well, now I know for next time I introduce myself...

[Zeggy]

Hello and welcome
I'll move your topic to the right section.

[JGadrow]

It makes me want to do a herkie,...

What? lol

[Nox]

I wondered too ... http://en.wikipedia.org/wiki/Herkie

Hi Greyth!
Welcome aboard. Well I'm quite new as well, but I guess I can welcome you too
Definitely agree - this forum is great
...and...let us know when your near-insanity passes

[jannesiera]

Welcome, Greyth! I'm always happy if a new member introduces himself / herself ^^.

[Barrikor]

Hello 

[Teckniel]

Hello there.
welcome to the forums

[blindangel]

Hey there!

nice to meet another coder like myself... nearing insanity lol

Only thing I can recommend is dont stare at the code to long, if you look at the same problem to long it just gets harder to find the cause as your mind knows what the code is ment to do and so misses the problem, move on to some other area and come back to it later with a clear mind... if thats at all possible

Look forward to hearing more of the developement of your game

[Scion]

leaving it and coming back later can be a double edged sword....on one side you might see it in a new light, but on the other you may have forgotten what you were trying to do....and so youll have to re-read (and understand) your existing code....which isnt allways as easy as youll think it will be when you wrote it.

My prefered method for solving problems that seem intractible is to find someone to explain the problem too...9 times out of ten the mere act of explaining the problem in a clear and concise way so that someone else can understand it will lead you to the solution....and for the 1 in 10 when it doesnt if you chose the right person then they may well be able to help you out.

[JGadrow]

My problem is that the companies I've worked for I've been the sole developer. I thought the days of the 'lone developer' were over! I was looking forward to dealing with others, managing code through a repository, having code reviews... *sigh* Maybe one of these days I'll work for someone who actually has a clue. lol

But, I can say that taking a break does help. Taking a break doesn't have to mean days or weeks at a time. It could be as simple as an hour or two. Go work on some other project (you do have more than one right) for a little while and when you come back, look over it again. Usually you'll have a fresh perspective.

The 'think the process through' solution can help a lot of people as well. However, I usually do this process before a single line of code is written. Basically, my scripts are usually a set of comments about what the process WILL do and then I fill in the code to make it happen.

You make a lot less errors this way (not that you should EVER consider your code error-proof!) and your code will be nice and clearly commented for you to return to later.

[Scion]

Aw Jeeze Makari i feel for you mate.

The closest ive ever come to not working in an IT firm was a Software firm that was owned and operated by a non IT firm, although we did have a team of between 4 and 12 trained IT staff.....and that was bad enough. IT and Buisness folks just talk and  operate on two completely different planes. When we say if we spend 20% longer now righting the tests up front they hear im going to have to spend a whole lot of cash and have no functioning code to show for it.....or We need a test environment translates loosly to they want twice as many machines for the same amount of work....

Still....it has to be said...we dont get to do code reviews either....mummble mummble....

[JGadrow]

lol Yup. However, I have 3 interviews in the next two weeks. All of which are for development shops. And all of them have mentioned they have a team at least 3 strong and have code reviews. *crossing fingers*