Live data from Hacker News

Move Slow and Make Things

multithreaded.stitchfix.com

131–133 of 133 posts

Re: Move Slow and Make Things

#131
post #24

Earlier quoted context omitted.

> I sent in my measurements and they sent me a trouser with wrong measurements and a postcard that said that they adjusted my measurements with AI for a better fit That is nothing short of hilarious. The machine knows best! Who are you, human, to pretend you are able to measure yourself?! > AI for memorizing generic trends It's possible "AI" may be just a pretext to sell mass-made junk and pretend it is adjusted to e…

> It's possible "AI" may be just a pretext to sell mass-made junk and pretend it is adjusted to each individual. It's also an internal distraction. They'd achieve something much closer to what they promise if they just threw some old-school regression analysis at the problem. But that's not cool these days, plus it's hard to relabel as AI even for the marketroids these days, and would involve actual work :). This app…

How about a neural network trained on thousands of fashion trends?

And by "neural network", I mean my brain.

And by "thousands of fashion trends ", I mean I look at people in the mall.

Re: Move Slow and Make Things

#132
post #59

Earlier quoted context omitted.

Shared state is fundamentally hard. I don't think you can make it bullet-proof at the hardware level without sacrificing performance.

Exactly because it's fundamentally hard, it must be avoided -- we the humans simply can't be trusted with it (speaking as a former C/C++ dev here). It should also be hardware-assisted (if it's impossible to stop it at the hardware level). Stuff like atomic counters were a good first step but the state of the art there hasn't moved in a long time (we don't have atomic 512-bit update operations, do we? if we did, a lot…

OT isn't done in hardware because it would be a massive waste of transistors. It would optimize many (possibly even most) software and would just increase cost and power consumption.

Re: Move Slow and Make Things

#133
post #132

Earlier quoted context omitted.

Exactly because it's fundamentally hard, it must be avoided -- we the humans simply can't be trusted with it (speaking as a former C/C++ dev here). It should also be hardware-assisted (if it's impossible to stop it at the hardware level). Stuff like atomic counters were a good first step but the state of the art there hasn't moved in a long time (we don't have atomic 512-bit update operations, do we? if we did, a lot…

OT isn't done in hardware because it would be a massive waste of transistors. It would optimize many (possibly even most) software and would just increase cost and power consumption.

And constantly reinventing broken wheels in every program isn’t a massive waste of transistors AND electricity?

I get where you’re coming from but that line of thinking got us into that mess in the first place IMO. At one point we should draw a line. Which we still don’t.

Post reply on HN