I got a question that some of you may be able to comment on...
I took C++ two years ago, and got to pure virutal functions. I have since taken java, and I am frustrated by its sluggishness.
So I started Direct X. I understand the concepts, and most of the coding, but its getting heavy. Should I abandon Direct X and go back to C++? or muck through it, and learn the forign syntax along the way. If you think I should go back to C++, where are some good tutorials? (besides this site).
I cannot say that I am solid in C++, but im not jello either... I'm in the middle O_o
lol if anyone can make sense of that cool, if not, im going to go douse myself in water to avoid the flames O_o
thanks again guys for your response,
I find that I can't force myself to learn something if I'm more interested in something else. If DirectX is what you want to work with and you have enough C++ experience to figure things out, then you should do that. Of course, that's not to say that going back to pure C++ won't do you a world of good. :D
learn algorithms, they are kewl k
lol any tutorials or sites that would aid me in learning them???
I love to solve problems, and even tho I suck at it, knowing algorithms would help =)
Learning algorithms thoroughly would be a life long process. I've put a great deal of effort into algorithms and data structures, and I've only scratched the surface. But you can get a good idea of what does what and get a basic idea of how it works here. Eventually though, you'll want to invest in a few (dozen, if you're like me and need plenty of different examples :rolleyes: ) books on the topic.
So as to avoid scaring you off algorithms and data structures, my experiences have been VERY rewarding. :)
rewarding as how?
are you a better programmer inspite of algorithms?
I find myself often taking alot of time to solve problems, and sometimes the long way O_o, would this help me solve problems better???
if you're not using algorithms, you're not programming
>rewarding as how?
You mean aside from looking like a total genius when I talk about it and watching people's eyes glaze over when I get into the theoretical aspects? :D
>are you a better programmer inspite of algorithms?
I'm a much better programmer thanks to the time and effort I put into learning them.
>would this help me solve problems better???
Yes, the benefit would be twofold: 1) You would learn how problems were solved before and be able to apply that prior art to your current problems and 2) The very act of learning algorithms will take you to new levels of proficiency because they permeate, well, everything. :)
yea i agree, but there ARE better ways to solve problems, granted big O notation is the judge jury and executioner of algorithms, but there has to be some way to do things the fastest way possible without breaking your head over it...
>granted big O notation is the judge jury and executioner of algorithms
By far the most well known at least.
>but there has to be some way to do things the fastest way possible without breaking your head over it...
Elegance takes work. The trick is finding a happy median of run-time performance and programmer productivity. :)
> but there has to be some way to do things the fastest way possible without breaking your head over it...
and there's just gotta be some way of making a million bucks without working >:(
i'll give you that answer and more once i finish this infinite compression algorithm i'm working on here
heh you and I both brother :cool:
Compression algorithm eh? I may have something for you, My final project in the C++ course was a DOS zipper. It turned the data file (only tested with text, but it converts the file to binary regardless so anything should work) into binary, then I do binary folds....
it kind of sort of worked.. but it could have been optimized 100 times over :rolleyes:
binary folds are a nice compression approach, just put the binary rows and colums in a 2 D array, and fold from a -j and recursively get smaller, mapping out the points where you folded. I had some little code, i think its commented at the top, but its on one of my thumb drives somewhere... ill look for it if you want me to
it's ok, twas just another bit of ridiculous to add to the impact
i'm done with compression algorithms right now :~
I took a look at that page u said for algorithms... WoW, talk about a wealth of knowlage O_o
i dont know where to start... and what to expect at the end?
any tips on starting out???
>any tips on starting out???
Sorting and searching algorithms and basic data structures (linked lists, stacks, queues, binary trees, etc...) are a great place to start.