Search results

From APIDesign

You searched for Domain/OS

Jump to: navigation, search

For more information about searching APIDesign, see Help.

Showing below 19 results starting with #1.


View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)

Page title matches

  1. Domain Specific Language (12,164 bytes)
    1: [[wikipedia::Domain Specific Language|Domain Specific Language]]s will be topic of [[User:Rich...
    5: ...ing [[JavaOne2010]]. Here are the slides: [[Image:Domain-library-shootout.pdf]].
    7: ===What is a [[wikipedia::Domain Specific Language|DSL]]?===
    9: ...r a particular solution technique. --[[wikipedia::Domain Specific Language|wikipedia]]
    35: ====When you're targeting domain experts, not java programmers====
  2. Domain Expert (2,206 bytes)
    1: ...volution]] will very likely suffer (unless such [[Domain Expert]] reads [[TheAPIBook]] first).
    3: ...without appropriate [[wikipedia:Domain knowledge|domain knowledge]]?
    5: ...about [[Truffle]], but certainly [[I]] am not a [[Domain Expert]], yet I am supposed to design something a...
    11: ...can be good [[API]] designer without being real [[Domain Expert]]. Soon we'll find out if [[API]] Design c...
    13: ... to [[design API as a service]] without being a [[Domain Expert]].

Page text matches

  1. OlderBlogPosts (111,273 bytes)
    519: ...ks, but it may help you to [[excel]] in designing domain specific languages. Either external or embedded (...
    1063: ==== Renewing [[TheAPIBook]]'s domain ====
    1065: ...naged to prolong the [[TheAPIBook|apidesign.org]] domain for next three years. I can see there are some fo...
  2. Blogs:JaroslavTulach:Theory (22,864 bytes)
    90: ... I can design [[Truffle]] [[API]] without being [[Domain Expert]] in the area of partial evaluation. Time ...
  3. Blogs:PetrHejl:BeautyMatters (3,396 bytes)
    9: ...d maintainable by others (growing popularity of [[Domain Specific Language]]s confirms this). Otherwise an...
  4. Domain Specific Language (12,164 bytes)
    1: [[wikipedia::Domain Specific Language|Domain Specific Language]]s will be topic of [[User:Rich...
    5: ...ing [[JavaOne2010]]. Here are the slides: [[Image:Domain-library-shootout.pdf]].
    7: ===What is a [[wikipedia::Domain Specific Language|DSL]]?===
    9: ...r a particular solution technique. --[[wikipedia::Domain Specific Language|wikipedia]]
    35: ====When you're targeting domain experts, not java programmers====
  5. Module system (1,378 bytes)
    3: ...en have a look at [[Maven]]. In case your primary domain is packaging, then you are probably seeking for [...
  6. DSL (38 bytes)
    1: #REDIRECT [[Domain Specific Language]]
  7. JavaOne2010 (2,311 bytes)
    43: == [[DSL|Domain-Specific Language]] Versus Library [[API]] Shooto...
  8. Excel (5,816 bytes)
    7: ...010]] (btw. you can get slides from here: [[Image:Domain-library-shootout.pdf]]). [[Rich]] said that his c...
  9. JavaOne2011 (5,743 bytes)
    32: Join us to learn how to design a [[DSL|Domain Specific Language]] in [[Java]], how to improve t...
    48: ...aunch''. This kind of [[startup|start]], when all OS I/O caches are completely empty is very important...
  10. Micronaut (1,737 bytes)
    9: ...ation]] Shootout (slides are available as [[Image:Domain-library-shootout.pdf]]). with [[RichUnger]] from ...
  11. Domain Expert (2,206 bytes)
    1: ...volution]] will very likely suffer (unless such [[Domain Expert]] reads [[TheAPIBook]] first).
    3: ...without appropriate [[wikipedia:Domain knowledge|domain knowledge]]?
    5: ...about [[Truffle]], but certainly [[I]] am not a [[Domain Expert]], yet I am supposed to design something a...
    11: ...can be good [[API]] designer without being real [[Domain Expert]]. Soon we'll find out if [[API]] Design c...
    13: ... to [[design API as a service]] without being a [[Domain Expert]].
  12. Curriculum vitae (5,736 bytes)
    7: ...il: jaroslav.tulach (at) [[APIDesign|apidesign]] (domain) org
    9: work: jaroslav.tulach (at) enso (domain) org
  13. Design API as a service (27 bytes)
    1: #REDIRECT [[Domain Expert]]
  14. Design as a service (27 bytes)
    1: #REDIRECT [[Domain Expert]]
  15. TwoYearsWithTruffle (18,456 bytes)
    1: ...n API as a service]] or whether one has to be a [[Domain Expert]] when designing an [[API]]. I feel it is ...
    22: ...ork went fine even I still wasn't a [[Truffle]] [[Domain Expert]].
    28: ...was to polish it. That required me to gain some [[Domain Expert]] knowledge, but not that much as the ''in...
    46: This all was achievable without [[Domain Expert]] knowledge of [[Truffle]]. However there ...
    81: ...ng this up was of course easy to do without any [[Domain Expert]] knowledge (except the need to read and c...
  16. APIDevelopment (30,003 bytes)
    119: ...o unlikely that the reviewers are going to become domain experts and help you understand your users or you...
  17. APIReviewSteps (10,464 bytes)
    83: ...find four reviewers (from the people who know the domain, for users of proposed API and from those who und...

View (previous 20) (next 20) (20 | 50 | 100 | 250 | 500)



Search in namespaces:

List redirects
Search for
Views
Personal tools
buy