Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Essay proposal #1630

Merged
merged 2 commits into from
Apr 1, 2022
Merged

Essay proposal #1630

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
19daba1
Essay proposal
persman96 Mar 30, 2022
0f502a7
Merge branch 'KTH:2022' into essay
persman96 Apr 1, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
23 changes: 23 additions & 0 deletions contributions/essay/persman/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# Assignment Proposal

## Title

Continuous deployment - How does feature toggle fit in?

## Names and KTH ID

- Pontus Persman (persman@kth.se)

## Deadline

Task 1

## Category

Essay

## Description

Feature toggles allow for deployment using conditional logic and environmental variables which determines whether certain code should be ran. Feature toggles may help to facilitate rapid releases as well as flexible control over which features to deploy. However, it may also introduce severe drawbacks, such as dead code, code complexity and system failure.

My goal for the essay is to present what role feature toggles has in regards to continuous deployment and its strengths and drawbacks.