Go:

Visual Taxonomy

Links

Hide/Show:

Taxonomy Path

Top > Computers > Computer Programming

---

https://en.wikipedia.org/wiki/Computer_Programming

Part of a series on
Software development
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Practices
Tools
Standards and bodies of knowledge
Glossaries
Outlines
v t e

Computer programming is the process of performing particular computations (or more generally, accomplishing specific computing results), usually by designing and building executable computer programs. Programming involves tasks such as analysis, generating algorithms, profiling algorithms' accuracy and resource consumption, and the implementation of algorithms (usually in a particular programming language, commonly referred to as coding).^[1][2] The source code of a program is written in one or more languages that are intelligible to programmers, rather than machine code, which is directly executed by the central processing unit. To produce machine code, the source code must either be compiled or transpiled. Compiling takes the source code from a low-level programming language and converts it into machine code. Transpiling on the other hand, takes the source-code from a high-level programming language and converts it into bytecode. This is interpreted into machine code. The purpose of programming is to find a sequence of instructions that will automate the performance of a task (which can be as complex as an operating system) on a computer, often for solving a given problem. Proficient programming thus usually requires expertise in several different subjects, including knowledge of the application domain, specialized algorithms, and formal logic.

Tasks accompanying and related to programming include testing, debugging, source code maintenance, implementation of build systems, and management of derived artifacts, such as the machine code of computer programs. However, while these might be considered part of the programming process, often the term software development is more likely used for this larger overall process – whereas the terms programming, implementation, and coding tend to be focused on the actual writing of code. Relatedly, software engineering combines engineering techniques and principles with software development. Also, those involved with software development may at times engage in reverse engineering, which is the practice of seeking to understand an existing program so as to re-implement its function in some way.^[3]

History

Ada Lovelace, whose notes added to the end of Luigi Menabrea's paper included the first algorithm designed for processing by an Analytical Engine. She is often recognized as history's first computer programmer.

See also: Computer program § History, Programmer § History, and History of programming languages

Programmable devices have existed for centuries. As early as the 9th century, a programmable music sequencer was invented by the Persian Banu Musa brothers, who described an automated mechanical flute player in the Book of Ingenious Devices.^[4][5] In 1206, the Arab engineer Al-Jazari invented a programmable drum machine where a musical mechanical automaton could be made to play different rhythms and drum patterns, via pegs and cams.^[6][7] In 1801, the Jacquard loom could produce entirely different weaves by changing the "program" – a series of pasteboard cards with holes punched in them.

Code-breaking algorithms have also existed for centuries. In the 9th century, the Arab mathematician Al-Kindi described a cryptographic algorithm for deciphering encrypted code, in A Manuscript on Deciphering Cryptographic Messages. He gave the first description of cryptanalysis by frequency analysis, the earliest code-breaking algorithm.^[8]

The first computer program is generally dated to 1843, when mathematician Ada Lovelace published an algorithm to calculate a sequence of Bernoulli numbers, intended to be carried out by Charles Babbage's Analytical Engine.^[9] However, Charles Babbage had already written his first program for the Analytical Engine in 1837.^[10]

Data and instructions were once stored on external punched cards, which were kept in order and arranged in program decks.

In the 1880s, Herman Hollerith invented the concept of storing data in machine-readable form.^[11] Later a control panel (plug board) added to his 1906 Type I Tabulator allowed it to be programmed for different jobs, and by the late 1940s, unit record equipment such as the IBM 602 and IBM 604, were programmed by control panels in a similar way, as were the first electronic computers. However, with the concept of the stored-program computer introduced in 1949, both programs and data were stored and manipulated in the same way in computer memory.^[12]

Machine language

Machine code was the language of early programs, written in the instruction set of the particular machine, often in binary notation. Assembly languages were soon developed that let the programmer specify instruction in a text format (e.g., ADD X, TOTAL), with abbreviations for each operation code and meaningful names for specifying addresses. However, because an assembly language is little more than a different notation for a machine language, two machines with different instruction sets also have different assembly languages.

Wired control panel for an IBM 402 Accounting Machine. Wires connect pulse streams from the card reader to counters and other internal logic and ultimately to the printer.

Compiler languages

See also: Compiler

