A git choose-your-own-adventure!
This document is an attempt to be a fairly comprehensive guide to recovering from what you did not mean to do when using git. It isn't that git is so complicated that you need a large document to take care or your particular problem, it is more that the set of things that you might have done is so large that different techniques are needed depending on exactly what you have done and what you want to have happen.
| #!/usr/bin/env sh | |
| ## | |
| # This is script with usefull tips taken from: | |
| # https://github.com/mathiasbynens/dotfiles/blob/master/.osx | |
| # | |
| # install it: | |
| # curl -sL https://raw.github.com/gist/2287773/hack.sh | sh | |
| # |
| // Ernest Hemingway | |
| function fibonacci(size) { | |
| var first = 0, second = 1, next, count = 2, result = [first, second]; | |
| if(size < 2) | |
| return "the request was made but it was not good" | |
| while(count++ < size) { |
| { | |
| "auto_indent": true, | |
| "auto_match_enabled": true, | |
| "caret_style": "smooth", | |
| "close_windows_when_empty": true, | |
| "color_scheme": "Packages/Theme - Aqua/Color Schemes/Tomorrow Night Aqua.tmTheme", | |
| "detect_indentation": true, | |
| "dictionary": "Packages/Language - English/en_US.dic", | |
| "draw_centered": false, | |
| "draw_indent_guides": true, |
Ideas are cheap. Make a prototype, sketch a CLI session, draw a wireframe. Discussions around concrete examples, not handy-waving abstractions. Don't say you did something, provide a URL that proves it.
Nothing is real until it's being used by a real user. This doesn't mean you make a prototype in the morning and blog about it in the evening. It means you find one person you believe your product will help and try to get them to use it.
I hereby claim:
To claim this, I am signing this object:
| <!DOCTYPE html> | |
| <meta charset="utf-8"> | |
| <style> | |
| .chart rect { | |
| fill: steelblue; | |
| } | |
| .chart text { | |
| fill: white; | |
| font: 10px sans-serif; |
Brief notes on Meteor for CS 294-101. Many of the key architectural ideas in Meteor are described at https://www.meteor.com/projects.
BSD as example of great system design. Application primitives: processes run by a scheduler, sockets, sys calls, virtual memory, mbufs. What makes something a platform. Unix vs Multics.
History of application architectures. Mainframes (e.g. IBM 360 / 3270), client-server (e.g. Win32), web (e.g. LAMP), cloud-client. Oscillation of where the software runs. Thin vs thick clients, data vs presentation on the wire. Changes driven by massive forces (cheap CPUs, ubiquitous internet, mobile). New architecture for each era.
What it takes to make modern UI/UX. Mobile. Live updating. Collaboration. No refresh button. All drive the need for “realtime” or “reactive” system. Very different from HTTP era.
Four questions: 1 — how do we move data around; 2 — where does it come from; 3 — where do we put it; 4 — how do we use it?
