Code center > Darwinbots3

Helping

<< < (8/9) > >>

Numsgil:
Those failing tests are for the continuous collision detection.  They fail because I haven't finished :)  I sometimes use failing tests as todo's when I want to work on something else for a while.  That way when I come back I have something I can work in immediately while I re-figure out the code and what I was trying to do.

rwill128:
Almost done with the copywriting -- gotta pay the bills, etc.

Anyway, I'll be gratefully jumping back into work I want to do (coding related work) at the end of the week, at latest.

Thanks for the information and sorry if it ended up being something you had to get done yourself.

Numsgil:
No worries.

I haven't started working on it myself.  It is super annoying without it, though, as the prebuild step takes about 5 or 6 seconds where Visual Studio seizes up. :/  Probably something I'm going to tackle if you don't in a week or two.

Peter:
From experience getting into code can take quite some time. Especially if you can't play with it full time.
From the peek I did in the code it seems better organized then most projects though.

I might actually contribute at some point.  But I don't have seas of free time atm and the free time I have seems to magically disappear. :unsure:

Numsgil:

--- Quote from: Peter on April 24, 2013, 05:21:11 PM ---From experience getting into code can take quite some time. Especially if you can't play with it full time.

--- End quote ---

Yeah, this is very true.  At work my job is pretty much to find bugs in unfamiliar code bases and it is exhausting.


--- Quote ---From the peek I did in the code it seems better organized then most projects though.

--- End quote ---

Thanks, I tried :)


--- Quote ---I might actually contribute at some point.  But I don't have seas of free time atm and the free time I have seems to magically disappear. :unsure:

--- End quote ---

That would be cool.  There's still enough to do that it should be easy to find some small corner problem in some area you find interesting and work on it more or less oblivious to the rest of what's going on.  I've gone so deep in so many different areas that I imagine it would be hard for any one person to feel comfortable in all parts of the program at once.

...

Also, on introspection, my core coding philosophy is very slow and methodical, to the point of being nearly pedagogical.  I don't mind spending 4 or 5 months researching, implementing, and testing something even when there's an 80% solution that would probably suffice that someone could spit out in a few days.  That's pretty antithetical to how most video game programming is done (I guess I like the change of pace from work).  Many programmers I know in real life would chafe working under these sorts of conditions, so I recognize this might not be a project everyone would feel comfortable working on, even given the ability, interest and time to do so.

Navigation

[0] Message Index

[#] Next page

[*] Previous page