Log in

No account? Create an account

Previous Entry | Next Entry

Mar. 15th, 2012

- came across *another* bug i encountered before and apparently hadn't fixed (though i thought i did) -- argh. investigating. seems to be two separate problems, but maybe they are connected...
- okay after lots more work i think i have those bugs fixed. i'm increasingly frustrated by the amount of time spent fixing bugs and not adding new things to the game. but at least i am managing to fix them as they are found


( 3 comments — Leave a comment )
Mar. 16th, 2012 06:05 am (UTC)
From an earlier entry: http://rinku.livejournal.com/1949305.html

most games are at their core not difficult or interesting to program. 99% of the code of any game is interchangeable, boring, and trivial to code. people who are programming geniuses *should* be bored by coding games, because game code is not supposed to be challenging or interesting, it's just supposed to work.

While it's true that it's easy for some people to get lost thinking about implementation systems and losing sight of the high level game design, I still feel that programming a game cannot be assumed to be easy unless you're just making new content or a mod for an existing game or engine. Or unless you're making something like Johann Sebastian Joust or whatever. I mean there are plenty of games that don't have much code, but if the game *does* have a lot of code, it takes a lot of discipline to structure the code in a way that minimizes time spent fixing bugs as the code grows larger.
Mar. 16th, 2012 06:41 am (UTC)
i don't really think it's *difficult* to program this game at all, just time-consuming. finding and fixing bugs isn't especially challenging, it's just tedious and repetitive. that's not to say that that in itself isn't a form of difficulty, since it does challenge one's patience, but what i meant in that quote was a different kind of difficulty, one that challenges the intellect or creativity. i don't feel that fixing bugs challenges my intellect or creative imagination, which is exactly why i don't enjoy it
Mar. 16th, 2012 06:43 am (UTC)
i'm also not sure that the bugs arise out of code size per se; i feel that the "proportion" of bugs is the same regardless of code size (e.g. one bug every 1000 lines or something like that). so more code does mean more bugs, but the bugs are not caused by the organization or structure, they're just usually localized bugs in the way particular functions work, at least in my case

(it's likely a larger code size makes it harder to *identify* bugs, though, but that's a different thing than being the cause of them)

Edited at 2012-03-16 06:44 am (UTC)
( 3 comments — Leave a comment )