- Introduction to Risk Management and Insurance Idag Mark S. Dorfman 150:-
- Principles of Risk Management and Insurance Idag George E. Rejda 150:-
- Macroeconomics - understanding the wealth of nations Idag David Miles , Andrew Scott 150:-
- Principles of Corporate Finance Idag Richard A. Brealey , Stewart C. Myers 150:-
- Study Guide for Managerial Economics and Business Strategy Idag Michael R. Baye 150:-
- Managerial Economics and Business Strategy Idag Michael R. Baye 150:-
- Applied International Trade Analysis Idag Harry P. Bowen , Abraham Hollander 150:-
- Introduction to economic growth Idag Charles I. Jones 150:-
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If you have | |
/cars | |
/cars/{carId} | |
/individuals | |
/individuals/{individualId} | |
and then | |
/individuals/andrei | |
needs to link to my cars, which would be /cars?individual=andrei | |
(( side-tracking here: maybe http://api.garage.com/cars?individual=http://api.garage.com/individuals/andrei seems better since the URIs are the IDs ? wdyt? )) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash -e | |
# Usage # copy from browser "JIRA-205\nTicket title" | |
# $ jira2branch # echoes jira-205-ticket-title | |
# $ JIRA2BRANCH_TEAM=team jira2branch # echoes jira-205-team-ticket-title | |
# $ jira2branch team2 # override mode | |
# echoes jira-205-team2-ticket-title ignoring $JIRA2BRANCH_TEAM | |
OS=`uname` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
class A | |
@temp: 'A' | |
constructor: () -> | |
console.log A.temp | |
class B extends A | |
@temp: 'B' | |
constructor: () -> | |
super | |
console.log B.temp |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
100 Continue | |
101 Switching Protocols | |
102 Processing | |
200 OK | |
201 Created | |
202 Accepted | |
203 Non-Authoritative Information | |
204 No Content |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
m = | |
x: 1 | |
getX: -> @x | |
getX = m.getX | |
console.log m.getX(), getX() # 1 undefined |
- rawgithub.com - Content-Type aware proxy
- gist.io - gist publisher
- GistDeck - gist slideshow
- prose.io - web-based interface for managing text-based content
- documentup.com - README publisher
- BundesGit - tracking down law changes in Germany
- Prose - literate programming (slightly not related)
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
re:replace(Str, "[\\-\\[\\]\\/\\{\\}\\(\\)\\*\\+\\?\\.\\,\\\\\^\\$\\|\\#\\s\\&]", "\\\\&", [global]). |
rambling re: tweet
By no means do I want to sound assertive. I lack a lot of knowledge in the area, so please slap me and set me straight, teach me a thing or two. The only thing that I standby is that it is stupid to explain syntax, to re-invent syntax, to argue about syntax, to have a liberal syntax, etc. Whatever does not matter (i.e. produce added value) should be standardized IMO. Eliminate mundane topics from the discussion to elevate the quality level. There are better things to do. That said readability, performance, simplicity, portability, ... still matter. A lot, I'd say.
- syntax - something that a parser can recognize e.g. PEG; the string 'function'
- semantics - something that a parser can associate syntax to. e.g. AST/parse tree; the fact that the string 'function' is associated with the concept of a function
- higher level stuff - paradigms (OOP, FP, LP, etc), models/concepts (monads, clas
OlderNewer