What are the potential pitfalls of naming conventions for parameters and properties in PHP object-oriented programming?

One potential pitfall of naming conventions for parameters and properties in PHP object-oriented programming is inconsistency, which can lead to confusion and errors in the code. To solve this issue, it's important to establish a clear and consistent naming convention for parameters and properties to ensure readability and maintainability of the code.

class Example {
    private $someProperty;

    public function setSomeProperty($value) {
        $this->someProperty = $value;
    }

    public function getSomeProperty() {
        return $this->someProperty;
    }
}