OpenLLM-France/wikimedia huggingface dataset:
# Security engineering

Security engineering is the field of engineering dealing with the security and integrity of real-world systems. It is similar to systems engineering in that its motivation is to make a system meet requirements, but with the added dimension of enforcing a security policy. It has existed as an informal field for centuries, in the fields of locksmithing and security printing.
Technological advances, principally in the field of computers, have now allowed the creation of far more complex systems, with new and complex security problems. Because modern systems cut across many areas of human endeavor, security engineers not only need consider the mathematical and physical properties of systems; they also need to consider attacks on the people who use and form parts of those systems using social engineering attacks. Secure systems have to resist not only technical attacks, but also coercion, fraud, and deception by confidence tricksters.
For this reason it involves aspects of social science, psychology and economics, as well as physics, chemistry and mathematics. Some of the techniques used, such as fault tree analysis, are derived from safety engineering.
Other techniques such as cryptography were previously restricted to military applications. One of the pioneers of security engineering as a formal field of study is Ross Anderson.

## Sub-fields of security engineering

* Computer security
* Physical security
* Information security
* Economics of security
* Locksmithing

## Patterns & Practices

The patterns & practices Security Engineering consists of the following activities:
* Security Objectives
* Security Design Guidelines
* Security Modeling
* Security Architecture and Design Review
* Security Code Review
* Security Testing
* Security Tuning
* Security Deployment Review
These activities help meet security objectives in the software life cycle.
# Secondary dominants

The dominant note in a scale is the fifth note of that scale.
The C major scale consists of the notes C D E F G A B. In C Major, G would be the dominant or fifth note. The tonic note in a scale is the first note of that scale, in C Major C would be tonic. The secondary dominant is the the dominant of the dominant or the five-of-five. If you begin in C major the secondary dominant would be D, which is the dominant of G.
However the scale that begins and ands on D in the key of C major is a minor one (actually, it is known as the 'dorian' mode WWHWWHW [W=Whole tone/Maj 2nd, H=half tone/min 2nd]).
So to strengthen the 'dominant effect', we raise the F one half step to F# (not coincidentally this is the 'leading tone' for the root of the next intended chord: G) Thus creating a major chord which has a strong harmonic tendency to resolve to the G major chord that is functioning as the dominant in the key of C major. This is one of the natural ways that accidentals can occur and is not considered in itself a full 'modulation'.
The secondary dominant can be used to prepare chords on other 'degrees' of the scale as well; the tonic, with the addition of the lowered 7th degree, is often used as the dominant of the sub-dominant etc.
# Secret Santa/Fixpointfree/Method/Paper/Exercise

There are $n\geq 4$ persons in a room and they would like to play secret Santa. This means that for each person $A$, another person $B\neq A$ has to be determined to whom $A$ has to give a gift. Every person is only allowed to know who to give the gift, no one is allowed to know more. The people stay the whole time in the room, they do not look away. They only have paper and pens. They are allowed to shuffle and to look in secret at choosen cards. Describe a procedure to determine a gift relation which satisfies all conditions.
# Security

Security may refer to:
* School:Computer forensics and security
* School:Security, surveillance and law enforcement
* Security engineering
* Information security
* IT Security
# Secrets of successful long-term intimate relationships

This psychology resource is a "stub". Learn how you can help Wikiversity to develop it.
# R^2/Rotation/Definition

A linear mapping
    $D(\alpha )\colon \mathbb {R} ^{2}\longrightarrow \mathbb {R} ^{2},$
which is given by a rotation matrix ${\begin{pmatrix}\operatorname {cos} \,\alpha &-\operatorname {sin} \,\alpha \\\operatorname {sin} \,\alpha &\operatorname {cos} \,\alpha \end{pmatrix}}$ (with some $\alpha \in \mathbb {R}$) is called rotation.
# R^2/Subsets/Sketch/3/Exercise

