3 ms·

I'm not going to Google it, I don't know what you're talking about. I assume it's some 'thing' that's impossible/hard to solve. I'm sure someone will solve it i

I'm not going to Google it, I don't know what you're talking about. I assume it's some 'thing' that's impossible/hard to solve. I'm sure someone will solve it if it's possible. It won't be me.

coldtea 12y ago
Hmm, if the claim of being able to solve everything by yourself (just "given time") wasn't dubious enough in itself, not knowing the "halting problem" (something very well established, at the very core of computer science, quite famous even as a trivia, and with several implications), would surely cast some doubts on it... You might be perfectly able to solve most of the regular problems programmers encounter in everyday IT (e.g CRUD apps, a fault tolerant service, etc), but without CS fundamentals including detailed domain knowledge of several area solving a lot of problems (much less "most of them") is nigh impossible. A lot of problems (advanced DSP, GUI library design, advanced compiler/GC design, speech recognition, database engine, etc) require large teams and specialists to do properly. Except if by "enough time" you mean "enough time to read the literature, become an expert, and devote many lifetimes worth of man-months to each project". In which case, duh, we're talking about a god-like premise anyway...
- hitchhiker999 12y ago
  Well I've been programming since I was 6 years old, and i'm 38 now. I am what I am, I have yet to encounter any issue I couldn't solve. I don't deal with those sort of things though, so no idea if I could or not. When I started there wasn't CS readily available, and I was a child - so I don't have your background. It would have saved me a lot of time if I did. I guess I'm from a different type of crew than you - we probably work very differently -> To each his/her own. Obviously my original statement wasn't to be taken so literally, it was meant to be glib and careless. I didn't make that clear I guess. My apologies. Edit: Out of respect I looked it up - I've thought about that before, didn't know it had a name. It's impossible to determine (quite obviously - though you could establish a rough probability). I will make an effort to remember the name for next time.

I'm not going to Google it, I don't know what you're talking about. I assume it's some 'thing' that's impossible/hard to solve. I'm sure someone will solve it if it's possible. It won't be me.

coldtea 12y ago

Hmm, if the claim of being able to solve everything by yourself (just "given time") wasn't dubious enough in itself, not knowing the "halting problem" (something very well established, at the very core of computer science, quite famous even as a trivia, and with several implications), would surely cast some doubts on it... You might be perfectly able to solve most of the regular problems programmers encounter in everyday IT (e.g CRUD apps, a fault tolerant service, etc), but without CS fundamentals including detailed domain knowledge of several area solving a lot of problems (much less "most of them") is nigh impossible. A lot of problems (advanced DSP, GUI library design, advanced compiler/GC design, speech recognition, database engine, etc) require large teams and specialists to do properly. Except if by "enough time" you mean "enough time to read the literature, become an expert, and devote many lifetimes worth of man-months to each project". In which case, duh, we're talking about a god-like premise anyway...

hitchhiker999 12y ago
Well I've been programming since I was 6 years old, and i'm 38 now. I am what I am, I have yet to encounter any issue I couldn't solve. I don't deal with those sort of things though, so no idea if I could or not. When I started there wasn't CS readily available, and I was a child - so I don't have your background. It would have saved me a lot of time if I did. I guess I'm from a different type of crew than you - we probably work very differently -> To each his/her own. Obviously my original statement wasn't to be taken so literally, it was meant to be glib and careless. I didn't make that clear I guess. My apologies. Edit: Out of respect I looked it up - I've thought about that before, didn't know it had a name. It's impossible to determine (quite obviously - though you could establish a rough probability). I will make an effort to remember the name for next time.