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: Low-code Ops and the art of abstraction #1205

Merged
merged 1 commit into from
Apr 15, 2021
Merged

Essay Proposal: Low-code Ops and the art of abstraction #1205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
24 changes: 24 additions & 0 deletions contributions/essay/isakha-lidfeldt/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
# Essay Proposal: "Low-code Ops and the art of abstraction"

## Members
Isak Hassbring (isakha@kth.se)
Github: [hassbring](https://github.com/hassbring)

Gustaf Lidfeldt (lidfeldt@kth.se)
Github: [glidfeldt](https://github.com/glidfeldt)

## Topic
We would like to write an essay on the *no-code / low-code* abstraction practice and its rapid evolvement. We will critically review its emergence in devops and talk about about devops from the bigger perspective - abstraction.

## Introduction

DevOps in general could be seen as a set of practices serving as abstraction layers that aims to let more people be more effective, by building an interface around difficulties - hence abstracting them away. The same goes for many other engineering fields, e.g. Computer Engineering is an abstraction on Electical engineering and programming languages are actually abstractions (nowdays multiple layers) on machine code. Among programmers, a one-liner is often considered superior compared to multiline programs (given equal task and performance). Why? Because we love the art of simplicity and abstraction.

In the no-code space, the computer program Excel is typically seen as the birth of the practice (in ~1985), as it lets "the average Joe" compute calculations without programming skills. Now, a lot has happened since then. Today, platforms such as Peltarion.ai even go beyond the once beloved one-liners and let creators (people building applications) set up, train, test and deploy cutting edge deep learning techniques without writing code. Bubble.io lets you write *interactive* front ends, also as a no-code practice. Shuttleops.io offers a no-code continuous delivery platform that literarly lets you *draw* your operations infrastructure / architecture and deploy.

We all know what the emergence of the no-code platform wordpress.org meant for web developers as it completely reshaped their industry.

So, what does this mean for the devloper teams as well as the operations? Is this the beginning of the end of devops as we know it?

We will explain *why* this matters for a devops engineer (or any engnineer in general!) and discuss the practical implications of low-code today and in the future.