>. It said you don't have to avoid tables for certain small situations where it can save you a ton of time and a few headaches. I am not a front end developer,

>. It said you don't have to avoid tables for certain small situations where it can save you a ton of time and a few headaches. I am not a front end developer, but I agree to the philosophy to an extent in terms of generic software development. As software developers, our job is not to thrive for the perfect solution, but writing maintainable, code that we ship. I understand that many people (probably not HN users) take "real artists ship", as an excuse to put ugly unmanageable "hack", which I am not supporting either (infact I think I would be one of the last guys to compromise of code quality), but truth of the matter is, we live in an non-ideal-finite-time-full-of-deadline world, and as every thing has a cost-to-benefit ratio (short and long term). I think as software developers, its a part of out job to judge that cost-to-benefit ratio and if the cost starts to become much for the benefit offered, its time to rethink about software puritanism.