Sign in to confirm you’re not a bot
This helps protect our community. Learn more
Leslie Lamport: Thinking Above the Code
8.5KLikes
380,401Views
2014Jul 15
Architects draw detailed blueprints before a brick is laid or a nail is hammered. Programmers and software engineers seldom do. A blueprint for software is called a specification. The need for extremely rigorous specifications before coding complex or critical systems should be obvious—especially for concurrent and distributed systems. This talk explains why some sort of specification should be written for any software. http://www.microsoftfacultysummit.com

Follow along using the transcript.

Microsoft Research

348K subscribers