Sketch the following subsets of $\mathbb {R} ^{2}$.
* ${\left\{(x,y)\mid x+y=3\right\}}$,
* ${\left\{(x,y)\mid x+y\leq 3\right\}}$,
* ${\left\{(x,y)\mid (x+y)^{2}\geq 4\right\}}$,
* ${\left\{(x,y)\mid \vert {x+2}\vert \geq 5{\text{ and }}\vert {y-2}\vert \leq 3\right\}}$,
* ${\left\{(x,y)\mid \vert {x}\vert =0{\text{ and }}\vert {y^{4}-2y^{3}+7y-5}\vert \geq -1\right\}}$,
* ${\left\{(x,y)\mid -1\leq x\leq 3{\text{ and }}0\leq y\leq x^{3}\right\}}$.
# R^2 to R^2/Linear/Image of a square/Exercise

Which of the following geometric shapes can be the image of a square under a linear mapping from $\mathbb {R} ^{2}$ to $\mathbb {R} ^{2}$?
# R^2/Circle/Circumference/Definition

Let $M=(a,b)\in \mathbb {R} ^{2}$ and $r\in \mathbb {R} _{+}$. Then the set
    ${\left\{(x,y)\in \mathbb {R} ^{2}\mid (x-a)^{2}+(y-b)^{2}=r^{2}\right\}}$
is called the circle with center $M$ and radius $r$.
# R^2/Subsets/Sketch/Exercise

Sketch the following subsets of $\mathbb {R} ^{2}$.
* ${\left\{(x,y)\mid x=5\right\}}$,
* ${\left\{(x,y)\mid x\geq 4{\text{ and }}y=3\right\}}$,
* ${\left\{(x,y)\mid y^{2}\geq 2\right\}}$,
* ${\left\{(x,y)\mid \vert {x}\vert =3{\text{ and }}\vert {y}\vert \leq 2\right\}}$,
* ${\left\{(x,y)\mid 3x\geq y{\text{ and }}5x\leq 2y\right\}}$,
* ${\left\{(x,y)\mid xy=0\right\}}$,
* ${\left\{(x,y)\mid xy=1\right\}}$,
* ${\left\{(x,y)\mid xy\geq 1{\text{ and }}y\geq x^{3}\right\}}$,
* ${\left\{(x,y)\mid 0=0\right\}}$,
* ${\left\{(x,y)\mid 0=1\right\}}$.
# R^3/Endomorphism/Has eigenvector/Exercise

Let
    $\varphi \colon \mathbb {R} ^{3}\longrightarrow \mathbb {R} ^{3}$
be a linear mapping. Show that $\varphi$ has at least one eigenvector.
# Origami

Origami is the art of folding squares of paper. Projects may be made of one or more sheets of paper, with the pieces folded and held together without the use of glue, tape, or string. One of the most popular models is the paper crane.
Origami is basically a Japanese art where "oru" meaning "folding" and "kami" meaning "paper". The art was originally developed by the Chinese, but later spread to the Japan because the Japanese started producing paper more efficiently and hence their paper was a lot cheaper than that produced by the Chinese. Slowly the art spread across the world and written instructions were produced in the form of books. Today, a lot of material is easily available in the internet.
In education, origami can be used in primary grades for art and geometry lessons without any stretch of the imagination. Grade school students are able to learn and fold very well (although there are plenty of advanced and complex techniques to keep people interested all their life). In addition, it's certainly a useful topic in any cultural study of Japan, though it is also an interesting part of Chinese and Spanish history as well. A teacher who likes origami would have no problem working something into any school subject.
Practicing origami has frequently been shown to help develop spatial skills and other cognitive processes.

## Origami folds

Almost all origami books use an internationally known set of symbols which are well represented elsewhere. Here are a few of the most important ones:
| Mountain Folds | A mountain fold is created by folding the paper back. | |
| Valley folds | A valley fold is created by folding the paper towards you. | |
| Creases | Creases are frequently used in origami as guides and to make more complex folds easier. Direction is sometimes important, as folding and unfolding a valley or mountain fold will affect which direction the paper will naturally fold later. | Fold and unfold mountain. |
| Creases | Creases are frequently used in origami as guides and to make more complex folds easier. Direction is sometimes important, as folding and unfolding a valley or mountain fold will affect which direction the paper will naturally fold later. | Fold and unfold valley |
| Open or Squash fold | Opening a pocket formed by the folds and flattening it in a different direction is more complicated, but a frequently-used technique. | |
| Inside reverse | An inside reverse fold is created by pushing a folded edge down, creating two mountain folds. | |
| Outside reverse | An outside reverse fold is created by pulling a folded edge back, creating two valley folds. It is often necessary to open the original fold somewhat in order to do this. | |

