Software Development Environment
A Software Development Environment is a computing environment that helps a software developer to solve a software programming task.
- Context:
- It can include a Source Code Editor.
- It can include a Code Debugger.
- It can range from being a Local Development Environment to being a Shared Development Environment.
- It can range from being a Integrated Development Environment to being a Non-Integrated Development Environment.
- …
- Counter-Example(s):
- Counter-Example(s):
- See: Compiler, Interpreter (Computing), Continuous Integration, Revision Control, Sandbox (Software Development).
References
2020
- (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/Deployment_environment#Development Retrieved:2020-5-1.
- The development environment (dev) is the environment in which changes to software are developed, most simply an individual developer's workstation. This differs from the ultimate target environment in various ways – the target may not be a desktop computer (it may be a smartphone, embedded system, headless machine in a data center, etc.), and even if otherwise similar, the developer's environment will include development tools like a compiler, integrated development environment, different or additional versions of libraries and support software, etc., which are not present in a user's environment.
In the context of revision control, particularly with multiple developers, finer distinctions are drawn: a developer has a working copy of source code on their machine, and changes are submitted to the repository, being committed either to the trunk or a branch, depending on development methodology. The environment on an individual workstation, in which changes are worked on and tried out, may be referred to as the local environment or a sandbox. Building the repository's copy of the source code in a clean environment is a separate step, part of integration (integrating disparate changes), and this environment may be called the integration environment or the development environment; in continuous integration this is done frequently, as often as for every revision. The source code level concept of "committing a change to the repository", followed by building the trunk or branch, corresponds to pushing to release from local (individual developer's environment) to integration (clean build); a bad release at this step means a change broke the build, and rolling back the release corresponds to either rolling back all changes from that point onward, or undoing just the breaking change, if possible.
- The development environment (dev) is the environment in which changes to software are developed, most simply an individual developer's workstation. This differs from the ultimate target environment in various ways – the target may not be a desktop computer (it may be a smartphone, embedded system, headless machine in a data center, etc.), and even if otherwise similar, the developer's environment will include development tools like a compiler, integrated development environment, different or additional versions of libraries and support software, etc., which are not present in a user's environment.
2021
- https://zurigroup.com/blog-best-practices-development-environments/
- QUOTE: ... 4 Best Practices for Development Environments (shared by a developer)
- Establish a local development environment.
- Operate a single machine to both run the application and develop on
- Adopt source control
- Create a safe space for testing within the dev environment
- QUOTE: ... 4 Best Practices for Development Environments (shared by a developer)