That's super cool. Love the visualizations!

That is a very interesting idea my friend.

Talon + Cursorless.

People have built the tools you're talking about. They're Talon and Cursorless.

I think you'd be shocked if you saw how productive some people in the Talon community are. Be sure to join the community Slack.

Same. Have to disagree though. I've been reintroducing a keyboard here and there, and whenever I have to do something in the VSCode editor, I get frustrated with the speed and end up going back to Cursorless.

I think it's a lot faster than keyboard / mouse, mostly because of how little moving of the cursor you have to do.

Could be I was slow to begin with, not super efficient with vim or emacs.

Also, "editing" is the fastest part for me, due to "bring" and "change". So little movement.

Agreed. I think overtime we'll just get more abstracted away from it. GKE Autopilot, for example.

I think you still have to understand the lego block in your hand though, so you can combine it well with the other parts of your system.

I could be wrong here, but I think `helm lint` just checks that the chart is formed correctly — Go templating and all.

I don't think it validates the Kubernetes resources.

Here's an example:

$ helm create foo

$ cd foo

Then change "apiVersion" in deployment.yaml to "apiVersion: nonsense"

In the linting, I got

$ helm lint ==> Linting . [INFO] Chart.yaml: icon is recommended

1 chart(s) linted, 0 chart(s) failed

$ helm template . | kubeval -

ERR - foo/templates/deployment.yaml: Failed initializing schema https://kubernetesjsonschema.dev/master-standalone/deploymen...: Could not read schema from HTTP, response status is 404 Not Found

THANK YOU

Move fast and break things guys

Break other people's things it seems.

And that's exactly the problem. We give them our things

Good luck! You’ll be surprised where you are in a few years

Good question! Each iteration of the model occurs for one unit of time. Because of this, we can directly compare distance and velocity.

Like if velocity was meters per second, and distance was meters, since the velocity update occurs for one second, we can compare the two.

I'll clarify in the post, this confused me too when I first started reading about the model.

If you adjust the velocity to v-1 it would be an incremental update, which seems natural. But if you update the velocity to d-1 (as stated) I can imagine this could be a jump and even could result in negative velocity for d=0.