## Examples

* Examples 1
* Examples 2
# Original Story for Seduced by the Dark Side

| The Story Here is the original story that we will make into a movie at Wikiversity Film School. It is a story of how two people bond together. It is a story which tells how some people can know yet willingly accept evil. It explains how it is so easy to be so seduced by the dark side. Pop quiz Be sure to take our pop quiz where you design the first two frames of our movie. | "Seduced by the Dark Side!" An old (yet wise) person and a young (but curious) person are outside a movie theater where they have just seen the movie "Star Wars". Now they stand looking at the movie poster on the wall outside the theater. The younger person says, "That was a great movie... but I don't understand one thing." The older person says, "Hum, what's that?". The young person says, "I don't understand how anyone can be 'seduced by the dark side'". The older person thinks for a while and then answers, "What computer do you use at home?" The young person immediately responds eagerly, "A Macintosh." Then the older person slowly says, "But what computer does your father use at work?" The young person thinks for a while and then smiles in amazement, exclaiming loudly, "Seduced by the Dark Side!" The older person smiles knowingly at the young person. The young person is very happy knowing he has just learned a very important lesson. Now the two have formed a bond that will last a lifetime. They begin walking slowly home together. The End |
# Origami/Examples 1
## TO MAKE REGULAR PENTAGONS

[ INSERT PICTURE "STAR.jpg" HERE. -- RCB]
Ray Calvin Baker (talk) 03:14, 15 May 2012 (UTC)

## I. MAKING 3-D SHAPES (Paper Sculpture)

TETRAHEDRON
CUBE
OCTAHEDRON
TWELVE REGULAR PENTAGONS
TWENTY EQUILATERAL TRIANGLES
Ray Calvin Baker (talk) 22:42, 1 May 2012 (UTC)

## XI. THE SITTING CRANE

Ray Calvin Baker (talk) 20:45, 13 April 2012 (UTC)
# Software Design/Specify interface contracts

This page augments Design by contract article on Wikipedia.

## Why

Well-specified interface contracts reduce cases when clients intentionally or unintentionally rely on unspecified behaviour, thus making the client code more robust.
Conversely, when clients don't use unspecified behaviour, maintaining the interface's compatibility doesn't require researching the code of the clients.

## Sources

* David Thomas; Andrew Hunt (2019). The Pragmatic Programmer (20th Anniversary ed.). Addison-Wesley Professional. ISBN 978-0135957059.
# Software Design/Transform collection declaratively

Checklist questions:
* Is it possible to transform or populate a collection or an array declaratively rather than in an imperative loop?
* Is it possible to find or compute some result while iterating a collection with a declarative operation rather than an imperative loop?
The technologies which facilitate declarative computations on collections include:
* LINQ in C#
* Streams in Java
* List comprehensions, generator expressions, and some functions from the itertools module in Python

## Why

It's harder to make a mistake in a declarative or functional transformation than in an imperative loop because less (or none) additional variables are defined in the transformation and each of them is scoped to its anonymous function without interfering with other variables.
The semantics of a declarative pipeline may be more apparent because they refer to library symbols such named like "sum", "map", "where", "collect", "findFirst", etc. which identify the logical operation being applied. On the other hand, with collection transformation in an imperative loop, readers have to read the whole loop and recognize the logical operation being applied by the loop pattern, which puts cognitive load on them.
Functional collection processing usually requires less code than imperative. Functional processing is also often clearer than imperative processing because the former is free of boilerplate code such as a declaration of a loop variable and references to a collection element by index. Since functional collection transformation is free of low-level details about how to iterate the collection, it makes the definition of the collection and the processing logic looser coupled.
Declarative computations over a collection automatically ensure following the practice of not doing several collection transformations in a single loop.

