I’ve always been curious as to what “normal” people think programming is like. The wildest theory I’ve heard is “typing ones and zeroes” (I’m a software engineer)
I’ve always been curious as to what “normal” people think programming is like. The wildest theory I’ve heard is “typing ones and zeroes” (I’m a software engineer)
You guys talk to computers in the language of computers. You are trying to get the computer to do something you want. However the computer doesn’t help you out, you have to tell it explicitly what to do down to the tinyist detail or it won’t work and you will be sad.
To the outside observer this looks like typing gibberish and copying in chunks of more gibberish. With occasional swearing.
How’d I do? (I know very little about programming and computers, I’ve worked manual labor for something like 20 years.)
That’s pretty much bang on.
You learn pretty fast that you’re an idiot and yes, you can write something, read it back many times, and still be wrong.
Hunting that missing semicolon in 500 lines of code qq
With that one, at least your parser should crap itself right around where the error is. You probably just need to search engine the error message, and find the page every other noob has to. Then it won’t take too long.
If your thing compiles but doesn’t work, then the real fun begins. You’re in the magical land of Turing completeness, where you hope the problem isn’t unsolvable in your case, because it definitely is in general.