Applications vs. Capabilities

Applications vs. Capabilities

You can design a system by creating applications, or you can design a system by building capabilities: I argue that we used to do the later, but since industrialism we’re doing more of the former, especially in libraries.

E2ed169f43b7aae4f46de5fa9ef837e9?s=128

Peter Rukavina

October 02, 2009
Tweet

Transcript

  1. presented at access 2009 october 2, 2009 peter rukavina http://ruk.ca/

    creative commons Attribution-Noncommercial-Share Alike 2.5 Canada license
  2. Applications vs. Capabilities (beta)

  3. when designing a system you can...

  4. build applications

  5. build capabilities

  6. the farm

  7. None
  8. None
  9. None
  10. None
  11. flexible multi-use systems for multi-talented generalists

  12. farmers do a lot of different stuff

  13. build capabilities (to do this stuff...)

  14. the factory

  15. None
  16. None
  17. None
  18. None
  19. None
  20. inflexible purpose- built systems for uni-talented specialists

  21. factory workers do one thing, over and over

  22. build applications (to make this possible...)

  23. None
  24. None
  25. “Industrialism led not only to new machinery, but also to

    new ways of thinking and acting”
  26. the systems design paradigm changed

  27. Capabilities systems design paradigm

  28. applications systems design paradigm

  29. not opposites but sensibilities

  30. capabilities interrelated malleable organic extensible invisible in the flow natural

    applications discrete manageable predictable billable obvious demarcated artificial
  31. Capabilities systems design paradigm return to a

  32. examples

  33. unix command line (capabilities)

  34. # grep os_fingerprint wifi.xml | sort | uniq -c 17

    <os_fingerprint>Apple iPhone</os_fingerprint> 1 <os_fingerprint>Linux</os_fingerprint> 46 <os_fingerprint>Mac OS X</os_fingerprint> 27 <os_fingerprint>Windows XP</os_fingerprint>
  35. copenhagen bicycle ramps (capabilities)

  36. None
  37. royal botanical gardens (applications)

  38. None
  39. None
  40. None
  41. None
  42. charlottetown boulder park (capabilities)

  43. None
  44. library coffee shops (applications vs. capabilities)

  45. None
  46. None
  47. None
  48. broadband for pei (applications vs. capabilities)

  49. None
  50. None
  51. flip mino (capabilities)

  52. None
  53. None
  54. mogensen hanging stools (capabilities)

  55. None
  56. None
  57. qTweeter (capabilities)

  58. None
  59. cisco vs. meraki (applications vs. capabilities)

  60. None
  61. Step 1 The PC you intend to use must be

    configured with a static IP address in the range of 10.0.0.2 to 10.0.0.30. Step 2 Make sure that the PC contains the access point image file (such as c1250-k9w7-tar. 124-10b.JDA3.tar in the TFTP server folder and that the TFTP server is activated. For additional information, refer to the "Obtaining the Access Point Image File" and "Obtaining TFTP Server Software" sections. Step 3 Rename the access point image file in the TFTP server folder. For example, if the image file is c1250-k9w7-tar.124-10b.JDA3.tar for an 12500 series access point, rename the file to c1250-k9w7-tar.default. Step 4 Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable. Step 5 Disconnect power (the power jack for external power or the Ethernet cable for in-line power) from the access point. Step 6 Press and hold the MODE button while you reconnect power to the access point. Step 7 Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button. Step 8 Wait until the access point reboots as indicated by all LEDs turning green followed by the Status LED blinking green. Step 9 After the access point reboots, you must reconfigure the access point by using the Web-browser interface or the CLI.
  62. None
  63. murphy’s community centre (capabilities)

  64. None
  65. prince edward island (capabilities)

  66. None
  67. flexible multi-use system for multi-talented generalists

  68. my network (capabilities)

  69. None
  70. silverorange virtual studios barrett & Mackay robertson library loca lola

    design team the guardian casa mia Hamamoto Noriaki shauna mccabe cbc city cinema moses media peter lux confederation centre internetworks cows allan rankin elections pei aliant kingfisher kayaking Formosa tea house george campbell lm montgomery land trust
  71. george campbell lm montgomery land trust silverorange virtual studios barrett

    & Mackay robertson library loca lola design team the guardian casa mia Hamamoto Noriaki shauna mccabe cbc city cinema moses media peter lux confederation centre internetworks cows allan rankin elections pei aliant kingfisher kayaking Formosa tea house
  72. i offer my network a set of capabilities

  73. my network offers me a set of capabilities

  74. Applications vs. Capabilities

  75. so what?

  76. None
  77. None
  78. 1 2 3 4 5 6 7 9 10 11

    12 13 14 8
  79. None
  80. 1 2 3 5 6 7 8 9 10 4

  81. None
  82. applications capabilities

  83. None
  84. None
  85. run a book and reading management application if the library’s

    mission to...
  86. extend society’s knowledge capabilities if the library’s mission to...

  87. book & reading management application dictionary day armchair travel mark

    twain week knitting club baby lapsit pirate party puppet show extend knowledge capabilities how to podcast defeating DRM how google works editing wikipedia green screen shots vinyl to MP3 citizen protest howto
  88. so...

  89. Capabilities systems design paradigm return to a

  90. we need to think less like...

  91. None
  92. None
  93. and more like...

  94. None
  95. None
  96. None
  97. the nice thing is...

  98. there is prior art...

  99. Applications vs. Capabilities (the end)