Visual Programming: Cooking the Spaghetti - GOTO Conferences

More documents

Recommendations

Info

1. Domain specificity "The ability for the general public to understand a VPL is inversely proportional to the likelihood that it will actually do something useful." -me ● This is really no different from a well-made API ○ Abstracts away unnecessary granularity ● Unspecific: Scratch, AppInventor, etc. ● Specific: Lego Mindstorms
2. Hiding the "dirty stuff" ● All VPLs hide some of the generic dirty stuff ● Goes hand-in-hand with domain specificity ○ If not domain-specific, it's hard to identify the dirty stuff ● Examples of dirty stuff in automated trading ○ In-flight Orders ○ Fairness ○ "It just works"
Page 1 and 2: Visual Programming: Cooking the Spa
Page 3 and 4: Who I am ● Chief technology offic
Page 5 and 6: Low-latency trading & VPL Communica
Page 7 and 8: I got tired of these guys yelling a
Page 9 and 10: But modules weren't enough ● Bugs
Page 11 and 12: The "Deutsch Limit" “The problem
Page 13: The solution is threefold 1. Domain
Page 17 and 18: We want our users to eat fruit Kath
Page 19 and 20: stock=GOOG;volume=5433728;LTP=782.0
Page 21 and 22: Domain Specific
Page 39 and 40: Wrap-up* ● VPLs can work for a ve
Page 41 and 42: Appendix
Page 43: Flowcharts are evil ● Poor repres

Visual Programming: Cooking the Spaghetti - GOTO Conferences

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?