Roger Peppe

Campaigning against unnecessary indirection everywhere.
Hacker at

[Roger Peppe @rogpeppe]

@rawkode I think it's a hard problem! Gerrit "solves" it by using an explicit Change-Id footer and tying the unit of change (CL) to that rather than to a branch. Ignoring the UI itself, I'm not sure what might work better.

[Roger Peppe @rogpeppe]

@rawkode I'd find that inconvenient. I almost always want to see what's changed since my last review, so I can see if the changes reflected my expectations, but if there's no relationship between the new review and its previous iteration, it's hard to see how that would be possible.

[Roger Peppe @rogpeppe]

@rawkode ... without any relationship to the original commit that was reviewed?

[Roger Peppe @rogpeppe]

@njcw I always thought an infinity mirror was just two mirrors either side of a room reflecting one another, but this doesn't seem quite that. Maybe a bit of base explanation for unfamiliar people might be helpful?

[Roger Peppe @rogpeppe]

@ibuildthecloud I'd say Go is agnostic about it, and channels are just one tool in the box. HTTP handling, for example, is conventionally push-style (https://t.co/7br0agwUV0), but channels are used under the hood to implement the server (https://t.co/KJnykWxZvN)

[Roger Peppe @rogpeppe]

@ibuildthecloud Out of interest, what don't you like about them? Been using them for years and they seem pretty hassle free and useful. I like sharing my WIP branches between different contexts.

[Roger Peppe @rogpeppe]

I'm here! Come by for a chat if you're too.

[CUE @cue_lang]

We're at KubeCon Amsterdam.

If you want to find out how to prevent misconfigurations ending up in production, come by (Hall 5, 1163).

Or join us for a chat about configuration, preventable outages, schemas, or our configuration control plane.

@CloudNativeFdn

[Roger Peppe @rogpeppe]

@aramh In your gist, the output from the command line `dune exec _build/default/bin/main.exe reduce /tmp/a.cue` seems to define `y` without respect to `x`, thus losing that constraint. But again, I'm probably missing something.

[Roger Peppe @rogpeppe]

@aramh ISTM that losing the constraint between y and x isn't quite valid there, because that reduced result will unify with `{x: z: 1, y: z: 2}` which the original would not. Am I missing something?

[Roger Peppe @rogpeppe]

@aramh Wouldn't it be more accurate to model it as incompleteError(string) ? That is, it's definitely an error currently, pending x being made more specific, because operators don't work on noncrete values, but we know that the result must be string.

[Roger Peppe @rogpeppe]

@davidcrawshaw Gotta improve Shelley voice input first!

[Roger Peppe @rogpeppe]

@ibuildthecloud Or memory! (I recently saw Claude using 77GB VM, 500MB RSS, more than Chrome with 70 tabs; not even a memory leak: restarting made no difference)

[Roger Peppe @rogpeppe]

@aramh If you're actually vibe coding, you're not seeing the code at all, so I fail to see why a vibe coder would care about the language being used beyond "is it effective with my LLM?"

[Roger Peppe @rogpeppe]

@martinfowler FWIW I enjoyed this blog post that focuses on some more quantitative aspects of context: https://t.co/rmjSiwyniv

[CUE @cue_lang]

Want to talk about how to end configuration chaos?

We will be at @fosdem (Brussels, Jan 31–Feb 1) and @cfgmgmtcamp (Ghent, Feb 2–4) 🚀

Ping us if you’re around.

[Roger Peppe @rogpeppe]

@0xlelouch_ My Q: what are good patterns you like to use for making your Go deadlock-free by design?

[Roger Peppe @rogpeppe]

@ImSh4yy Newcastle upon Tyne

[Roger Peppe @rogpeppe]

evergreen tweet

[Kent Beck 🌻 @KentBeck]

for each desired change, make the change easy (warning: this may be hard), then make the easy change

[Roger Peppe @rogpeppe]

@DuncanWChisholm Johnny Findlay is such a banger of a tune! I never knew its name or that it was written by Donald Riddell though - very happy to know that.