I posted to our internal chat channel #continuous-learning this post
by Itamar Turner-Trauring:
So I have a Take:
Imagine if LLM coding assistants had come out when programming required explicit manual memory management.
I posted to our internal chat channel #continuous-learning this post
by Itamar Turner-Trauring:
So I have a Take:
Imagine if LLM coding assistants had come out when programming required explicit manual memory management.
| [ | |
| // // Evaluate | |
| {"keys": ["ctrl+enter"], | |
| "command": "clojure_sublimed_eval", | |
| "context": [{"key": "selector", "operator": "equal", "operand": "source.clojure"}]}, | |
| // // Evaluate Buffer | |
| {"keys": ["ctrl+b"], | |
| "command": "clojure_sublimed_eval_buffer", | |
| "context": [{"key": "selector", "operator": "equal", "operand": "source.clojure"}]}, |
| #!/usr/bin/env python3 | |
| import fileinput | |
| def cleanup(line: str) -> str: | |
| return line.replace(" ", " ").replace('xml:space="preserve"', "") | |
| def __main__(): |
| curl -v https://gitpod.com/ | |
| * Trying 45.79.154.83... | |
| * TCP_NODELAY set | |
| * Connected to gitpod.com (45.79.154.83) port 443 (#0) | |
| * ALPN, offering h2 | |
| * ALPN, offering http/1.1 | |
| * successfully set certificate verify locations: | |
| * CAfile: /etc/ssl/cert.pem | |
| CApath: none | |
| * TLSv1.2 (OUT), TLS handshake, Client hello (1): |
| # We could use a smaller/simpler image to download the package, but this is the same base image as | |
| # our ultimate image that we’re building, so we get to reuse the same cached layers. | |
| FROM debian:buster-slim AS builder | |
| WORKDIR /tmp/install | |
| RUN apt-get update && apt-get install -yq wget | |
| RUN wget --quiet \ | |
| -O confluent-community.tar.gz \ |
| # An example of a GitHub Actions job that builds a Docker container image and then pushes | |
| # it to to the GitHub Packages container registry associated with the same repo, using | |
| # regular `docker` commands. | |
| # Change these to whatever you want, of course. For example, you might want to only run this workflow for | |
| # PRs. Personally I like to check the build on every push. That said, it’s probably not necessary to publish | |
| # an artifact (container image) for every single push; I’m personally planning to add an `if` to the push | |
| # step that skips the `docker push` if the GitHub event is `push`. | |
| name: Push | |
| on: |
As of May 2021