Sorry your browser is not supported!

Alright, I really need to talk about my problems, and hopefuly some people will attend to give me some advise. (really thankfuly appreciated)

My problem is... errr... actually... it's a little COMPLEX! or un-usual , but I try explaining!

VISION: Have you ever heard 'Measure twice, cut once'(it explains alot...)
Have you ever seen guys/gals with no experience, trying to make next gen games or HL3!... OR people who ask a really basic and frequent question, without even reading the FAQ or searching the web/forums! (one of those a hundred times asked/answered questions )

PROBLEM 1: I think I'm exactly the opposite! I'm always measuring... so no 'cuts'!
The cutting part is my goal, but I'm so worried about it! so I'm always, JUST, measuring!
I hate double posting, asking stupid questions, bugging the forums or the people, etc. so I'm always trying not to do them! (except this time )
When I have a question, I really try my best to find/search the answer by myself... I guess that must be a good thing... but sometimes I just feel that's not the best way... it feels like searching the whole city for a shop because you are shy to ask people for the address! (how stupid!)
So a common, easy and solvable problem becomes a monster, it's like searching all the day for a 5mins away answer!

PROBLEM 2: What do the developers mean when they say 'with Linux portablity in MIND' or something like that... sometimes it's like designing a car that is a normal one, but the design was somehow planned so they can make it fly if needed... just by attaching a certain jet engine to somewhere certain in the car which was planned before making the jet engine nor the car!!!
Is that a vision or just experience? (or both)
How do they make/design a normal 3d engine, then implement some more complex things like shaders, etc. without rewriting the whole rendering engine? this must be something more than theories, software engineering, etc. (maybe a vision achived by experience?)

PROBLEM 3: Some people show their work in WIP for some reason... I think there are lots of things envolved, like needing help, needing comment, needing asure, finging bugs, testing, or just showing off, and so on...
But I need something besides... I need to know if my design/plan is a good one...! did I think about everything, is my goal achivable, what are the things I will/won't need, how do I follow the steps in the duration to meet the deadline, etc.

PROBLEM 4: If your native language is English then give me a point between 0 to 100, because that's really annoying... I mean not knowing that people would get you right or wrong is very annoying...!

If you have anything to share then do it, that might be the key to open up any of these locks, or might be the key that I'm looking for...

Oh... and something more... about books and their size, reading and practicing... OK, no more questions for now... just wrote it to remind my self!

best regards.

They mean that you shouldnt use windows-only libaries, if that is possible. Generaly, it means not to rely too much on one kind of platform. Linux is growing up, some big companies use it in critical tasks and if it becomes THE operating system, it's not good to code it from beginning if you could have coded it thinking portability.
Your explanation is not what I would call the situation. It would be more like desinging a car that runs on every road, even in those which are used currently only in maintainance tasks, not only in the most common public roads.

Look at Torque (it also runs on linux). You can also add shaders to DBP.

You know, people dont usualy read posts that long when it's about personal problems. "Linux" -word just popped out there.

I was about to knock off for excessive use of elipses and exclamation marks , but I understand your frustration. 100/100


You want to be precise, and plan properly, so that when you implement your design in code it works with as few quirks as possible? Out of college I'm finding you and starting a game development studio with you as the lead project manager. You may be able to save yourself the worrying by planning stages of a project, stages in which you only want one maybe two features working correctly, and a few others with anticipated bugs that can be addressed after this particular chunk of code has been written. This will also get you thinking about a more efficient way of designing the technical aspect of a program, making everything modular so that you can isolate specific areas of the code, making it easier to fix or add things.

You keep measuring, and not cutting?
Cut, then. Weild the axe, and chop the program out of the wood.
You have measured your wood for long enough.