When the question about the difference between self and static came up, I knew I had to get this right, but honestly, at that point, I started to wonder if they were testing my ability to recite PHP theory or actually solve problems. I explained that self refers to the current class itself, and static refers to the class in the inheritance chain — essentially, static is used when dealing with late static binding. But then, I felt like my answer wasn’t enough. They wanted more — they kept pushing. I could tell they were expecting an in-depth, textbook-style explanation of everything I knew about late static binding, inheritance, and the specifics of when to use self versus static in a real-world context. In reality, I use these concepts when the code calls for them, but at that point, I felt like I was in an exam room instead of a conversation about real programming challenges. It felt like no matter what I said, I wasn’t going to win this one. It became clear to me that this interview wasn’t about solving problems, but about seeing if I could memorize and regurgitate theoretical knowledge, which, frankly, has little to do with the day-to-day of real-world development.