HN user

nateroling

240 karma
Posts5
Comments62
View on HN

No, I think I he’s saying that we have that, and we should use it more.

AlphaGo uses discovery when it evaluates potential moves and iterates.

Claude Code uses discovery when it generates a script and the evaluates whether it works or not.

He’s saying we need to allow ai systems to do the evaluation and iteration themselves for science and engineering the same way we do for code.

Basically, harness engineering for engineering.

I’ve bounced off of LazyGit multiple times because I never figured out how to make it play nice with a light theme terminal.

I haven’t used dark mode anything for years. I set my monitor so it’s roughly as bright, or slightly brighter than, a piece of white paper.

No more flash-bangs when some website doesn’t support dark mode.

I mean that when a computer can visually understand a document and reformat and reinterpret it in any imaginable way, who cares how it’s stored? When a png or a pdf or a markdown doc can all be be read and reinterpreted into an infographic or a database or an audiobook or an interactive infographic the original format won’t matter.

This made me do a double-take. Surely you would never do this, right? It seems to be directly counter to the idea of being able to audit changes:

“Event replay: if we want to adjust a past event, for example because it was incorrect, we can just do that and rebuild the app state.”

This, but for many things.

Paint is ready at the hardware store Table is ready at the restaurant Construction is done on a bridge

All kinds of things that we need a one-time notification for.

Composable SQL 1 year ago

I’ve done the same with SQLAlchemy in Python and SQLKata in C#.

Sadly the whole idea of composable query builders seems to have fallen out of fashion.

I had the same thought, but it sounds like this operates at a much lower level than that kind of thing:

Then, a physics-based neural network was used to process the images captured by the meta-optics camera. Because the neural network was trained on metasurface physics, it can remove aberrations produced by the camera.

The problem with these kind of pixel-perfect, inspectable design tools, is that there's no distinction between important details and unimportant details.

For example, if our app uses a letter-spacing of 1.2 for all the body text, and your Figma design uses a letter-spacing of 1.25, is that important? Or is that a mistake?

In something like Figma, being consistent is difficult for designers. But in code, being consistent is the default — exceptions are hard for developers!

There's a fundamental mismatch that just ends up being painful all around.

"The map is not the territory." Trying to get a design doc to 100% accuracy is often a waste of time. Design tools need a way to specify which details are important, and which are not.

I have a custom theme that's pretty minimal, because I find lots of colors distracting.

Colors are vaguely based it on pen on paper:

       white: background
   dark blue: foreground
  light gray: brackets and commas and stuff
         red: literals (strings, numbers, true/false)
       black: comments
This means comments and literals stand out, which are usually the things I don't want to miss when I'm reading through code.
Preact Signals 4 years ago

Maybe I’m thick, but I don’t see what makes this (or solid, or svelte) different from Knockout or RxJS. Does this somehow avoid the tangled dependency chains and complex push-based reactivity issues that I deal with in RxJS/Angular?

To me the brilliance of React is the VDOM, which allows you to treat your components like a render loop in a game.

What’s the piece that I’m missing that separates Signals from RxJS observables?

I’ve played with this idea a bit. In my experience it felt like a hack to work around the fact that individual PRs took a while to get merged.

An alternative solve is to work in a way that allows PRs to be merged more quickly, ie pairing, mobbing, or prioritizing getting reviews done asap.