Friend thinks he knows more...

**FuelCap** · 11-08-2005

Originally Posted by Cool-August

My friend uses somthing called HotDog to build web pages.

That is so sad... HTML is the freaking most easy languages[scripting] to learn.

**Jeremy G** · 11-08-2005

Originally Posted by FuelCap

That is so sad... HTML is the freaking most easy languages[scripting] to learn.

HTML isn't a scripting language, its a mark-up language.

Guess it isn't so easy after all?

I only pointed it out because its a common mis-conception.

**Thantos** · 11-08-2005

Having seen quite a few of your programming related posts I wouldn't tout your programming skills as a measure of your computer skills.

I have never had to use that 'help' thing before, I hardly know what it looks like

Hate to tell you but this isn't a plus. I'd take someone who knows how to use their resources to find an answer over someone who can fiddle with the system until they figure out a way. I'd do that any day of the week and twice on sundayss.

**VirtualAce** · 11-08-2005

I think a programmer should know more than the guys at Best Buy who put them together. I'm A+ certified and I'm a programmer and it's my opinion that a programmer should know the ins and outs of their computer system. Especially if you are going to program games. Intimate knowledge of the hardware is essential, not just knowledge of game design. Even though drivers have made this easier, it is not an excuse to be lazy. Often times designers and software engineers point out errors to the driver engineers who then address the issue with a patch in the driver. So the two are not separated by much. And if you understand assembly language then you will understand that the algos in software can then be put into hardware and vice versa. You can't program it if you don't know how it works. You might be able to hammer out something that 'works' but to really program the system and utilize the hardware and CPU to its fullest I feel you need more knowledge than just a couple of C++ courses.

Language is the paint brush and hardware is the canvas.

Oh and I've seen a lot of people like that. Just browse the boards here and you will see them.

I want to program a Win32 app but I don't know C++ or Win32. Please help.

I want to make a game but I don't want to read a lot of books or do a lot of research. I also want to use an existing library so I can avoid the low level DirectX/OpenGL stuff. K thx.

I'm a topper in my class but I can't for the life of me figure out how to write a program that averages grades. Please help.

They are everywhere.

**novacain** · 11-08-2005

"I am not young enough to know everything."
Oscar Wilde

I thought I knew alot about computers after ten years commercial experience building systems and five years commercial experience programming. I don't count any non commercial experience, I have another 15 years of that.

Then I meet a tech who showed me the actual 'ones' and 'zeros' passing through the BUS of a computer on an oscilliscope

Soon you realise how much more there is to learn......

**jmd15** · 11-08-2005

Originally Posted by Bubba

I think a programmer should know more than the guys at Best Buy who put them together.

I think that most programmers do know more than someone at Best Buy, but what I was trying to point out was that there are people who may not be able to program, but can know more about computers than a programmer. Although, a lot of times if they get into computers that much, they will start doing a little programming as well.

**BobMcGee123** · 11-08-2005

Hate to tell you but this isn't a plus. I'd take someone who knows how to use their resources to find an answer over someone who can fiddle with the system until they figure out a way. I'd do that any day of the week and twice on sundayss.

I think I agree with this more than anything posted thusfar.

I remember all through high school I would use computer lab time to write little 3D computer games. Very often, the hardest things to write granted me almost no respect due to their obscure nature, but the relatively easy stuff that simply produced pretty graphics made my comrades nearly poop themselves because it looked pretty.

**Queatrix** · 11-08-2005

As I said, I am only 14, so I know I have gobs more to learn, and that to a computer guru I might not be very advanced at all. But on the other hand, compared to the average, I am.

**FuelCap** · 11-08-2005

Originally Posted by Jeremy G

HTML isn't a scripting language, its a mark-up language.

Guess it isn't so easy after all?

I only pointed it out because its a common mis-conception.

Oeps sorry...

**Govtcheez** · 11-08-2005

Your friend sounds like a manager, and is therefore WAY smarter than you.

**BobMcGee123** · 11-08-2005

As I said, I am only 14, so I know I have gobs more to learn

Understanding this is a very good attribute. Just that honest admission alone probably puts you ahead by quite a bit.

EDIT:

Your friend sounds like a manager, and is therefore WAY smarter than you.

I'm going to cut my pinky off and eat it now. Just because you said that. Subsequently, I hate you.

**rockytriton** · 11-08-2005

I work with some people who are programmers (some c, some java, some cobol, etc) who don't know the slightest thing about the operating system they use. This one guy, for instance, he has been doing C for about 15 years, he still doesn't know he uses a multi-tasking operating system. When he checks his email, he closes the window he's looking at, then when he goes to visual studio, he closes his email client. Everything with him is one window at a time open and maximized.

**BobMcGee123** · 11-08-2005

What? Because he only has one application running at a time, he doesn't know his operating system is capable of multi-tasking...I think you're making a bit of an extrapolation here.

**rockytriton** · 11-08-2005

of course I am. The point is, just because he's a programmer, doesn't mean he knows how to use the computer efficiently. He has 2 gigs of RAM and 3 Ghz processor, yet he still opens and closes a new program instead of just opening another instance. We have several projects, if he needs to build two of them, he opens VS, builds it, closes VS, opens another instance of VS, opens the next project, builds it, etc.