The fact that you must have an engine to build a non-trivial game is a fallacy, something perpetuated largely by people who don’t know any better.
@LazyLizzard said:My list of corporate examples is classified, but in real terms I would have never discovered my clever little path finding technique if I didn't figure it out myself and without it, I wouldn't be able to draw thousands of independantly moving Zombies on the screen. No, I don't use A* or any variant thereof.
Why re-invent something someone else has already done? Simple. For the same reason you play a game that someone else has already finished. It wasn't you. It's a cliche, but it's true for me.
What may be reality for you is an untested, unfounded assumption for hundreds of kids trying to make games and starting out the wrong way
I don't think you're properly aware of the experience of the developers that are saying people who write engines with no game in mind make poor engines. We've all made our share of engines, good and bad. We've watched hordes of people assume that they're this generation's Carmack and end up never producing either a game OR workable engine.
@LazyLizzard said:Ask yourself why aren't they on these forums and if they are, why aren't they speaking up?
@tbulford said:If we make people feel unwelcome because we didn't think they would finish there game what would that make us :0
Bottom line: People know their shit here, despite sounding like they're advocating certain "easy" solutions.
LazyLizzard said:Again, I agree. However, the downside is that programmers end up focusing on what something looks like instead of what makes it tick or how it fits together. That in itself isn't a problem, but, follows the trend of the South African job market where there are an over abundance of half baked coders out there that are nothing more than spaghetti coders with 10+ years of experience. It creates an attitude of buy/want for free/I can't do it myself yields results where sometimes entire projects are the nett result of google'd code that was cut and pasted. With that we lose a part of the thinking process that people like K&R used to make C or Microsoft used to make Windows or Sun used to make Java. It's probably an engineering discussion more that a games discussion but the principle is the same. Heck I don't know if that came out right but I have work to do and can't sit and type this all day,...
hermantulleken said:I don't think trends in there being more half-baked programmers has anything to do with the level on which these programmers learn their skills. I think it's simply because there are so many programmers required and so few of them, that even a half-baked programmer can get a decent job; the average is dropping simply because the pool is growing.
That in itself isn't a problem, but, follows the trend of the South African job market where there are an over abundance of half baked coders out there that are nothing more than spaghetti coders with 10+ years of experience.