Professionally: Waterfall release cycle kills innovation, and whoever advocates it should be fired on the spot. MVP releases and small, incremental changes and improvements are the way to go.
Personally: Don’t use CSS if tables do what you need. Don’t use Javascript for static Web pages. Don’t overcomplicate things when building Web sites.
THE AMOUNT OF TIMES I SEE PEOPLE USE A TABLE WHEN BULLET POINTS WOULD WORK IS TOO DAMN HIGH. Tables SUCK is you’re putting long paragraphs randomly in specific places and not others.
As a web dev, please don’t. Use a table if you have data that should be (re)presented. Don’t use tables for layout. Please use semantic HTML elements, for the love of accessibility.
Professionally: Waterfall release cycle kills innovation, and whoever advocates it should be fired on the spot. MVP releases and small, incremental changes and improvements are the way to go.
Personally: Don’t use CSS if tables do what you need. Don’t use Javascript for static Web pages. Don’t overcomplicate things when building Web sites.
Use tables for presenting tabular data, not for layout of non-tabular data.
If you’d put it in a relational db or spreadsheet, then tables is fine.
THE AMOUNT OF TIMES I SEE PEOPLE USE A TABLE WHEN BULLET POINTS WOULD WORK IS TOO DAMN HIGH. Tables SUCK is you’re putting long paragraphs randomly in specific places and not others.
As a web dev, please don’t. Use a table if you have data that should be (re)presented. Don’t use tables for layout. Please use semantic HTML elements, for the love of accessibility.