- node.js
- Installation paths: use one of these techniques to install node and npm without having to sudo.
- Node.js HOWTO: Install Node+NPM as user (not root) under Unix OSes
- Felix's Node.js Guide
- Creating a REST API using Node.js, Express, and MongoDB
- Node Cellar Sample Application with Backbone.js, Twitter Bootstrap, Node.js, Express, and MongoDB
- JavaScript Event Loop
- Node.js for PHP programmers
| //configurable variables | |
| boolean | |
| exportMode = true; //set to true when exporting, false when designing | |
| String | |
| folderPrefix = "b"; | |
| int | |
| fps = 24, | |
| outputScale = 2, //set to 2 or 4 when exporting, 1 when designing | |
| windowSize = 480 * outputScale, |
| // by Dave @ beesandbombs >:) | |
| int[][] result; | |
| float time; | |
| void setup() { | |
| setup_(); | |
| result = new int[width*height][3]; | |
| } |
Hello, visitors! If you want an updated version of this styleguide in repo form with tons of real-life examples… check out Trellisheets! https://github.com/trello/trellisheets
“I perfectly understand our CSS. I never have any issues with cascading rules. I never have to use !important or inline styles. Even though somebody else wrote this bit of CSS, I know exactly how it works and how to extend it. Fixes are easy! I have a hard time breaking our CSS. I know exactly where to put new CSS. We use all of our CSS and it’s pretty small overall. When I delete a template, I know the exact corresponding CSS file and I can delete it all at once. Nothing gets left behind.”
You often hear updog saying stuff like this. Who’s updog? Not much, who is up with you?
| man | |
| kvinna | |
| är | |
| pojke | |
| flicka | |
| jag | |
| en | |
| han | |
| hon | |
| ett |
Picking the right architecture = Picking the right battles + Managing trade-offs
- Clarify and agree on the scope of the system
- User cases (description of sequences of events that, taken together, lead to a system doing something useful)
- Who is going to use it?
- How are they going to use it?
| // I've only used this for focus management, I'm willing to bet you don't | |
| // actually want to do this unless it's focus management | |
| function useUpdateEffect(effect, deps) { | |
| let mounted = useRef(false) | |
| useEffect(() => { | |
| if (mounted.current) { | |
| return effect() | |
| } else { | |
| mounted.current = true |