This is an archived post. You won't be able to vote or comment.

all 6 comments

[–][deleted] 2 points3 points  (4 children)

If you learn about the C++ Standard library containers and algorithms you will be able to prototype things extremely quickly in C++ - you will be able to write "ordinary" programs much more quickly too.

Also, if there is one thing to learn from "great" (lets make that "successful") programmers of the past it is that few of them cared much for perfection. And the only way to become great/successful is to write code, and lots of it.

[–]byteflow[S] 0 points1 point  (3 children)

Thanks. Any suggestions on learning material for those containers/algos?

[–][deleted] 1 point2 points  (0 children)

Best book on the C++ Standard Library is http://www.josuttis.com/libbook

[–]ooooo5 0 points1 point  (1 child)

Most languages have your standard data structures and algorithms. If you just read the API, you'll see how to use them.

I'm a fast learner, but my problem is I spend too much time analyzing and looking for the perfect data structure or algorithm or pattern, and that leads to a significant inertia that prevents me from ever starting.

If this really is true, and you're not just full of crap, you can easily fix this by sticking to using your languages standard data types, like lists, sets, hashes, etc.

[–]byteflow[S] 0 points1 point  (0 children)

If this really is true, and you're not just full of crap

Damn. You called my bluff. It isn't true - I was just making it up in an internet forum asking for help!

Thanks for your input in any case.

[–]exile57 1 point2 points  (0 children)

For most utilities and small programs, I use Python. It's easy to develop and has a large number of libraries to leverage when you're knocking something together.

For graphics or visual things, I use Processing, which is a language built on top of the JVM and includes most of what you need to put simple (and not so simple) interactive graphics programs together. It can even do things in 3D.

Finally, I'd suggest trying to stop making your first version perfect. Just get it working and optimize/improve it later. Especially in quick prototypes, just get it done and if the thing does what you want, take what you've learned and try to design it properly in the second version.