The technical community seems to have these virulent quality assumption: Everything test driven, inside out, full stack, behaviour drive. This is great an

The technical community seems to have these virulent quality assumption: Everything test driven, inside out, full stack, behaviour drive. This is great and a must if you have a clear product requirement and/or a clear vision. I think it might be an infliction particularly common among those of us who started our own thing after (too many?) years of "Enterprise" (and other larger-scale) programming. After being burned by having to support/maintain/develop upon someone else's huge, less-than-optimally-thought-out code base you grow afraid of quick hacks, even tho those are sometimes exactly you need.