6 ms·
If you aren't patching something, don't use monkey patching. It's a band-aid fix: eventually your code gets better and you get rid of it. And code that modifie
by rads 17y ago
If you aren't patching something, don't use monkey patching. It's a band-aid fix: eventually your code gets better and you get rid of it.
And code that modifies core classes, like your Array#pack example, is almost always bad code. It doesn't matter if you're working alone or with 100 people.
- cookiecaper 17y agoI worked with this dude who would make changes to the CakePHP API without telling anyone and then I'd spend like a day trying to figure out why the documentation didn't match up. I tried to get him to at least make a prominent declaration and documentation every time he made a change that broke the API, but he didn't listen to me. Shortly thereafter, they terminated my contract because my work was not "up to their standards". :C