Programming ways

The more you program, the more you remember.
I use my references quite often, and see nothing wrong with that.
More importantly, you should develop an instinct of where to find stuff when you need it.

When I started "looking" at OpenGL a while back (Before I started getting to the advanced C++ stuff), I made a reference using notepad. That helped. So I guess I''ll make one for C++.

---

E-mail:wiseelben@wiseelben.com
AIM: WiseElben
ICQ: 299127026

[edited by - GameDev Staff on September 27, 1989 9X:58:97 XMS] For violating Article 43 Page 456 Paragraph 251 Line .042]

Don''t worry, when I learned C++ I felt bad because I always had to look in a book to find out what I needed to do, or go copy someone elses code. But the more you code, the more it gets in your head and you will eventually remember all the important stuff.

Shrug I usually have to look up most functions... As such I prefer some templates that expand to hints of what function params are... works like a trick, I just need to make more of them.

In this context templates means a macro expanded by a typed in word. (for those who use VIM, a modified DrCStubs.).
I.e.
memset`
becomes
memset(«PTR_to_dest», «char_to_set», sizeof(«PTR_to_dest») );

I have keys mapped to easily jump between the «» chars. (markjump.vim)


So in short, basicaly how I do it too.

:wave
Feral
p.s. as I know a few vimmers are around if there is interest I''ll hurry up my posting of my modified DrCStubs.)

i have something against looking up stuff. Now when i think of this ,it has contributed alot to my very slow learning speed

I usually look at a reference too. And I also generally make my own references depending on what I''m doing.

Those aren''t bugs, they''re added features

Okey. Good.

---

E-mail:wiseelben@wiseelben.com
AIM: WiseElben
ICQ: 299127026

[edited by - GameDev Staff on September 27, 1989 9X:58:97 XMS] For violating Article 43 Page 456 Paragraph 251 Line .042]

There''s no reason to be worried about looking things up. This isn''t some highschool test or something, and employers aren''t going to fire you for making sure you do your job quickly and accurately.

A good programmer is not defined by how much he can memorize, but by how fast he can look up relevant information.

References are your friends, use them. If you work in the industry, you'll be looking up things all the time. It's a waste of brain-power to memorize things like entire APIs of class interfaces. Keep your head clear for the important parts of programming. Your mind should be developing and implementing algorithms, instead of being abused as an API reference database.


[edited by - Yann L on August 7, 2003 12:07:03 AM]