High-level languages made the process of developing a program simpler and more understandable, and less bound to the underlying hardware. The first compiler related tool, the A-0 System, was developed in 1952^[13] by Grace Hopper, who also coined the term 'compiler'.^[14][15] FORTRAN, the first widely used high-level language to have a functional implementation, came out in 1957,^[16] and many other languages were soon developed—in particular, COBOL aimed at commercial data processing, and Lisp for computer research.

These compiled languages allow the programmer to write programs in terms that are syntactically richer, and more capable of abstracting the code, making it easy to target varying machine instruction sets via compilation declarations and heuristics. Compilers harnessed the power of computers to make programming easier^[16] by allowing programmers to specify calculations by entering a formula using infix notation.

Source code entry

See also: Computer programming in the punched card era

Programs were mostly entered using punched cards or paper tape. By the late 1960s, data storage devices and computer terminals became inexpensive enough that programs could be created by typing directly into the computers. Text editors were also developed that allowed changes and corrections to be made much more easily than with punched cards.

Modern programming

Quality requirements

Main article: Software quality

Whatever the approach to development may be, the final program must satisfy some fundamental properties. The following properties are among the most important:^{[17] [18]}

• Reliability: how often the results of a program are correct. This depends on conceptual correctness of algorithms and minimization of programming mistakes, such as mistakes in resource management (e.g., buffer overflows and race conditions) and logic errors (such as division by zero or off-by-one errors).
• Robustness: how well a program anticipates problems due to errors (not bugs). This includes situations such as incorrect, inappropriate or corrupt data, unavailability of needed resources such as memory, operating system services, and network connections, user error, and unexpected power outages.
• Usability: the ergonomics of a program: the ease with which a person can use the program for its intended purpose or in some cases even unanticipated purposes. Such issues can make or break its success even regardless of other issues. This involves a wide range of textual, graphical, and sometimes hardware elements that improve the clarity, intuitiveness, cohesiveness and completeness of a program's user interface.
• Portability: the range of computer hardware and operating system platforms on which the source code of a program can be compiled/interpreted and run. This depends on differences in the programming facilities provided by the different platforms, including hardware and operating system resources, expected behavior of the hardware and operating system, and availability of platform-specific compilers (and sometimes libraries) for the language of the source code.
• Maintainability: the ease with which a program can be modified by its present or future developers in order to make improvements or to customize, fix bugs and security holes, or adapt it to new environments. Good practices^[19] during initial development make the difference in this regard. This quality may not be directly apparent to the end user but it can significantly affect the fate of a program over the long term.
• Efficiency/performance: Measure of system resources a program consumes (processor time, memory space, slow devices such as disks, network bandwidth and to some extent even user interaction): the less, the better. This also includes careful management of resources, for example cleaning up temporary files and eliminating memory leaks. This is often discussed under the shadow of a chosen programming language. Although the language certainly affects performance, even slower languages, such as Python, can execute programs instantly from a human perspective. Speed, resource usage, and performance are important for programs that bottleneck the system, but efficient use of programmer time is also important and is related to cost: more hardware may be cheaper.

Readability of source code

In computer programming, readability refers to the ease with which a human reader can comprehend the purpose, control flow, and operation of source code. It affects the aspects of quality above, including portability, usability and most importantly maintainability.

Readability is important because programmers spend the majority of their time reading, trying to understand, reusing and modifying existing source code, rather than writing new source code. Unreadable code often leads to bugs, inefficiencies, and duplicated code. A study found that a few simple readability transformations made code shorter and drastically reduced the time to understand it.^[20]

Following a consistent programming style often helps readability. However, readability is more than just programming style. Many factors, having little or nothing to do with the ability of the computer to efficiently compile and execute the code, contribute to readability.^[21] Some of these factors include:

• Different indent styles (whitespace)
• Comments
• Decomposition
• Naming conventions for objects (such as variables, classes, functions, procedures, etc.)

The presentation aspects of this (such as indents, line breaks, color highlighting, and so on) are often handled by the source code editor, but the content aspects reflect the programmer's talent and skills.

Various visual programming languages have also been developed with the intent to resolve readability concerns by adopting non-traditional approaches to code structure and display. Integrated development environments (IDEs) aim to integrate all such help. Techniques like Code refactoring can enhance readability.

Algorithmic complexity

