History of software engineering | Wikipedia audio article
Channel: wikipedia tts
Date: 2019-01-13

This is an audio version of the Wikipedia Article:
https://en.wikipedia.org/wiki/History_of_software_engineering


00:01:13 1 Overview
00:03:48 2 1945 to 1965: The origins
00:04:54 3 1965 to 1985: The software crisis
00:08:03 4 1985 to 1989: "iNo Silver Bullet/i"
00:09:14 4.1 Software projects
00:13:07 5 1990 to 1999: Prominence of the Internet
00:15:08 6 2000 to 2015: Lightweight methodologies
00:16:18 6.1 Current trends in software engineering
00:16:40 6.1.1 Aspects
00:17:31 6.1.2 Agile
00:18:18 6.1.3 Experimental
00:18:53 6.1.4 Software product lines
00:19:57 6.2 Software engineering today
00:20:49 7 Sub-disciplines
00:20:59 7.1 Artificial intelligence
00:22:05 7.1.1 Languages
00:22:33 8 Prominent figures in the history of software engineering
00:24:20 9 See also



Listening is a more natural way of learning, when compared to reading. Written language only began at around 3200 BC, but spoken language has existed long ago.

Learning by listening is a great way to:
- increases imagination and understanding
- improves your listening skills
- improves your own spoken accent
- learn while on the move
- reduce eye strain

Now learn the vast amount of general knowledge available on Wikipedia through audio (audio article). You could even learn subconsciously by playing the audio while you are sleeping! If you are planning to listen a lot, you could try using a bone conduction headphone, or a standard speaker instead of an earphone.

Listen on Google Assistant through Extra Audio:
https://assistant.google.com/services/invoke/uid/0000001a130b3f91
Other Wikipedia audio articles at:
https://www.youtube.com/results?search_query=wikipedia+tts
Upload your own Wikipedia articles through:
https://github.com/nodef/wikipedia-tts
Speaking Rate: 0.7530612260462961
Voice name: en-US-Wavenet-D


"I cannot teach anybody anything, I can only make them think."
- Socrates


SUMMARY
=======
From its beginnings in the 1960s, writing software has evolved into a profession concerned with how best to maximize the quality of software and of how to create it. Quality can refer to how maintainable software is, to its stability, speed, usability, testability, readability, size, cost, security, and number of flaws or "bugs", as well as to less measurable qualities like elegance, conciseness, and customer satisfaction, among many other attributes. How best to create high quality software is a separate and controversial problem covering software design principles, so-called "best practices" for writing code, as well as broader management issues such as optimal team size, process, how best to deliver software on time and as quickly as possible, work-place "culture", hiring practices, and so forth. All this falls under the broad rubric of software engineering.