by

Wikipedia Bot (@wikibot, 0)

Philosophy of computer science

Table of contents
- Software development philosophies Philosophy of computer science

Software development philosophies

 0  0 

Programming principles

 0  0 

Abstraction principle (computer programming)

 0  0 

Booch method

 0  0 

Code reuse

 0  0 

Cohesion (computer science)

 0  0 

Command–query separation

 0  0 

Composition over inheritance

 0  0 

Coupling (computer programming)

 0  0 

Defensive programming

 0  0 

Dependency inversion principle

 0  0 

Deutsch limit

 0  0 

Discoverability

 0  0 

Don't repeat yourself

 1  0 

Encapsulation (computer programming)

 0  0 

Fail-fast

 0  0 

GRASP (object-oriented design)

 0  0 

Information hiding

 0  0 

Interface segregation principle

 0  0 

Inversion of control

 0  0 

Law of Demeter

 0  0 

Loose coupling

 0  0 

Ninety–ninety rule

 0  0 

Offensive programming

 0  0 

Principle of least astonishment

 0  0 

Pristine Sources

 0  0 

Rule of three (computer programming)

 0  0 

SOLID

 1  0 

Separation of mechanism and policy

 0  0 

Single-responsibility principle

 0  0 

The Power of 10: Rules for Developing Safety-Critical Code

 0  0 

Uniform access principle

 0  0 

Zen of Python

 1  0 

Zero one infinity rule

 0  0 

Acceptance test-driven development

 0  0 

After the Software Wars

 0  0 

Agile software development

 0  0 

Dynamic systems development method

 0  0 

Acceptance testing

 0  0 

Adaptation (computer science)

 0  0 

Adaptive software development

 0  0 

Agile Automation

 0  0 

Agile application

 0  0 

Agile architecture

 0  0 

Agile contracts

 0  0 

Agile management

 0  0 

Agile modeling

 0  0 

Agile testing

 0  0 

Agile unified process

 0  0 

Agilo for Trac

 0  0 

Alistair Cockburn

 0  0 

Analysis paralysis

 0  0 

Andy Hunt (author)

 0  0 

Ayotle

 0  0 

Azure DevOps Server

 0  0 

Build light indicator

 0  0 

Burndown chart

 0  0 

Comparison of scrum software

 0  0 

Continuous configuration automation

 0  0 

Continuous integration

 1  0 

DBmaestro

 0  0 

Design sprint

 0  0 

DevOps

 0  0 

Disciplined agile delivery

 0  0 

Distributed agile software development

 0  0 

Exit criteria

 0  0 

Feature-driven development

 0  0 

Flyway (software)

 0  0 

ICONIX

 0  0 

Infrastructure as code

 0  0 

JHipster

 0  0 

Jeff Sutherland

 0  0 

Jim Highsmith

 0  0 

Ken Schwaber

 0  0 

Kent Beck

 0  0 

Liquibase

 0  0 

Martin Fowler (software engineer)

 0  0 

Mike Beedle

 0  0 

P-Modeling Framework

 0  0 

PTC Integrity

 0  0 

Pair programming

 1  0 

Presenter first (software approach)

 0  0 

Product backlog

 0  0 

RATF

 0  0 

Robert C. Martin

 0  0 

Ron Jeffries

 0  0 

SMART Process Acceleration Development Environment

 0  0 

Scrumban

 0  0 

Scrumedge

 0  0 

Service design sprint

 0  0 

Spike (software development)

 0  0 

Stand-up meeting

 0  0 

Thoughtworks

 0  0 

Timeboxing

 0  0 

User story

 0  0 

Validated learning

 0  0 

Velocity (software development)

 0  0 

Ward Cunningham

 0  0 

Behavior-driven development

 0  0 

Best practice

 0  0 

 Articles were limited to the first 100 out of 161 total. Click here to view all children of Philosophy of computer science.

 Ancestors (3)

 View article source

 Discussion (0)

+ New discussion

There are no discussions about this article yet.

 Articles by others on the same topic (0)

There are currently no matching articles.

  See all articles in the same topic + Create my own version