What happens when your code starts running? A process is allocated from memory, a class instantiates, and your program is..."born". It runs its code -- and maybe that code responds to inputs, does calculations....has....feelings....falls in love...or whatever :) Maybe it has the ability to interact with other processes and send messages to these other processes. Maybe it runs independently.
It's blissfully ignorant of the system within which it runs: The BIOS, the hardware, etc. Or maybe not! Maybe it even has the ability to probe its environment, learn about it, report on it (...run experiments on it), etc.
From your program's perspective, it is unique, it has perspective, it has experience.
And at some point, the program terminates. What happens? The code stops running. The memory is returned to the pool. Maybe new programs are launched (with no knowledge of previously-launched programs, unless they've left some sort of permanent record in a database or a file, etc.)
What is the "experience" of the program after it terminates (or before it was allocated from memory). Kind of an absurd question when you frame it that way, right? Programs don't have an experience when they're not executing! They simply don't exist at that abstraction level. But that certainly doesn't mean the computer is gone, or that other programs - that use the exact same memory - won't have similarly rich (or poor) experiences in the environment.
I know this a bit contrived...but maybe it's not? I find this logical and, frankly, it makes sense. We're all allocations from a global memory pool that continues to be recycled so long as the computer is running. And to answer OPs primary question, then: Yes, pre-birth is exactly the same as post-life, but both aren't so bad :)