Re: REST impact paper

On 9/7/17 5:12 PM, Joseph S. Barrera III wrote:
>> Each of us only knows a subset, and newbies know nothing.  A good
> architecture book covers a lot, but
>> usually without context of the turning points and their direct and
> indirect meaning.  It would be helpful to
>> have something like a Pirate Code for various branches of technology.
> You could call them "patterns" or something.

That's usually used a bit more narrowly, but close enough.  Or you could refer to software patterns, more generically, as concepts.  
In my recent way of looking at things, they are concepts that can be captured in close to the same form, the same morphology.  At 
least in terms of metadata; the actual core concept is still expressed in free form paragraphs and diagrams.

Perhaps most of what I'm thinking about could be covered as design patterns, but that isn't what people have done that I've seen so 
far.  Can you point to a better list?

http://www.mcdonaldland.info/2007/11/28/40/
http://www.dofactory.com/net/design-patterns
https://en.wikipedia.org/wiki/Software_design_pattern#Classification_and_list
https://dzone.com/refcardz/design-patterns

That is interesting for what it is, but completely misses things like:

Connection oriented vs. packet switching vs. RPC vs. message routing in various senses.
TCP/IP vs everything else.
EDI vs. ASN.1 vs. XML vs. JSON vs. MsgPack / many.
Unix vs. everything else.
ODBC vs. JDBC vs. various modern solutions.
OS / VM / containers.

For many of those, you could quantify resources wasted and/or redirected and development delay for things that were local 
minima/maxima in some sense.

sdw

>
> On Thu, Sep 7, 2017 at 4:58 PM, Stephen D. Williams <[email protected]> wrote:
>
>> Looks like a cool list.  Have to study it.
>>
>> We should consider theory vs. practice, and practice vs. commercial
>> feasibility / success vs. ubiquity vs. free/wide use separately.
>> Frequently linked, but they happen in different waves, sometimes widely
>> separated, so it would be even more muddled to be tracked in one framework.
>>
>> Nothing is very clean.  But some points are clear and others clear enough
>> to consider.  Besides REST, there are plenty of examples, to wit: IETF, Jon
>> Postel etc.  Even an idea as simple as this was a turning point (regardless
>> if it was from a single person or a general consensus of the time, as often
>> happens):
>>
>> "Be conservative in what you send and liberal in what you accept"
>>
>> https://tools.ietf.org/html/rfc4677
>>
>> In computing, politics, and other areas, there are plenty of singular
>> concepts that bifurcate groups and/or time periods.  It would be
>> interesting to catalog those.  A lot of successful companies started with a
>> concept that was new or implemented in a new way.
>>
>>
>> More important than the curiosities of history would be usability as a
>> roadmap of concepts, plateaus of sophistication, and foibles that one
>> should be aware of.  I use many such principles every day, mostly as reflex
>> now.  We could briefly summarize before and after for internalization
>> justification.
>>
>> Each of us only knows a subset, and newbies know nothing.  A good
>> architecture book covers a lot, but usually without context of the turning
>> points and their direct and indirect meaning.  It would be helpful to have
>> something like a Pirate Code for various branches of technology.
>>
>> http://mentalfloss.com/article/58900/11-rules-actual-pirate-code
>> http://pirates.wikia.com/wiki/Code_of_the_Pirate_Brethren  Haha
>> http://pirates.wikia.com/wiki/Pirata_Codex  Jaja
>>
>> Coding Codex?
>>
>> Stephen
>>
>>
>> On 9/7/17 12:56 PM, Gregory Alan Bolcer wrote:
>>
>>> Fill us in.  I don't think computing, science, or software is that clean.
>>>
>>> I grew up (professionally) with grand computing challenges.
>>> http://www.grids.ac.uk/Complex/grand_challenges/
>>>
>>> I don't think these are the same ones, but it's an interesting list.
>>> My favorite:  Exploiting division by zero;
>>>
>>> Greg
>>>
>>> On 9/7/2017 10:21 AM, Stephen D. Williams wrote:
>>>
>>>> There are some interesting problems with also capturing the temporality
>>>> of things, including things that sped up or held back invention /
>>>> adoption.  I can see a couple possibilities.
>>>>
>>> _
>>>
>> _______________________________________________
>> FoRK mailing list
>> http://xent.com/mailman/listinfo/fork
>>
> _______________________________________________
> FoRK mailing list
> http://xent.com/mailman/listinfo/fork


-- 
Stephen D. Williams [email protected] [email protected] LinkedIn: http://sdw.st/in
V:650-450-UNIX (8649) V:866.SDW.UNIX V:703.371.9362 F:703.995.0407
AIM:sdw Skype:StephenDWilliams Yahoo:sdwlignet Resume: http://sdw.st/gres
Personal: http://sdw.st facebook.com/sdwlig twitter.com/scienteer

_______________________________________________
FoRK mailing list
http://xent.com/mailman/listinfo/fork