OOP uses the same coding techniques than Sequential Programming. (SP)
You have to approach it with another mind, but there is no difference in coding, just A DIFFERENCE IN LOGICAL THINKING.
SP was the initial programming technique: The program starts AT THE START (seems silly to say that, but the program has one entry point only.) The processor then read an instruction and performs it. Then it reads THE NEXT and executes it. Then it read the next and executes it. and so on. That is sequencial programming.
(This sequence could be interrupted by an "interrupt", to stop the current execution, jump to another routine - The "Interrupt" routine - executes it, then return to the main program where it left it.)
In our modern times, the processors are able to do "multi-tasking": doing more than one thing at the same time (not really true, but it looks like it).
So, an OOP contains a lot of small INDEPENDANT "functions". There is still a "start point", when you load the program.
After that, the processor stays in a "loop", waiting for "EVENTS". Events can be anything: a key-press, a mouse movement, an incomming message, a hardware interrupt: anything, really!
The "event" triggers the running of a routine (the "object"), and the routines starts to run.
DURING that run, another event may occur: it triggers the running of another routine, and now, we "appear" to have two routines running at the same time. (again, not exactly true: the processor still executing ONE instruction at a time, but it does one of the first routine, then one of the second and so on, so it appears to be simultaneous).
So, in OOP, you don't think it terms of "sequence": you think that ALL your routines CAN be running at once!
THAT is the difficult bit, because one routine may change a "global value" WHILE the other routine expects that value to be constant!
Each of your routines is a different person, and all of them want to speak at the same time! (remind you some heated pub discussions?)
Good luck