Duration: 11:54

2 views

0

This is an audio version of the Wikipedia Article:\nhttps://en.wikipedia.org/wiki/Software_design_pattern\n\n\n00:01:09 1 History
00:04:22 2 Practice
00:05:47 3 Structure
00:06:40 3.1 Domain-specific patterns
00:07:17 4 Classification and list
00:07:58 4.1 Creational patterns
00:08:07 4.2 Structural patterns
00:08:15 4.3 Behavioral patterns
00:08:24 4.4 Concurrency patterns
00:08:33 5 Documentation
00:10:49 6 Criticism
\n\n\nListening 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.\n\nLearning by listening is a great way to:\n- increases imagination and understanding\n- improves your listening skills\n- improves your own spoken accent\n- learn while on the move\n- reduce eye strain\n\nNow 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.\n\nListen on Google Assistant through Extra Audio:\nhttps://assistant.google.com/services/invoke/uid/0000001a130b3f91\nOther Wikipedia audio articles at:\nhttps://www.youtube.com/results?search_query=wikipedia+tts\nUpload your own Wikipedia articles through:\nhttps://github.com/nodef/wikipedia-tts\nSpeaking Rate: 0.8315276563791001\nVoice name: en-AU-Wavenet-D\n\n\n"I cannot teach anybody anything, I can only make them think."\n- Socrates\n\n\nSUMMARY\n=======\nIn software engineering, a software design pattern is a general, reusable solution to a commonly occurring problem within a given context in software design. It is not a finished design that can be transformed directly into source or machine code. It is a description or template for how to solve a problem that can be used in many different situations. Design patterns are formalized best practices that the programmer can use to solve common problems when designing an application or system.
Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Patterns that imply mutable state may be unsuited for functional programming languages, some patterns can be rendered unnecessary in languages that have built-in support for solving the problem they are trying to solve, and object-oriented patterns are not necessarily suitable for non-object-oriented languages.
Design patterns may be viewed as a structured approach to computer programming intermediate between the levels of a programming paradigm and a concrete algorithm.