Hacker News new | ask | show | jobs
by thfuran 264 days ago
The alternative to using private methods or reflectively mucking about with library/platform internals isn't always "do the same thing but with only public API"; it's sometimes "you can't possibly fix the bug or implement the feature that you want to". It sure does increase maintenance burden though.
1 comments

> it's sometimes "you can't possibly fix the bug or implement the feature that you want to"

Yes. It is, and that is what any responsible person should choose.

So you'd tell customers "No, I'm not fixing that bug because doing so would offend my aesthetic sensibilities. Yes, I know you have a support contract, but I simply refuse to address your problem even though I could"? Or maybe you'd phrase it a little differently in public.
Yes, I have told customers exactly that when there was no supported way to achieve what they wanted. I'm not putting my name on that.
“Poor decisions on your part do not constitute an emergency on mine.”
"Poor decisions on a third party's part do constitute an emergency on mine."