Someone told me that easiest way to 'destroy' a programmer is to prevent them from programming for a month or so. Is that correct?
Printable View
Someone told me that easiest way to 'destroy' a programmer is to prevent them from programming for a month or so. Is that correct?
I moved your post to the off-topic forum, since it's not really a technical question- it's still fun though!
But I disagree- sometimes it's best to get away from something (whether that's programming, playing the guitar, reading a textbook, whatever) for a while and come back to it. Practice makes perfect, but overdoing it can leave you sick of the thing you're trying to perfect!
Java programmers are never destroyed: they're collected with the garbage.
lol.Quote:
Originally Posted by Sean4u
I could do with a month long holiday.. I may have to take 4 weeks off as an experiment. I will let you know if I survive!!
No, that will just give them enough time to do it in their head before they get to the tedious job of fixing every mistake. Maybe the other way around? Give them a big project and little time.
Programmers often do that to themselves, which I think is one of the biggest killers of hobby programmers who could have gone on to be professional had they kept at it. People think "oh man this project would be awesome", not realizing that the project is non-trivial or made up of several smaller projects. Then they become discouraged when they don't have their goals accomplished in a couple weeks and give up on it altogether. That's why I always stress that people should work on much smaller projects until they have a more accurate idea of what a big project will take.Quote:
Originally Posted by Melawe
I almost did that to my self ones. :P I wanted to make a database, users would also be able to add info to it too. I plan on getting back to it soon.Quote:
Originally Posted by KevinWorkman