New programmers are excited that their code works the first time, but experienced programmers know that something is definitely wrong if it actually did work the first time.
As an experienced programmer, something is wrong if the jump function works. Maybe once the character hits the ground, they get flung back up.
As a 9 year old, who was actually interested in Java at that time because of using an app-making tool, an error log said "expected int, got float", and I thought int meant Intent so I brute forced an integer to be an Android object, and I got mad when the bug got worse.
As an experienced programmer, I unfortunately feel this pain...
I remember this one night I had a dream that I was programming something for my Graphing Calculator, probably a game or something, and then once I woke up I sprung off of my bed onto my computer to program on my Ti-84 Plus CE Graphing Calculator.
Funny thing? The program I had programmed from my dream actually worked.
A programmer's actual worst nightmare: seeing the same platformer over and over again but with different textures and seeing it has thousands of views.
I've made around 3 games for the TI-84 Plus CE. They run pretty slowly because they are all programmed in TiBASIC and they also take a long time to refresh every frame. But anyways...
No, I can't program in Assembly (unfortunately)
But let's be honest - no one is programming in Assembly anymore, we've got compilers and crap to inject data into x86 computer chips or whatnot.