@ethaneisenhard@ASpittel@kentcdodds@ow@lesliecdubs@1Chenzo @EmmaWedekind I usually review the diff on the code review, but then look at the actual larger component/page/context to look at how the whole is making sense. Super important step IMO.
@HugoGiraudel So true. I do a lot of interviewing and rarely do front end candidates understand anything about HTML, accessibility, SEO, or document outlines. Even things like ‘can you put an H1 tag in a span tag?’, ‘can you explain the differences between article, header, footer?’
I’m beginning a code style guide for front end development for my team. The purpose is to reference in code reviews. Any advise or resources? Google search is showing me all dated things.
@sarah_edo Email is solvable only if all email providers decide to force their platforms to be evergreen. Otherwise it is the last holdout of success = knowing hacks. And the ones that don’t disappear very fast. Too many companies rely on it for communicating to their customers.
@SaraSoueidan How to deal with not yet fully adopted css features, like width: fit-content even with prefixes doesn’t work in some places. So don’t use it? Or progressive enhancement or feature detection? I avoid if caniuse shows me red on supported browsers.
@EmmaWedekind What is the worst thing that has happened to an application/website that you were in some way responsible for? Then how did you deal with it.
@seldo@getify An iOS engineer I work with says JavaScript isn’t a real programming language like Objective-C or Swift. I think that way of thinking is dangerous for his future.
@sarah_edo My first impression in using with a production level application was that it was a pain, BUT very quickly saw that it caught a few bugs and now in the flow of it, love it.