• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Rig for a programmer?

I wasn't commenting on your will power.. how motivated you were... wheather you could do it... I have no idea on any of that.

What I amd many others are saying, is its not what alot of people think... you might have the right picture in your head... great.. but most dont..

I know alot of people that have gone into programming with almost a mainstream public view on it... and its just not like that...

its kinda like people waiting to be a cop so they can do bad boys II type shit.... aint gonna happen.. Im sure u get what im sayin..

good luck either way...
 
I see what you are saying now, and sorry for retaliating harshly. I could understand how you would feel the way you do, like many others are saying. I hardly know shit about programming, but I know about it, and I doubt its a mainstream point of view. Regardless I could see where you are coming from.
 
I agree with SkitlZ in the fact it isn't what most people expect it to be. It's extremly frustrating and complicated at times and it just makes one want to quit. So far what I've learned has been kiddie junk and is relatively easy and uncomplicated. Sitting and looking at pages of code to determine what your problem is and then realizing you add an e to a variable in your declarations and throughout the entire code you spelled if differently is quite irritating.
 
Originally posted by Stinger836
I agree with SkitlZ in the fact it isn't what most people expect it to be. It's extremly frustrating and complicated at times and it just makes one want to quit. So far what I've learned has been kiddie junk and is relatively easy and uncomplicated. Sitting and looking at pages of code to determine what your problem is and then realizing you add an e to a variable in your declarations and throughout the entire code you spelled if differently is quite irritating.
Click to expand...

what language? most c compilers will catch that cause the variable isn't defined.

if it's visual basic, make them option explicit
 
Well I understand about that stuff and that was just in high school. We made probably 30 programs a semester in high school, and they all weren't perfect. Given they were basic programs using arrays and storing stuff to a file and basics really. However I got a very small taste of it. And I did want to toss the computer across the room on numerous occasions lol, but I eventually got it and everything was fine. I see what you mean, in a newbie way.
 
Save your eyes and fend off headaches - make sure you have a quality video card for 2d (just about any mainstream card family right now should be fine) and a solid 19" monitor. it should be able to do 1600x1200 @85hz, but 75hz will do.

and on a side note, stay away from VB if you actually like programming. VB is a heap of crap for real concepts. and if doing .Net, stay away from VS.Net and learn how to program without. it will make you stronger.
 
problem with programming is, i got burnt out on it really fast :(

that's why i'm now an EE major... same frustrations, only on a different level.
 
Originally posted by plot
what language? most c compilers will catch that cause the variable isn't defined.

if it's visual basic, make them option explicit
Click to expand...

Sorry it was a poor example. But the just of it happens. I was thinking VB but I use option explicit. But that still just leaves the variable alone IIRC. I dunno though Ill check later.
 
hehe. problem with most languages/compilers is if you forget a damn semi-colon or bracket, it shits a brick.
 
Originally posted by primea
Even the considered low-end system today will have no problem with all the tools you've listed ... I suggest just ramping up your RAM, and invest on a back-up solution. Believe me ... you would not want to lose your code after you've spent a week or more on it.

An external drive (firewire/USB), CD-Writer, and a USB Pen Drive ... make mulitple copies of everything ... and if you can setup an FTP server the better ... that way you can download your codes when you forgot to bring it with you.

A two monitor setup will be beneficial ....
Click to expand...
I could not agree more with this post. Especially the FTP bit. Its a godsend, as long as you remember to upload/sync your files regularly.

I've started to work directly from my Cruzer Mini. Its slow, it might shorten its life, but nothing's worse than not being able to submit an assignment because you don't have it. And professors will get stricter about assignments, tests and projects as you continue into your Junior/Senior year. (I'm a MIS Senior)

EDIT: i just read the rest of the thread, and i can tell you straight out that i am NOT a programming person. I have to take two advanced computer classes for my degree, and the one i'm in (Data Com and Networking) we have to build a Java program to get email and stuff. I was shitting briques by the first project. (teensy-weensy compared to the final project)

I also loved programming in Borland C++, in DOS and having my programs do cool stuff. Now i don't.
 
Hm.. Commenting off of what Mark Larson recommended..

I never code on my computer. There is a Unix server which I SSH into and I code directly on that Unix machine. I fell in love with Bash, Vi, and GCC. All outstanding.

That way I never forget to bring my program anywhere and I can access it from any computer on campus.
 
buy an athlon 64 system and code some 64bit apps:D

hey someone has to start somewhere...
 
One thing you shouldn't get misled about - a P4 is about the worst thing for compiling as you can get. This is just facts, reiterated from various tech boards.

Compilers tend to be branch-happy, and the P4 is anything but (note how it does so well in streaming benchmarks without many branches). This has to do with its long pipeline - the branch penalty is pretty damn high even with the C's.

I'd say get an AthlonMP or Opteron machine for compiling - you'll love the benefits of dual processors and a short pipeline when compiling. AthlonMPs are dirt cheap right now and you just can't go wrong, even with a lowly pair of 2000MPs.

Intel's HT is good, but compiling is nothing like DVD encoding or MP3 encoding.

Prescott was rumoured to be better at compiling because of its better branch predictor, but the longer pipeline offsets that to some extent.
 
Originally posted by Mark Larson
One thing you shouldn't get misled about - a P4 is about the worst thing for compiling as you can get. This is just facts, reiterated from various tech boards.

Compilers tend to be branch-happy, and the P4 is anything but (note how it does so well in streaming benchmarks without many branches). This has to do with its long pipeline - the branch penalty is pretty damn high even with the C's.

I'd say get an AthlonMP or Opteron machine for compiling - you'll love the benefits of dual processors and a short pipeline when compiling. AthlonMPs are dirt cheap right now and you just can't go wrong, even with a lowly pair of 2000MPs.

Intel's HT is good, but compiling is nothing like DVD encoding or MP3 encoding.

Prescott was rumoured to be better at compiling because of its better branch predictor, but the longer pipeline offsets that to some extent.
Click to expand...
while everything u say is correct... I have a feeling the programs hes going to be compiling will do so in about 3-4 min on a PII.. :D
 
You must log in or register to reply here.
Back
Top