#Can someone walk me through something?
1 messages · Page 1 of 1 (latest)
try using recursive decomposition on the problem and apply computational thinking to solve it 
Oh uh
I’ll try..
oh my god
that's the long way of saying use your brain
Ive been trying but everytime I think I’m finished the ui messes up
😭😭😭😭
break the problem down into smaller parts and deal with each one individually, don't try to do it as a whole / all at once
but pyro
what if i cant even solve the smaller part
then you're cooked, or at least not trying hard enough
what smaller parts did you end up with?
I managed to make it blink but
The problem is
It’s not covering the full screen
It’s leaving a little tiny spot in the top
screengui.IgnoreGuiInset -> true
yep that's breaking down the problem 👍
I’ll add it in the script and see what it shows now after I’m finished with my chocolate cake and pizza with lemon Italian ice sparkling water
instead of "oh it just doesnt look right", you specified exactly what small part of it wasn't working. well done.
Yeah that was the only problem
The timing was good
the better you get at doing that, the better you'll get at coding
and wait, that was the only problem from the start?
Yes
Lol
I should’ve explained it better
Sorry
Or showed a video
"theres a gap at the top of the screen" is much more conclusive and definitive than "i want to create effect i dont know how the tutorials dont work" wouldn't you agree?
Yes 😞
I’ll be more detailed next time I have a problem my peanut brain can’t figure out
you should get into the habit of explaining problems to a caveman who doesn't know anything about code
don't be more detailed or try to overthink it
just state exactly what you see, against what it is supposed to look like
like the more ooga booga caveman you are about it, the better
Ahh noted
like here it'd be "ooga booga BLINK UI NOT COVER WHOL SCREEN"
LOL
you know what i mean....
if it helps
this is actually a real debugging technique, it's called rubber duck debugging https://en.wikipedia.org/wiki/Rubber_duck_debugging
Rubber duck debugging (or rubberducking) is a debugging technique in software engineering, wherein a programmer explains their code, step by step, in natural language—either aloud or in writing—to reveal mistakes and misunderstandings.
The name is a reference to a story in the book The Pragmatic Programmer. It tells a story of a developer wh...
There’s a website for this?!
to describe this in other words, it's basically "state the obvious as much as you can"
that's why you might often see me asking stupid or obvious questions
Oh Dw I do it too
ya, if a question is obvious and you haven't asked it, ur doin it rong
Hey thanks for the advice
Programmers often discover solutions while explaining a problem to someone else, even to people with no programming knowledge. Describing the code, and comparing to what it actually does, exposes inconsistencies.
