This is fucking dumb. People learning how to code don't know how to start. They don't know what to start writing or where to start on it. This is akin to telling a depressed person "just don't be sad".
If anyone genuinely feels this way and wants to get started in coding, I highly recommend doing one of the mooc.fi courses. Codecademy is fine as a taster/refresh but don't waste money on the premium when something like mooc is available for free.
Alright, smart guys. I know how to code.
How do I make these variables into a an app?
Honestly I've been trying to learn coding for a while, and there's a huge chasm between knowing a language and doing something with it that I can't go over. I want to make an app to create ttrpg character sheets... Alright how do I make my code into something with an UI? How do I turn it into an executable? How do I turn these lines into SOMETHING?
I'm not sure I get it. Is there a significance to him holding the mouse in front of him like that, instead of having it on the table like normal people? It seems to me that if you want to learn to code you should have your hands on the keyboard more.
Obligatory link to the wizard book, aka learn programming the proper way. Never mind the language this is about principles and fundamental concepts. Yes by the end of it you'll have written a compiler, that's the equivalent of a smith forging a hammer and tongs. Flank with HTDP if you need a bit hand-holding putting programs together, SICP is rather pinpoint-focussed on the concepts so doesn't contain much in terms of design. If you want a stand-alone implementation of the language (with the first link you can run all the code boxes in the browser, fancy newfangled stuff I approve of) racket is the way to go, just add #lang sicp in front of your files and you'll have the exact dialect the wizard book uses.
The wizard book has been the standard recommendation for like 20 years now, the only reason other tutorials exist is because newbs insist on "how to move cube in unity without programming" type of hand-holding. It's not actually helping them, on the contrary I see much learned helplessness in the young'uns.
From those basics you can dive into whatever concrete you need for whatever you want to do, you'll have the necessary background to not be lost at sea. To further build that background knowledge it's a good idea to have acquaintance with a broad selection of standard data structures, algorithms, and their properties. No need to go in real depth but you should have an at least intuitive understanding of why they have the properties they have, like, don't be surprised if your game stutters if you're using hashmaps. O(1) and amortised O(1) are not the same thing.
Last, but not least, never write your own datetime or unicode handling code.