## Why not

It may be harder to debug declarative collection computations than equivalent imperative loops.
Functional collection transformation pipeline may be less efficient than an equivalent imperative code. Even when the performance difference between optimally written functional and imperative versions is not significant, it might be easy to make a performance bug in a declarative pipeline which would lead to unnecessary materialization of intermediate collection views. For example, in Kotlin, this is sometimes a matter of forgetting asSequence call in the beginning of a pipeline.

## Related

* Don't mingle several collection transformations in a single loop

## Sources

* Goetz, Brian (July 6, 2016). "An introduction to the java.util.stream library".
# Software Design/Shorten variable's name to the first letter of the type noun

Checklist question:

## Example

If the type of the variable is MyEntry, call the variable e: the first letter of the noun "entry".

## Related

* Name a variable semantically
# Software Design/Steepness of learning curve

Steepness of learning curve is a high-level software, interface, and code quality that reflects how much effort a user or a developer has to put into learning the software, or the interface, or the codebase before they can use the software or the interface, or work with the codebase effectively.
The essential contributing factors to the steepness of the learning curve are the complexity and the conceptual weight of some software, interface, or code. The primary software qualities and factors that may contribute to accidental steepness of learning curve are
* Inconsistency in naming, parameter order in functions, code formatting, etc.
* Obscure code.
* Codebase requiring to navigate a lot.
* Untraceable code behavior.
* Unknown unknowns stemming from unapparent dependencies and poor discoverability of the software.

## Relevant practices

* Don't hide an object access chain
# Software Design/Structuredness

Structuredness is a code and interface quality that reflects the proportion between the information that constitutes the code or the interface governed by some style rules, conventions (including naming conventions), design and programming patterns, and the unique information.
Structuredness, as defined in the Software Design project, should not be confused with McCabe's structuredness.

## Relations to other qualities

Higher structuredness is not necessarily better for the ultimate software quality, as exemplified by satiric projects such as FizzBuzz Enterprise Edition. However, unnecessary unstructuredness, or inconsistency, makes the code or the interface more complex and its learning curve steeper which makes code harder to navigate and read.
It may be easier to spot clerical errors in highly structured code than in the code which is equivalent in size, but is chaotically organized because the developer can follow the visual pattern of the structured code without much mental effort and focus only on the business logic details. Maintaining the structure also helps to reduce the size of change sets in the revision control system because the structure itself typically won't be changed often. While reviewers find bugs in smaller changes sets more effectively.

## Relevant practices

* Always use the same way to do a thing
* Arrange parameters in a consistent order
* Call function's return variable "result"
* Minimize the diff between implementations of a strategy
* Object access chains: either always or never encapsulating them.
# Software Design/Testability
## Relevant practices

* Hide an object access chain
# Software Design/Split responsibilities between classes and functions

Checklist questions:
* Does a class have a single responsibility?
** A business logic area
** An external integration (database, service, API)
** A domain data object, a builder, or a configuration class for another class
** An aspect of the program's control flow or data flow, such as an active object, or an object integrating other objects
* Does a function have a single responsiblity?
** A single business logic operation
** A single kind of external operation (e. g. a specific API call or a database operation)
** An aspect of program's control flow, or a function integration other functions (including higher-order functions)
* If a function has more than three (3) parameters, couldn't its responsibilities be split between multiple functions?
This practice corresponds to the Single Responsibility Principle, applied on the level of classes.

## Why

* Steepness of learning curve: less cognitive load when learning the code, the learning process is more manageable
* Easiness of future change: replace classes and functions, combine them in different ways
* Reusability: more likely that focused classes and functions could be reused in several places in the codebase, fostering DRY
* Testability: unit-testing of small classes and functions doesn't require mocking or fragile control of side effects
* Debuggability: debugging is not needed or quicker when a focused unit test fails
* Observability: in profiling results, the bottleneck could be identified more clearly. Sizes of queues between classes organized in a SEDA-like pipeline could be monitored.
* Software Design/Structuredness: when followed consistently, Single Responsibility Principle is itself a form of structure

