New type of negative self-talk unlocked: calling it "vibe coding" when I change some lines of code and then assemble and run the program again to see if that fixed the problem

Instead of stepping through it until I consciously understand where and how exactly I broke it

That's deserved TBH

But also
I'm lazy

And that's why I will never be a programmer, I guess

@vaporeon_ my advisor in undergrad would call that "code bashing"

also sorry to break it to you, but you are not a loser