Thread by @copyconstruct

What are the biggest pain points you believe tooling can address in the next decade (2020-2029)?

I’ll go first:

- CI/CD. Jenkins is currently the CI gold standard and it’s a very low bar.
- Easier abstractions and paradigms for building infra. Kube is too low level + complex.

What I mean by “paradigms” is basically this:

Right now the compute spectrum is a bit of an embarrassment of immature riches; as an industry we need to innovate, experiment and educate more on how to pick the right compute option for the wide variety of workloads we already run.

How can FaaS be leveraged better and applied to existing problems to get better outcome?

https://twitter.com/copyconstruct/status/1205230675541905408?s=21

Can traditional “PaaS” development be rethought from the ground up, given the low level primitives we now have (bare metal servers in the cloud, VMs, FaaS etc).

How awesome would it be if I as a developer didn’t have to fuck around with kubectl, terraform, cloud tooling etc.

If instead, the PaaS would let me choose where to run my app based on *app leve concerns* like latency, CPU usage, RPS, traffic patterns (bursty vs sustained) etc.

And transparently run my workload wherever it’s best suited to be run - be it in “containers” or in VMs or compiled down as a wasm instance and run on the “edge” in CDN POPs or by invoking a lambda function.

With all the debuggability and observability baked in out of the box.