The academic field and the engineering practice of computer programming are both largely concerned with discovering and implementing the most efficient algorithms for a given class of problems. For this purpose, algorithms are classified into orders using so-called Big O notation, which expresses resource use, such as execution time or memory consumption, in terms of the size of an input. Expert programmers are familiar with a variety of well-established algorithms and their respective complexities and use this knowledge to choose algorithms that are best suited to the circumstances.

Methodologies

The first step in most formal software development processes is requirements analysis, followed by testing to determine value modeling, implementation, and failure elimination (debugging). There exist a lot of different approaches for each of those tasks. One approach popular for requirements analysis is Use Case analysis. Many programmers use forms of Agile software development where the various stages of formal software development are more integrated together into short cycles that take a few weeks rather than years. There are many approaches to the Software development process.

Popular modeling techniques include Object-Oriented Analysis and Design (OOAD) and Model-Driven Architecture (MDA). The Unified Modeling Language (UML) is a notation used for both the OOAD and MDA.

A similar technique used for database design is Entity-Relationship Modeling (ER Modeling).

Implementation techniques include imperative languages (object-oriented or procedural), functional languages, and logic languages.

Measuring language usage

It is very difficult to determine what are the most popular modern programming languages. Methods of measuring programming language popularity include: counting the number of job advertisements that mention the language,^[22] the number of books sold and courses teaching the language (this overestimates the importance of newer languages), and estimates of the number of existing lines of code written in the language (this underestimates the number of users of business languages such as COBOL).

Some languages are very popular for particular kinds of applications, while some languages are regularly used to write many different kinds of applications. For example, COBOL is still strong in corporate data centers^[23] often on large mainframe computers, Fortran in engineering applications, scripting languages in Web development, and C in embedded software. Many applications use a mix of several languages in their construction and use. New languages are generally designed around the syntax of a prior language with new functionality added, (for example C++ adds object-orientation to C, and Java adds memory management and bytecode to C++, but as a result, loses efficiency and the ability for low-level manipulation).

Debugging

Main article: Debugging The first known actual bug causing a problem in a computer was a moth, trapped inside a Harvard mainframe, recorded in a log book entry dated September 9, 1947.^[24] "Bug" was already a common term for a software defect when this insect was found.

Debugging is a very important task in the software development process since having defects in a program can have significant consequences for its users. Some languages are more prone to some kinds of faults because their specification does not require compilers to perform as much checking as other languages. Use of a static code analysis tool can help detect some possible problems. Normally the first step in debugging is to attempt to reproduce the problem. This can be a non-trivial task, for example as with parallel processes or some unusual software bugs. Also, specific user environment and usage history can make it difficult to reproduce the problem.

After the bug is reproduced, the input of the program may need to be simplified to make it easier to debug. For example, when a bug in a compiler can make it crash when parsing some large source file, a simplification of the test case that results in only few lines from the original source file can be sufficient to reproduce the same crash. Trial-and-error/divide-and-conquer is needed: the programmer will try to remove some parts of the original test case and check if the problem still exists. When debugging the problem in a GUI, the programmer can try to skip some user interaction from the original problem description and check if remaining actions are sufficient for bugs to appear. Scripting and breakpointing is also part of this process.

Debugging is often done with IDEs. Standalone debuggers like GDB are also used, and these often provide less of a visual environment, usually using a command line. Some text editors such as Emacs allow GDB to be invoked through them, to provide a visual environment.

Programming languages  

Main articles: Programming language and List of programming languages

See also: Computer program § Languages

Different programming languages support different styles of programming (called programming paradigms). The choice of language used is subject to many considerations, such as company policy, suitability to task, availability of third-party packages, or individual preference. Ideally, the programming language best suited for the task at hand will be selected. Trade-offs from this ideal involve finding enough programmers who know the language to build a team, the availability of compilers for that language, and the efficiency with which programs written in a given language execute. Languages form an approximate spectrum from "low-level" to "high-level"; "low-level" languages are typically more machine-oriented and faster to execute, whereas "high-level" languages are more abstract and easier to use but execute less quickly. It is usually easier to code in "high-level" languages than in "low-level" ones. Programming languages are essential for software development. They are the building blocks for all software, from the simplest applications to the most sophisticated ones.

Allen Downey, in his book How To Think Like A Computer Scientist, writes:

The details look different in different languages, but a few basic instructions appear in just about every language:

• Input: Gather data from the keyboard, a file, or some other device.
• Output: Display data on the screen or send data to a file or other device.
• Arithmetic: Perform basic arithmetical operations like addition and multiplication.
• Conditional Execution: Check for certain conditions and execute the appropriate sequence of statements.
• Repetition: Perform some action repeatedly, usually with some variation.

Many computer languages provide a mechanism to call functions provided by shared libraries. Provided the functions in a library follow the appropriate run-time conventions (e.g., method of passing arguments), then these functions may be written in any other language.

Programmers

Main articles: Programmer and Software engineer

Computer programmers are those who write computer software. Their jobs usually involve:

• Prototyping
• Coding
• Debugging
• Documentation
• Integration
• Maintenance
• Requirements analysis
• Software architecture
• Software testing
• Specification

Although programming has been presented in the media as a somewhat mathematical subject, some research shows that good programmers have strong skills in natural human languages, and that learning to code is similar to learning a foreign language.^[25][26]

See also

• 

  Computer programming portal

Main article: Outline of computer programming

• ACCU
• Association for Computing Machinery
• Computer networking
• Hello world program
• Institution of Analysts and Programmers
• National Coding Week
• Object hierarchy
• Programming best practices
• System programming
• Computer programming in the punched card era
• The Art of Computer Programming
• Women in computing
• Timeline of women in computing

References

• Bebbington, Shaun (2014). "What is coding". Tumblr. Archived from the original on April 29, 2020. Retrieved March 3, 2014. 
• Bebbington, Shaun (2014). "What is programming". Tumblr. Archived from the original on April 29, 2020. Retrieved March 3, 2014. 
• Eliam, Eldad (2005). Reversing: Secrets of Reverse Engineering. Wiley. p. 3. ISBN 978-0-7645-7481-8. 
• Koetsier, Teun (2001). "On the prehistory of programmable machines: musical automata, looms, calculators". Mechanism and Machine Theory. Elsevier. 36 (5): 589–603. doi:10.1016/S0094-114X(01)00005-2. 
• Kapur, Ajay; Carnegie, Dale; Murphy, Jim; Long, Jason (2017). "Loudspeakers Optional: A history of non-loudspeaker-based electroacoustic music". Organised Sound. Cambridge University Press. 22 (2): 195–205. doi:10.1017/S1355771817000103. ISSN 1355-7718. 
• Fowler, Charles B. (October 1967). "The Museum of Music: A History of Mechanical Instruments". Music Educators Journal. 54 (2): 45–49. doi:10.2307/3391092. JSTOR 3391092. S2CID 190524140. 
• Noel Sharkey (2007), A 13th Century Programmable Robot, University of Sheffield
• Dooley, John F. (2013). A Brief History of Cryptology and Cryptographic Algorithms. Springer Science & Business Media. pp. 12–3. ISBN 9783319016283. 
• Fuegi, J.; Francis, J. (2003). "Lovelace & Babbage and the Creation of the 1843 'notes' ". IEEE Annals of the History of Computing. 25 (4): 16. doi:10.1109/MAHC.2003.1253887. 
• Rojas, R. (2023). "The First Computer Program". arXiv:2303.13740 [cs.GL]. 
• da Cruz, Frank (March 10, 2020). "Columbia University Computing History – Herman Hollerith". Columbia University. Columbia.edu. Archived from the original on April 29, 2020. Retrieved April 25, 2010. 
• "Memory & Storage | Timeline of Computer History | Computer History Museum". www.computerhistory.org. Archived from the original on May 27, 2021. Retrieved June 3, 2021. 
• Ridgway, Richard (1952). "Compiling routines". Proceedings of the 1952 ACM national meeting (Toronto) on - ACM '52. ACM '52. pp. 1–5. doi:10.1145/800259.808980. ISBN 9781450379250. S2CID 14878552. 
• Maurice V. Wilkes. 1968. Computers Then and Now. Journal of the Association for Computing Machinery, 15(1):1–7, January. p. 3 (a comment in brackets added by editor), "(I do not think that the term compiler was then [1953] in general use, although it had in fact been introduced by Grace Hopper.)"
• [1] The World's First COBOL Compilers Archived 13 October 2011 at the Wayback Machine
• Bergstein, Brian (March 20, 2007). "Fortran creator John Backus dies". NBC News. Archived from the original on April 29, 2020. Retrieved April 25, 2010. 
• "NIST To Develop Cloud Roadmap". InformationWeek. November 5, 2010. Computing initiative seeks to remove barriers to cloud adoption in security, interoperability, portability and reliability.
• "What is it based on". Computerworld. April 9, 1984. p. 13. Is it based on ... Reliability Portability. Compatibility
• "Programming 101: Tips to become a good programmer - Wisdom Geek". Wisdom Geek. May 19, 2016. Archived from the original on May 23, 2016. Retrieved May 23, 2016.
• Elshoff, James L.; Marcotty, Michael (1982). "Improving computer program readability to aid modification". Communications of the ACM. 25 (8): 512–521. doi:10.1145/358589.358596. S2CID 30026641.
• Multiple (wiki). "Readability". Docforge. Archived from the original on April 29, 2020. Retrieved January 30, 2010.
• Enticknap, Nicholas (September 11, 2007). "SSL/Computer Weekly IT salary survey: finance boom drives IT job growth". Archived from the original on October 26, 2011. Retrieved June 24, 2009.
• Mitchell, Robert (May 21, 2012). "The Cobol Brain Drain". Computer World. Archived from the original on February 12, 2019. Retrieved May 9, 2015.
• "Photograph courtesy Naval Surface Warfare Center, Dahlgren, Virginia, from National Geographic Sept. 1947". July 15, 2020. Archived from the original on November 13, 2020. Retrieved November 10, 2020.
• Prat, Chantel S.; Madhyastha, Tara M.; Mottarella, Malayka J.; Kuo, Chu-Hsuan (March 2, 2020). "Relating Natural Language Aptitude to Individual Differences in Learning Programming Languages". Scientific Reports. 10 (1): 3817. Bibcode:2020NatSR..10.3817P. doi:10.1038/s41598-020-60661-8. ISSN 2045-2322. PMC 7051953. PMID 32123206.

1. "To the brain, reading computer code is not the same as reading language". MIT News | Massachusetts Institute of Technology. December 15, 2020. Retrieved July 29, 2023.

Sources

• Ceruzzi, Paul E. (1998). History of Computing. Cambridge, Massachusetts: MIT Press. ISBN 9780262032551 – via EBSCOhost.
• Evans, Claire L. (2018). Broad Band: The Untold Story of the Women Who Made the Internet. New York: Portfolio/Penguin. ISBN 9780735211759.
• Gürer, Denise (1995). "Pioneering Women in Computer Science" (PDF). Communications of the ACM. 38 (1): 45–54. doi:10.1145/204865.204875. S2CID 6626310. Archived (PDF) from the original on October 9, 2022.
• Smith, Erika E. (2013). "Recognizing a Collective Inheritance through the History of Women in Computing". CLCWeb: Comparative Literature & Culture: A WWWeb Journal. 15 (1): 1–9 – via EBSCOhost.

Further reading

• A.K. Hartmann, Practical Guide to Computer Simulations, Singapore: World Scientific (2009)
• A. Hunt, D. Thomas, and W. Cunningham, The Pragmatic Programmer. From Journeyman to Master, Amsterdam: Addison-Wesley Longman (1999)
• Brian W. Kernighan, The Practice of Programming, Pearson (1999)
• Weinberg, Gerald M., The Psychology of Computer Programming, New York: Van Nostrand Reinhold (1971)
• Edsger W. Dijkstra, A Discipline of Programming, Prentice-Hall (1976)
• O.-J. Dahl, E.W.Dijkstra, C.A.R. Hoare, Structured Programming, Academic Press (1972)
• David Gries, The Science of Programming, Springer-Verlag (1981)

External links

Library resources about Computer programming
Online books Resources in your library Resources in other libraries
v t e Computer science
v t e Software engineering
v t e Software quality
Authority control databases

Wikibooks has a book on the topic of: Computer Programming

Wikibooks has a book on the topic of: Windows Programming

Wikiversity has learning resources about Computer Programming

• Media related to Computer programming at Wikimedia Commons
• Quotations related to Programming at Wikiquote
• Software engineering at Curlie

---

Links  

https://en.wikipedia.org/wiki/Category:Computer_programming

Subcategories``ёёё]]]

`0-9

A

• Algorithms

► Anti-patterns (72 P)

B

► Computer programming books (3 C, 29 P)

C

► Code refactoring (9 P)

► Computer programming folklore (27 P)

• Concurrent Computing

► Programming constructs (5 C, 67 P)

D

► Data structures (19 C, 20 P)

► Debugging (5 C, 58 P)

`E`F

G

► Programming games (34 P)

`H`I`J`K

L

► Computer libraries (36 C, 77 P)

► Live coding (1 C, 17 P)

`M`N`O

`P

► Program derivation (2 P)

• Programs
• Software Optimisation

► Computer programmers (9 C, 185 P)

► Programming (empty)

► Programming contests (3 C, 57 P)

► Programming idioms (3 C, 10 P)

• Programming Languages

► Programming paradigms (11 C, 102 P)

► Programming principles (33 P)

`Q

`R

• Programming Resources

`S

► Self-hosting software (14 P)

► Software design patterns (3 C, 145 P)

► Source code (3 C, 69 P)

► Source code generation (1 C, 3 P)

T

► Computer programming tools (38 C, 102 P)

`U

V

► Visual programming (1 C, 1 P)

`W`X`Y`Z

Σ

► Computer programming stubs (1 C, 282 P)

Index

```[[[ёёё

Computer programming

Outline of computer programming

*

List of programming languages

A

AirPair

Algoid (programming language)

Algorave

Application architect

Asynchrony (computer programming)

B

Bayesian Program Synthesis

Berger Series

Best coding practices

Binary repository manager

C

Characteristic based product configurator

Cheat sheet

Code Club

Code Words

Codecademy

CodeHS

CoderDojo

Compile and go system

Computer network programming

Computer program

Computer programming in the punched card era

Conditional operator

Creative coding

D

Daily build

Dangling else

Derivative code

Design-Oriented Programming

Deutsch limit

Directive (programming)

E

End-user development

Energy modeling

Engineering Code Snippets Project

EPANET

Event (computing)

Event cascade

Example-Centric Programming

Existence detection

Explicit parallelism

F

Feature toggle

Flowchart

Floyd's triangle

Fluxus (programming environment)

Free variables and bound variables

FreeCodeCamp

Fully qualified name

Function prototype

G

Garbage (computer science)

Gateway (computer program)

Geocoder (Ruby)

Gerrit (software)

Ghana Code Club

Glue code

Gnits standards

Grist (computing)

Grok Learning

H

Hacker

Hand coding

Happy path

I

Identity transform

Integrated Water Flow Model (IWFM)

Invariant (computer science)

Ixi lang

J

User:JJacobMollan/sandbox

K

Kata (programming)

L

LaunchCode

LearnStreet

Lighthouse Labs

Lightweight programming language

List of program transformation systems

Live coding

Locks-and-keys

M

Macro instruction

Makers Academy

MobileNotifier

N

Nassi–Shneiderman diagram

National Computer Rank Examination

Natural language programming

Nested quotation

Neutral build

Nondeterministic programming

O

Object-based language

Observer effect (information technology)

OLE DB for OLAP

OLE DB provider

OMNeT++

One Month

One-liner program

Opaque pointer

Opaque predicate

Open Agent Architecture

Open collaboration

Open Database Connectivity

Open energy system models

P

Persistence (computer science)

Phase distinction

Pointer aliasing

Polyglot (computing)

Polyglot persistence

Predeclared

Privatization (computer programming)

Procedural design

Proggy programming fonts

Program comprehension

Program-specific information

Programmer's Stone

Programming interview

Programming model

Proto.io

Psychology of programming

R

Recursive transcompiling

Refinement (computing)

Reverse architecture

Rewrite (programming)

S

Scaffold (programming)

Segment (company)

Self-documenting code

Self-hosting

Self-relocation

Services computing

Side effect (computer science)

Sigar (software)

Signature program

Signed overpunch

Skeleton (computer programming)

Softcoding

Software build

Software craftsmanship

Sonic Pi

Standalone program

Stanza (computing)

Stripped binary

The Structure and Interpretation of the Computer Science Curriculum

SwitchUp

System programming

System time

T

Taint checking

Third-party software component

TidalCycles

Timeout (computing)

Tombstone diagram

Toy program

Transient (computer programming)

Treehouse (company)

Truth bit

U

Unspecified behavior

V

Variadic template

W

Winner-take-all in action selection

Workspace

Y

Yoda conditions

Young Rewired State

Ρ

Portal:Computer programming

Pages in Other Languages

Categories:

• Software Development
• Software Engineering
• Computers