| /* | |
| This is an idea for mocking HTML data that lets you test whether your layout breaks on any screen size for any | |
| unexpected dynamic data. | |
| This script scans the document for class names with a specific pattern and periodically randomizes the content | |
| of those elements while meeting the constraints specified in the class name. This can let you quickly test | |
| whether your layout breaks for any dynamic content that you may not have thought about. This should ideally be used | |
| with a responsive design testing tool such as DevTools or Sizzy/Bizzy. |
To bring some sanity to your twitter feed, add these words to your muted list here: https://twitter.com/settings/muted_keywords
Needless to say, this is highly subjective and may not be applicable to how you want to use Twitter. Many of these conversations are important, but I have those on other platforms, not Twitter.
suggest_recycled_tweet_inline
suggest_activity_tweet
First of all you need to decide who will be your target consumers based on the following:
They have the same environment(webpack config, babel config) setup as you where you built your design system(this is mostly possible if you use monorepos/same configs where all the teams share the same environment).
They don't have the same environment which is the case when you work in bigger teams and you want to distribute your design system as any other npm package which is already built and can be used directly.
If your use case falls under case no. 1 then you can just compile the source babel src -d build and leave the bundling to the consumer projects tools(webpack/rollup)
2019 update: this essay has been updated on my personal site, together with a followup on how to get started
2020 update: I'm now writing a book with updated versions of all these essays and 35 other chapters!!!!
If there's a golden rule, it's this one, so I put it first. All the other rules are more or less elaborations of this rule #1.
You already know that you will never be done learning. But most people "learn in private", and lurk. They consume content without creating any themselves. Again, that's fine, but we're here to talk about being in the top quintile. What you do here is to have a habit of creating learning exhaust. Write blogs and tutorials and cheatsheets. Speak at meetups and conferences. Ask and answer things on Stackoverflow or Reddit. (Avoid the walled gardens like Slack and Discourse, they're not public). Make Youtube videos
This content moved here: https://exploringjs.com/impatient-js/ch_arrays.html#quickref-arrays
Download the following repositories and run yarn install in each:
| Method | Side effects1 | State updates2 | Example uses |
|---|---|---|---|
| Mounting | |||
componentWillMount |
✓ | Constructor equivalent for createClass |
|
render |
Create and return element(s) | ||
componentDidMount |
✓ | ✓ | DOM manipulations, network requests, etc. |
| Updating | |||
componentWillReceiveProps |
✓ | Update state based on changed props |
