"fixing everybody else's code that comes across your desk because they didn't do it the way you would" that's the real world of design and collaborative enviro

"fixing everybody else's code that comes across your desk because they didn't do it the way you would" that's the real world of design and collaborative environments. Branding, code quality, standards they all start with setting a direction that makes sense in order to improve efficiency across multiple disciplines and experience levels. Hackey fixes have always been available. Instead of using h3 tags you can use b tags and scale them up to a particular font size. Even when something works, you have collaboration and reputation to operate by. Case in point: Somebody actually had to create an animation to explain what the hell is going on with this hack to people who already know html and css, whereas with a unicode character or SVG you wouldn't have to have meta instructions. You could say good code or technique often requires no explanation. that's what I'm trying to get it.