News for hackers. Stuff that matters.

joshwa

Re:Everyone in Seattle hates AI on Thursday December 04, 2025 @04:05PM (#46153065)
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.

Re:Dicing an Onion, the Mathematically Optimal Way on Sunday August 17, 2025 @11:00PM (#44936976)
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.
Re:Dicing an Onion, the Mathematically Optimal Way on Sunday August 17, 2025 @10:23AM (#44931785)
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

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.
Re:Why we switched from Webpack to Vite on Wednesday April 28, 2021 @08:06PM (#26975792)
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.

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

Ask HN: Does this exist yet? UGC video clearinghouse for protests/etc.

I was inspired by OSINTHK's work during the protests in HK--assembling multiple videos of single incidents to provide as much context/evidence to fight the public relations battle.I'm sure something like this must exist already--a collaborative public OSINT platform for correlating UGC by timestamp and location? Where users can upload video and based on the metadata you cluster them into...

( Read More... | 1 comment | on HN )
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)

Re:New Grad vs. Senior Dev on Saturday March 28, 2020 @09:57PM (#22715757)
On a larger architectural scale, see: Use Boring Technology

http://boringtechnology.club/

Also described as: "how to be old, for young people"

Re:New Grad vs. Senior Dev on Saturday March 28, 2020 @09:54PM (#22715742)
Knowing how so many devs are hungry to move to the new shiny thing, the question is often more like "why hasn't this been rewritten in Python3 already?".

Possible answers:

• Legit technical or cost/benefit reasons

• Probably a good idea but no budget/time for the effort

• Somebody already tried and it was a disaster

• No manager has been stupid enough to humor the devs

Re:I got my file from Clearview AI on Wednesday March 25, 2020 @02:19PM (#22687070)
Re:Spreadsheet Horror Stories on Friday February 28, 2020 @11:20PM (#22448792)
Worth mentioning Exce-Lint, an Excel add-in that automatically finds formula errors in spreadsheets.

https://plasma-umass.org/ExceLint-addin/

Re:Show HN: Terrastruct – A Diagramming Tool for Systems on Sunday January 05, 2020 @02:52PM (#21963566)
It's kind of an old-school tool, but Enterprise Architect is a tool that does just this. It's also a completely overwrought model-based engineering thing but ignore that and it's a useful systems/data architecture model database tool.

https://sparxsystems.com/products/ea/

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.

There's a good review of existing and novel desalinization technologies, including OP's supercavitation method, here:

https://www.researchgate.net/publication/271673255_Large-sca...

Older »