band-aids

The end result is band-aids on top of band-aids, rather than a proper solution to the problems.

It's just band-aids that keep people from taking real responsibility because they believe the Process will take care of things.

Edit: the article itself alludes to band-aids: our developer had improperly patched the glitch i.e.

Maybe some of the techniques it used could be applied to Africa, and not just band-aids that keep Africa hooked on western 'aid'.

But band-aids exist exactly because they contribute towards long-term improvement of a wound.

The right solution is of course the inconsistency itself, but practically, we patch it with band-aids.

But we as front-end developers just have to live with those band-aids; we don't get to reengineer the user's browser.

You're trying to fix a broken pipe with band-aids.

Yet we still needed to add some additional Band-Aids around the libraries provided to be able to support all cases we wanted seamlessly.

Just rip off the band-aids and move forward.

And even in big corps, 95% of all IT is usually plumbing and hectically applying band-aids for past issues that should not have been there in the first place.

People usually don't care about post-it brands or pen brands (or band-aids or toothpaste) because, in most cases, they are __functionally equivalent__, so you can decide on price or convenience.

But again, the script could easily say "He band-aids his hand in rhythm with the cymbals." If you want to read more about some actual decisions an editor goes through, I highly recomment In The Blink Of An Eye, written by sound and film editor Walter Murch.

Band-aids and mercuro-chrome - I'll never forget the smell of a new band-aid.