Image quality may be about striking the balance between speed and quality, but there’s more to it than meets the eye. What if, despite having methods to develop better and better image experiences for the web, the user disagrees? In a quest to find answers, Jeremy Wagner takes us through an image quality study that he designs, develops, and iterates on with user feedback. Asking “Why?” is no easy undertaking in research. His lossy is your gain.
“The modern developer can’t hide behind a keyboard and expect the rest of the team to handle all of the important decisions that define our workflow,” writes front-end developer Ronald Méndez. Drawing on his decade of experience, he shares advice for going beyond code, sharing ideas, and fighting for a seat at the table.
Always writing the clearest possible code is what helps separate the great developers from the merely good. It cuts confusion, reduces headaches for current and future developers, and saves everybody time in the long run. And though not always as easy as it sounds, with good forward planning, a logical approach to code structure, and adherence to a few guiding principles, coding with greater clarity is something all developers can achieve.
A Progressive Web App (PWA) is a website with special powers. Despite what you might have heard, most websites—and, more importantly, their readers—can benefit from becoming PWAs. And it’s so easy! New A List Apart editor-in-chief Aaron Gustafson explains.
Maintenance is an ever-present aspect of web development, but there simply isn’t much data about what we do industry-wide. To uncover what developers consider best practices and great resources, we’re all taking the (very short!) Great Web Maintainability Survey from Jens Oliver Meiert.
If you only interact with users when they need support or have a feature request, you’re only interacting with the minority of your customers. The ones who don’t reach out to you may be creating their own workarounds to a problem you’d love to hear about, or they may have a use case that would lead to a brilliant feature. Are you guilty of the same developer shyness? Do you build things to enhance a tool or service for your own use, and assume the developer is too busy to want to hear about it? Don’t wait until there’s a need for support: ask your happy customers what they do with your product, and tell developers how you’re using their product.