It was fun

Download
Share  Add to  Flag Embed
Uploaded from authorPOINT
Views:
 
Category: Entertainment
     
 
License:   All Rights Reserved

Presentation Description

No description available.

Comments

Presentation Transcript

Slide1: 


It Was Fun: 

It Was Fun While It Lasted

It Wasn't Much Fun: 

It Wasn't Much Fun 1959, Moscow (USSR), M.Sc. Thesis I was a computer

It Was Fun: 

It Was Fun 1960, Manchester (UK), Mercury When love prevails Logic fails So the computer Was made neuter

It Was Fun: 

It Was Fun Computing meteor stream orbits

It Was Fun: 

It Was Fun Running simulations of meteor swarm’s evolution

It Was a Mistake: 

It Was a Mistake I thought the computer was for computing (Just as Aristotle thought brain was for cooling blood)

But it took me long time to see the light: 

But it took me long time to see the light First I thought computers were too difficult to program

But it took me long time to see the light: 

But it took me long time to see the light So I wrote compilers KLIPA, ALGOL-60

But it took me long time to see the light: 

But it took me long time to see the light Then I thought running programs on computers was too messy

But it took me long time to see the light: 

But it took me long time to see the light So I wrote an operating system SODA

But it took me long time to see the light: 

But it took me long time to see the light Then I thought something was amiss with the data

But it took me long time to see the light: 

But it took me long time to see the light So I played with data structures

And I’ve sinned: 

And I’ve sinned For five long years I worked in the industry. Directing the transfer of OS/360 to Polish-made RIAD computers.

Much later (1983, Dublin): 

Much later (1983, Dublin) Responding to an invited paper I said: Fred Brooks is a hard act to follow: I know, I’ve lifted the OS/360 !

Then I thought I saw the light : 

Then I thought I saw the light Computer is for executing programs!

Programming methodology: 

Programming methodology Structured programming (programming structures) GOTO considered harmful

Programming methodology: 

Programming methodology Step-wise refinement Correctness

Programming methodology: 

Programming methodology Correctness, yes but what does it mean? With respect to ...

Programming methodology: 

Programming methodology Correctness wrt formal specification - „faultily faultless' - clear, but useless

Programming methodology: 

Programming methodology Specs Reality Program Correctness ? Ill-defined relationship

Programming methodology: 

Programming methodology Theory Model Model Satisfaction Satisfaction Well-defined relationship

I was sure I saw the light: 

I was sure I saw the light It all reduces to theories. A good theory leads to good programs and satisfied customers. A poor theory hinders construction of good programs and makes customers weep.

I was sure I saw the light: 

I was sure I saw the light Build theories of small domains, make program-models for them, then combine theories and programs shall jell together!

I was sure I saw the light: 

I was sure I saw the light But it ain’t necessarily so! combining theories is difficult (and not always possible) combining implementations is (nearly always) messy and often dangerous

I was sure I saw the light: 

I was sure I saw the light I thought that perhaps combinig little actions into larger systems should be done entirely without any notion of „time', i.e even without any predetermined notion of „follows'.

I was sure I saw the light: 

I was sure I saw the light Thus the concept of doubly guarded command was born and (partially) explored

But while I followed the light: 

But while I followed the light The world was changing became the soup du jour

In the new brave world: 

In the new brave world Computers, becoming ever more numerous (and physically smaller), disappear behind services they provide.

In the new brave world: 

In the new brave world Computation has to be correct. Service has to be dependable.

In the new brave world: 

In the new brave world The mathematical, strict criterion of correctness is being replaced by a behavioural, loose criterion of dependability.

In the new brave world: 

In the new brave world All actors (people, machines and systems thereof) occasionally malfunction. This is not only accepted, but also expected.

In the new brave world: 

In the new brave world No-one really complains that Windowsâ is prone to crash, only that it crashes at an inopportune moment.

In the new brave world : 

In the new brave world Like no-one complains that tires occasionally go flat, only that it happens when we are particularly short of time.

In the new brave world: 

In the new brave world No-one is to blame and the guilt is subtly shifted to the „user': If I only didn’t drive there, if I only didn’t press these two keys together! Or was it three?

In the new brave world: 

In the new brave world Every hour more users than babies are born. Each user soon becomes an expert at their specific fingering. Such an expertise quickly becomes an article of faith and an academic discipline.

In the new brave world: 

In the new brave world Particular fingerings turned articles of faith cum academic disciplines are invested.

An aside, from Webster’s:: 

An aside, from Webster’s: invest - to array in the symbols of office and honor to furnish with power or authority to surround with troops or ships so as to prevent escape or entry to commit money in order to earn a financial return

In the new brave world: 

In the new brave world In the ecumenical primordial ocean of Internet, growth is primarily by accretion of external grime. Reason is yet to be born: while no-one convinces, many try to catch.

In the new brave world: 

In the new brave world Correctness, rigour, mathematics of computing is pushed into an ever smaller and darker corner labelled „special concerns'.

I have the feeling that: 

I have the feeling that Having witnessed the birth of computing science, I am witnessing its demise.

While it lasted: 

While it lasted It certainly was fun!

Slide43: 

?