Re: Some Advice.
From: Joec (joec_at_annuna.com)
Date: 02/14/04
- Next message: Digital Puer: ""Thinking in C++" vs. "C++ How to Program" vs. ???"
- Previous message: Joec: "Re: Some Advice."
- In reply to: Mike Wahler: "Re: Some Advice."
- Next in thread: Mike Wahler: "Re: Some Advice."
- Reply: Mike Wahler: "Re: Some Advice."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 14 Feb 2004 02:35:43 GMT
Mike Wahler wrote:
> "Joec" <joec@annuna.com> wrote in message
> news:N9cXb.2961$WW3.1845@newsread2.news.pas.earthlink.net...
>
>>
>>Robert W Hand wrote:
>
>
> [some good advice]
>
>
>>Wow thanks for the tips.
>
>
> Yes, imo Bob's advice is always worth listening to.
>
>
>> Some of them I am learning as I go along. I
>>am learning that naming is far more important in C than in Perl.
>
>
> IMO it's *always* important, regardless of language. It's a
> 'quality of work' issue, not a language issue.
>
> Source code is primarily for human consumption. Think about
> trying to read and understand your code after being away from
> it for a year (or more).
>
>
>>Writing a program and learning is very fustrating.
>
>
> I feel your pain. We've all been there. :-)
> But, learn by doing.
>
>
>>I want to learn. I
>>can read books on syntax and theory all day but it doesn't matter until
>>it is applied.
>
>
> Right. Practice, practice.
>
> Hang in there. :-)
>
> -Mike
>
>
Again thanks for the tips. It is good to hear from people who do this
in the real world. I hope to be there some day. I never realized that
programming involved such basic skills.
I really wanted to study programming in school but the stiff math
requirements kept me out of the field of study. The more I get into and
learn programming the more I learn that programming I more like a
liberal art than a science. Yes math can be involved if it is necessary
for an algorithm but writing a program is more like writing a good paper
than doing math.
In my current project like all I have had in the past and you can see
them, I have had my share of bugs and problems to solve. 70% are simple
mistakes, Curly braces, putting a < backwards or leaving off some part
of initialization or command. I like C++ because the compiler quickly
finds many of those errors. 20% are bad logic. I just did something
wrong and I have to re-think my program. 10% are that I don't know the
syntax. Perl was really bad for that in complex data structures.
I have been writing demo programs and posting them on my page. I get
really excited and proud when I learn something like inheritance,
creating a dynamic array or reading and writing files. There is alot of
code out there so a lot of people do it, it can't be that hard.
This program I am writing I have done already in perl. I came up with a
better basic design for the program. The map in my Perl game was a 2d
array of characters but in my C++ it is a grid of objects. That solved
many of the problems I was having trying to expand the game and make it
better. My work with and studying of C++ has given me a better ability
to write that program in perl.
Again thanks for reading my messages mostly they are 70% frustration and
30% question. I hope that my code can be seen and I get some advice why
my return character function won't return the character when I draw the
map but will when I use a debugging flag or cout in another part of the
program. I will do some reading and go over my code again in a few days.
- Next message: Digital Puer: ""Thinking in C++" vs. "C++ How to Program" vs. ???"
- Previous message: Joec: "Re: Some Advice."
- In reply to: Mike Wahler: "Re: Some Advice."
- Next in thread: Mike Wahler: "Re: Some Advice."
- Reply: Mike Wahler: "Re: Some Advice."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
