Scanners are there to take input from your keyboard. Kinda like Cin >> for C++
Names are indeed arbitrary but the point of contestion I think right now is why did I name it 'playerName' instead of something like 'input' or whatever to make it less likely to confuse me or a maintenance programmer down the road.
Basically instead of: Scanner playerName = new Scanner(System.in);
I should have made: Scanner inputDevice = new Scanner(system.in); or Scanner genericInput *rest of code*.
I'm mention this because in previous programs he made a separate scanner for each input statement he wanted.
He named each of the scanners after the thing he was going to input. He's still using that naming convention, so I was skeptical as to whether he actually gets it.
I hate my reputation too. I hate my inability to recall important tidbits after a week of not working on something over a weekend. Whether I'm getting better I can't say but to give you some insight about the job I posted..I had to leave.
Not because they didn't like me but because I was a student assistant and I had to also go to school for 6 credits per semester. FAFSA screwed me and money is tight so I wasn't able to sign up. Which forced me to drop that job.
Beleive it or not I was actually learning alot but I was still wet behind the ears. Printing issues? I got that in the bag and a metal box. stage set up? Check. Spanish speaking proffesors having issues with word? I know how to explain it for dum dums like myself.
New concepts? Not so much. But if I got better in that tech job I can do better in programming with time. Also the name of my department was network and media. Meaning I had to do media which was setting up for not so tech stuff and become a stagehand/roadie for whatever the event was. No more on this due to privacy and what not.
I actually felt like I left on a good note though so that's good. Not that it matters because yeah I'm a piece of shit of a worker and i'm 22 with alot of pre-reqs that I still have to take to transfer to a uni for my bachelors in C.science.
Now that that's out of the way reelya..
I still do like naming conventions for naming things on what i'm going to use them for. Yes, it's inefficient and I know that but I don't know how to name it without it being so damn generic that I don't know WHAT to use it for. Maybe i'm overthinking things and I should just generically named things like 'inputDevice' and just trace the code for hours in the future when my programs become bigger and more complex.
Kay, so
how do I make that code box bigger for people to read? An again, I AM NOT GOING TO WORK ON THIS PROJECT ANY LONGER! I just want some
advice on how I should build bigger things in the future. I don't have a system for organizing projects with classes or larger things. I don't know
how to make things scalelable (the ability to continuously build on code without having to double back and rewrite your original code).