Hacker Newsnew | past | comments | ask | show | jobs | submit | joshwa's commentslogin

URA quotas—I see the Amazon infection has spread from Seattle to Redmond.


The thing about language models is that they are *language* models. They don't actually parse XML structure, or turn code into an AST, they are just next-token generators.

Individual models may have supplemented their training with things that look like structure (e.g. Claude with its XMLish delimiters), but it's far from universal.

Ultimately if we want better fidelity to the concepts we're referencing, we're better off working from the larger/richer dataset of token sequences in the training data--the total published written output of humanity.


Just the opposite! When sautéing, too-small pieces have burned by the time the larger ones have cooked, giving the dish a bitter burnt flavor and ugly black flecks.


If small pieces burn then so will ends of larger pieces. Just lower the heat and give it enough time instead.


https://onion-cutting-simulator.streamlit.app/

I made my own version of this a while back, and it lets you create your own cutting methods, plot the statistical distribution, and share your ideas via permalink. It also lets you tweak onion parameters, such as number of layers and the layer thickness distribution curve).

Along the way I discovered two things:

1. I came up with my own method ("Josh’s method" in the app above) where the neither the longitudinal cuts nor the planar cuts are full depth, so the number of cuts at the narrower core is less than at the wider perimeter.

2. After all this hyper-optimization about size, it turns out what really matters when cooking is the THICKNESS, since ultimately determines the cooking rate. The only way to avoid thin outliers that burn long before the rest are cooked is to discard more of the tip of the onion, where the layers are the thinnest.

The 3D version of the simulator is still in progress--turns out 3D geometry is a lot harder than 2D. :)

Pull requests are welcome! https://github.com/joshwand/onion-simulator


Beautiful!


My thought is just to rent it out for to rich folks with lawns for a few hundred bucks a week. My contraption will have thermal detection, AI target discrimination, and precision targeting with a laminar flow water stream. That’s the plan, anyways.


Likewise but for raccoons. Are you precision targeting or just broad sprinkler coverage? I need to make sure my cat doesn’t get hosed :-/

I got a cheap MLX90640 off aliexpress for target detection and a grove vision AI V2 module to use with IR cam for classification/object tracking. Esp32 for fusion and servo/solenoid actuation.

Collab?


messagingengine.com is the domain used for fastmail's mail servers.


Huh, that suggests that geocrasher doesn't actually know what they're talking about.


Ah, the classic build tool evolution cycle! 1. Become frustrated with complex build tool

2. Write a new tool that is dead simple, opinionated (your opinions), convention over configuration, etc

3. Post to HN

4. Achieve adoption

5. As more people use the tool, feature creep ensues

6. In order to satisfy diverse use cases, make everything modular and configurable!

7. Tool slows and becomes impossible to manage

8. GOTO 1.


That's quite a leap there. Vite has a different strategy to overcome webpack's slowness, mainly using ES modules and build on demand.

So, even if it were to support more features, it will still be a net gain over webpack.

Not to mention that vite uses esbuild which is 10-100x faster than next best


> feature creep ensues

I believe esbuild authors (and Vite relies on esbuild in development) are adamant that they are not going to allow feature creep.


Can I just stick a vibrator against the back of my skull for a few minutes daily?



Hi OP, did you ever find a good solution for this? Trying to set something up for my daughter's kindergarten class.

(email in profile)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: