Broadly speaking, common CSS best practices cover readability, efficiency and modularity. Adopting them purports to make long-running projects more manageable. But do any of them really help, and how many of them actually improve the product that falls into people's hands? Is it possible that CSS best practice can perpetuate or even beget bad design practice?
Hand-crafted code has been the hallmark of quality front-end development since front-end was even a thing. As websites become more functional, though, and loaded through myriad viewports, is typing our intentions the best use of our time? If we make markup easier, what do we have to fear? Easier markup means more people can build richer content on the web. Also, by relying on tools, rather than our fingers, developers can free up time to focus on the features that really need brain power: accessibility, semantics, optimization, saner class structures, and whatever comes next. We just first need to define what is “good enough” output, and rethink how we approach our tools to make them actually useful.
WebSockets, Server Sent Events or should I maybe just use Short Polling?
Choosing the right tool for the job is always harder then it looks and often requires deep understanding of the various techniques and hacks. Join this journey and learn about the beauty and horrors of building the real-time web.