{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

A Brief History of Software

A Brief History of Software - up our code and what can...

Info iconThis preview shows pages 1–2. Sign up to view the full content.

View Full Document Right Arrow Icon
A Brief History of Software Michael Lopp, Rands in Repose Open Source Conference from O'Reilly Media 18 minutes, recorded 2009-07-22 This podcast is available at:  http://itc.conversationsnetwork.org/audio/download/ITC.oscon-Lopp-2009.07.22.mp3 In this OSCON presentation Michael Lopp, author of the blog Rands in Repose, takes a trip down memory lane to  1992, and brings a few lessons in software development back to the future. He discusses the well intentioned 'forces  of evil' that can make us stray from the path of tight coding, and how, in software development, the small decisions  are just as important as the bigger ones. Lopp's alternative title for his presentation is 'R.I.P Borland', and he uses an old copy of Paradox, Borland's desktop  database product, to raise some pertinent coding questions. When the entire Paradox application is less than half the  file size of his keynote, are we, as developers, getting lazy? Are we becoming digitally in debt? Why should we clean 
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Background image of page 2
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: up our code and what can prevent us from doing so? Complete the sections below: Homework Submission Code: This four-digit code was assigned by your course instructor and is required to get credit for this assignment. 4960 What part of this podcast was most interesting to you and why? The way Borland company dares to compete with the most widely used software – Access of Microsoft. If you could ask Michael Lopp one question about the content of the presentation, what would it be? What do you mean by mentioning “well intentioned forces of evil”? How does this podcast relate to the content of its associated lecture topic? The lecture is about system development and design of IT services. What were your thoughts about Michael Lopp’s comment about software and “well intentioned forces of evil”? I am not sure why he used that phrase. I guess the forces of evil here are the undermining things that hamper the development of the system....
View Full Document

{[ snackBarMessage ]}