This is all the CSS needed to render almost the entire app from mobile to desktop widths, in both light and night themes. The "utility CSS" is generated by a framework and not something engineers have to be concerned with when writing components.
Hey. I work at Twitter. I think that at certain companies the "front-end" role is not as specialized as assumed, and you tend to interview for a specific team that has an opening, rather than for a generic position among a hoard of similar developers.
Having said that, I'm surprised there was only one CSS question, and the suggestion to combine questions with front-end specific knowledge might be a good way to ease into the interview.
FYI, the keyboard shortcuts on http://littleoutliner.com/ seem to prevent me from using cmd+opt+I or cmd+opt+U when the window has focus. cmd+opt+J works though.
The analogies and conclusions are based on false assumptions about the driving forces and consequences of the "machine revolution". You can expect fewer jobs and the accumulation of more wealth concentrated in the hands of fewer people as a result of increased automation and the creation of more efficient "digital production lines".
Hi, I'm part of the team working on HTML5 Boilerplate.
As this featured project is, in some way, defining itself relative to what it believes HTML5 Boilerplate is and should be, I'm going to chime in with some thoughts.
If someone wants to create a new project after their concerns have not been shared by others maintaining a large, existing, community project (e.g., how Lo-Dash came to be) then that's fair enough. But I'm always disappointing to see people do so before raising their concerns and making their arguments. It would avoid the repetition of errors and discussions that have been addressed previously. We could also work together to adapt HTML5 Boilerplate if there is a good case to do so.
Once-upon-a-time, I didn't appreciate the work and community knowledge that went into HTML5 Boilerplate. However, after I started to open issues against the repo and contribute to the project, I realised that it has always been very open to contributions and changes of direction. I had significantly underestimated how much thought and combined knowledge was going into the project, and how much it was constantly evolving.
It's hard to design a useful starting template that's clear and friendly enough for newcomers, documented enough for explorers, and svelte enough for experienced developers. We're always trying to figure out the best way to present the value of the project while not scaring away too many people. Hopefully, we're doing a decent job of balancing those concerns and making people feel welcome in the discussions.
I hope that developers will continue to work with -- and look to join -- the people developing HTML5 Boilerplate at any given time. If you think something is missing or should be removed, make the case for it. We listen and learn; we're constantly evolving the project.
I haven't had the experience that HTML is harder to maintain if you use classes more liberally. What this approaches forces you to do is: write or edit CSS every time you want a new combination of existing traits...which isn't ideal either.
The post also suggests that certain class names are "unsemantic", when they obviously aren't. They just have different meaning to the sorts of class names the author is advocating.
I don't see plugins.js and main.js loading twice. And that CSS warning can only come from other tabs you had open as we don't include any `-o-` prefixed code in the CSS.
This is a hypothesis. IIRC, there is considerable variation in pigmentation in other parts of the world too. There isn't a direct mapping because other factors, like sexual selection (something not mentioned in the article), affect the phenotype of populations.
I've been wondering if Facebook will do general object and/or product detection in photos to help them match highly targeted adverts to the content (and location, season, etc.) of a photo.
Unfortunately, at the time when Ian didn't seem to care about the issue of responsive images, I asked him about the possibility of using the existing `<img>` element and he said it was pointless to try and modify existing image parsing. Forget it.
Now, he decides that actually this is the way to go. Frustrating.
For reference, in the email linked above, Ian Hickson said:
> So why not just give the UA the characteristics and a template to use to build the file names itself? That way we still give the UA all the same information, but it is much less verbose and still solves all the same use cases. Thus:
