Topic: Computing (Page 45)
You are looking at all articles with the topic "Computing". We found 481 matches.
Hint:
To view all topics, click here. Too see the most popular topics, click here instead.
π Cargo cult programming
Cargo cult programming is a style of computer programming characterized by the ritual inclusion of code or program structures that serve no real purpose. Cargo cult programming is symptomatic of a programmer not understanding either a bug they were attempting to solve or the apparent solution (compare shotgun debugging, deep magic). The term cargo cult programmer may apply when an unskilled or novice computer programmer (or one inexperienced with the problem at hand) copies some program code from one place to another with little understanding of how it works or whether it is required.
Cargo cult programming can also refer to the practice of applying a design pattern or coding style blindly without understanding the reasons behind that design principle. Examples being adding unnecessary comments to self-explanatory code, overzealous adherence to the conventions of a programming paradigm, or adding deletion code for objects that garbage collection automatically collect.
Obsessive and redundant checks for null values or testing whether a collection is empty before iterating its values may be a sign of cargo cult programming. Such obsessive checks make the code less readable, and often prevent the output of proper error messages, obscuring the real cause of a misbehaving program.
Discussed on
- "Cargo cult programming" | 2015-02-16 | 10 Upvotes 3 Comments
π FILE_ID.DIZ
FILE_ID.DIZ is a plain text file containing a brief content description of the archive in which it is included. It was originally used in archives distributed through bulletin board systems (BBS), and still in the warez scene.
Bulletin boards commonly accept uploaded files from their users. The BBS software would prompt the user to supply a description for the uploaded file, but these descriptions were often less than useful. BBS system operators spent many hours going over the upload descriptions correcting and editing the descriptions. The FILE_ID.DIZ inclusion in archives was designed to address this problem.
FILE_ID stands for "file identification". DIZ stands for Description In Zipfile.
Clark Development and the Association of Shareware Professionals supported the idea of this becoming a standard for file descriptions. Clark rewrote the PCBDescribe program and included it with their PCBoard BBS software. The ASP urged their members to use this description file format in their distributions. Michael Leavitt, an employee of Clark Development, released the file specification and his PCBDescribe program source code to the public domain and urged other BBS software companies to support the DIZ file.
SysOps could add a common third-party script written in PPL, called "DIZ/2-PCB" that would process, rewrite, verify, and format DIZ files from archives as they were uploaded to a BBS. The software would extract the archive, examine the contents, compile a report, import the DIZ description file and then format it according to your liking. During this time, it was usual practice to add additional lines to the description, such as ads exclaiming the source of the uploaded BBS.
Traditionally, a FILE_ID.DIZ should be "up to 10 lines of text, each line being no more than 45 characters long." according to the specification v1.9.
The concept of DIZ files was to allow a concise description of uploaded files to be automatically applied. Advertisements and "high ASCII" artwork were specifically prohibited.
Even since the decline of the dial-up bulletin board system, FILE_ID.DIZ files are still utilized by the warez scene in their releases of unlicensed software. They are commonly bundled as part of the complete packaging by self-described pirate groups, and indicate the number of disks, and other basic information. Along with the NFO file, it is essential to the release. Especially in terms of unlicensed software ("warez"), it was common for each file in a sequential compressed archive (an archive intentionally split into multiple parts at creation so the parts can then be individually downloaded by slower connections like dial-up. Example: .rar, .r00, .r01, .r02, etc.), to contain this file. This probably contributed to its extended popularity after the decline of the bulletin board system in the late 1990s and early 2000s until now, since even casual consumers of unlicensed software would have stumbled upon it due to its abundance.
Discussed on
- "FILE_ID.DIZ" | 2015-06-27 | 10 Upvotes 3 Comments
π Fundamental theorem of software engineering
The fundamental theorem of software engineering (FTSE) is a term originated by Andrew Koenig to describe a remark by Butler Lampson attributed to the late David J. Wheeler:
"We can solve any problem by introducing an extra level of indirection."
The theorem does not describe an actual theorem that can be proven; rather, it is a general principle for managing complexity through abstraction.
The theorem is often expanded by the humorous clause "β¦except for the problem of too many levels of indirection," referring to the fact that too many abstractions may create intrinsic complexity issues of their own. For example, the use of protocol layering in computer networks, which today is ubiquitous, has been criticized in ways that are typical of more general disadvantages of abstraction. Here, the adding of extra levels of indirection may cause higher layers to duplicate the functionality of lower layers, leading to inefficiency, and functionality at one layer may need data present only at another layer, which fundamentally violates the goal of separation into different layers.
π PAQ
PAQ is a series of lossless data compression archivers that have gone through collaborative development to top rankings on several benchmarks measuring compression ratio (although at the expense of speed and memory usage). Specialized versions of PAQ have won the Hutter Prize and the Calgary Challenge. PAQ is free software distributed under the GNU General Public License.
Discussed on
- "PAQ" | 2014-05-30 | 12 Upvotes 1 Comments
π Pick Operating System
The Pick operating system (often called just "the Pick system" or simply "Pick") is a demand-paged, multiuser, virtual memory, time-sharing computer operating system based around a unique MultiValue database. Pick is used primarily for business data processing. It is named after one of its developers, Dick Pick.
The term "Pick system" has also come to be used as the general name of all operating environments which employ this multivalued database and have some implementation of Pick/BASIC and ENGLISH/Access queries. Although Pick started on a variety of minicomputers, the system and its various implementations eventually spread to a large assortment of microcomputers, personal computers and mainframe computers.
Discussed on
- "Pick operating system" | 2017-03-13 | 11 Upvotes 2 Comments
π Quine
A quine is a computer program which takes no input and produces a copy of its own source code as its only output. The standard terms for these programs in the computability theory and computer science literature are "self-replicating programs", "self-reproducing programs", and "self-copying programs".
A quine is a fixed point of an execution environment, when the execution environment is viewed as a function transforming programs into their outputs. Quines are possible in any Turing complete programming language, as a direct consequence of Kleene's recursion theorem. For amusement, programmers sometimes attempt to develop the shortest possible quine in any given programming language.
The name "quine" was coined by Douglas Hofstadter, in his popular science book GΓΆdel, Escher, Bach, in honor of philosopher Willard Van Orman Quine (1908β2000), who made an extensive study of indirect self-reference, and in particular for the following paradox-producing expression, known as Quine's paradox:
"Yields falsehood when preceded by its quotation" yields falsehood when preceded by its quotation.
Discussed on
- "Quine (computing)" | 2011-06-11 | 10 Upvotes 3 Comments
π Personal Knowledge Management
Personal knowledge management (PKM) is a process of collecting information that a person uses to gather, classify, store, search, retrieve and share knowledge in their daily activities (Grundspenkis 2007) and the way in which these processes support work activities (Wright 2005). It is a response to the idea that knowledge workers need to be responsible for their own growth and learning (Smedley 2009). It is a bottom-up approach to knowledge management (KM) (Pollard 2008).
π Triple Fault
On the x86 computer architecture, a triple fault is a special kind of exception generated by the CPU when an exception occurs while the CPU is trying to invoke the double fault exception handler, which itself handles exceptions occurring while trying to invoke a regular exception handler.
x86 processors beginning with the 80286 will cause a shutdown cycle to occur when a triple fault is encountered. This typically causes the motherboard hardware to initiate a CPU reset, which, in turn, causes the whole computer to reboot.
Discussed on
- "Triple Fault" | 2023-01-11 | 12 Upvotes 1 Comments
π Confused Deputy Problem
In information security, a confused deputy is a computer program that is tricked by another program (with fewer privileges or less rights) into misusing its authority on the system. It is a specific type of privilege escalation. The confused deputy problem is often cited as an example of why capability-based security is important.
Capability systems protect against the confused deputy problem, whereas access-control listβbased systems do not.
Discussed on
- "Confused Deputy Problem" | 2023-10-18 | 11 Upvotes 2 Comments
π M-DISC: The storage medium that lasts 1000 years
M-DISC (Millennial Disc) is a write-once optical disc technology introduced in 2009 by Millenniata, Inc. and available as DVD and Blu-ray discs.
Discussed on
- "M-DISC: The storage medium that lasts 1000 years" | 2024-09-18 | 11 Upvotes 2 Comments