## Why not

* Splitting responsibilities results in more code, classes, and functions
* More navigation between classes and functions is required
* Resource usage and performance: more classes and functions need to be compiled and/or loaded by the runtime. More calls and more code mean less effective usage of the instruction cache.

## Related

* Extract Class refactoring
* Extract loosely coupled parts of a class into smaller classes
* Break up too large and complex functions
* Extract self-contained pieces of logic as functions
* Keep the number of function arguments low entry in C++ Core Guidelines suggests that a function having too many parameters is a hint that it may have multiple responsibilities.
# Software Design/Transform data with pipeline operator

Pipeline operator sends the expression from the left-hand side to the function on the right-hard side. It appears in Elixir, Elm, F#, Haskell (via a third-party library) and R .

## Examples

In Elixir:

## Why

The written sequence of functions corresponds to how are applied one after another, which makes the code more natural to read.

## Why not

There are many situations where the pipeline operator is not applicable: for example when the expression should be sent to a function with several parameters as a non-last parameter. Using several different function application forms can be seen as inconsistency: it's against the practice to always use the same way to do a thing.

## Related

* Choose programming language or framework similar to the language of the problem domain

## Sources

* David Thomas; Andrew Hunt (2019). The Pragmatic Programmer (20th Anniversary ed.). Addison-Wesley Professional. ISBN 978-0135957059.
# Paideia High School/Gettysburg Address/dedicate

dedicate: 1.(transitive) To set apart for a deity or for religious purposes; consecrate. 2.(transitive) To set apart for a special use
# Paideia High School/Gettysburg Address/devotion

devotion: 1.The act or state of devoting or being devoted 2.Feelings of strong or fervent affection; dedication
# Paideia High School/Gettysburg Address/engage

engage: 1.(transitive) To engross or hold the attention of (someone); to keep busy or occupied. 2.(transitive) To draw into conversation. 3.(transitive) To attract, to please; (archaic) to fascinate or win over (someone). 4.(transitive) To enter into conflict with (an enemy). 5.(intransitive) To enter into battle.
# Paideia High School/Gettysburg Address/consecrate

consecrate: 1. To declare, or otherwise make something holy.
# Paideia High School/Gettysburg Address/conceive

conceive: 1.(transitive) To develop an idea. 2.(transitive) To understand someone
# Paideia High School/Gettysburg Address/detract

detract:
1.(transitive) To take away; to withdraw or remove. 2.(transitive) To take credit or reputation from; to defame or decry.
# Student Projects/Natural vegetation of India

Introduction
The trees and plants that grow without any intervention of human beings and grow naturally depending upon factors like soil, temperature and rainfall etc. For example forests, grasslands. India is home to many varieties of plant species and one of the bio-diversity countries of the world.
Types of Natural vegetation in India:
1.Tropical Evergreen forest
2.Tropical deciduous forest
3.Thorny
4. Mountain vegetation
Tropical Evergreen :
The word evergreen itself denotes that the forest is evergreen throughout the year. This type of forests is heterogeneous in nature. Mahogany, Ironwood, Ebony are some the trees grown in this type of vegetation in India. Regions: west coast of India, North East of India and Andaman and Nicobar.
This type of vegetation is possible only in the areas where rainfall is more than 200 cm.
Tropical Deciduous forest :
This type of forest is mostly dominated by few varieties of plants and trees were at particular season majority of trees shed their leaves in a particular season. Teak, Sal, sandalwood are some examples of this type of vegetation. This type of vegetation needs more 70 - 200 cm of rainfall. They are homogeneous in nature.
Thorny vegetation :
This type of vegetation is seen in the desert. Where less rainfall and dry. Cactus, dates palm are some of the plant species grown in this type of vegetation. This type of is dominated in regions of Rajasthan and interior of Deccan plateau.
Mountain vegetation :
This type of vegetation is found in mountain regions and it varies and further, it is classified into many. This type of vegetation is found in the Himalayas and western ghats.