It's not just for the sake of it. What if you decide to change your implementation later, and you get to that object a different way? If you've got an accessor method, then you just change it in one place and the rest of your code works.
Good programming isn't about making it always quicker to implement. Think about maintenance, flexibility, reuse etc.
Software engineering has changed over the years, for a reason. Someone just didn't invent this stuff cause they were being 'cute'.
Sure if your program consists of plotting some points and making them go up and down, you might not bother. But any sort of large application benefits from strong design and impementation methods.
Aaron
Good programming isn't about making it always quicker to implement. Think about maintenance, flexibility, reuse etc.
Software engineering has changed over the years, for a reason. Someone just didn't invent this stuff cause they were being 'cute'.
Sure if your program consists of plotting some points and making them go up and down, you might not bother. But any sort of large application benefits from strong design and impementation methods.
Aaron