Live data from Hacker News

Some things just take time

lucumr.pocoo.org

211–220 of 295 posts

Re: Some things just take time

#211

With all the emphasis on the speed of modern AI tools, we often seem to forget that velocity is a vector quantity. Increased speed only gets us where we want to be sooner if we are also heading in the right direction. If we’re far enough off course, increasing speed becomes counterproductive and it ends up taking longer to get where we want to be. I’ve been noticing that this simple reality explains almost all of bot…

The biggest problem is the fact they DON'T clarify their stupid assumptions.

The number of times I've seen them get the wrong end of the stick in their COT is ridiculous.

Even when I tell them to only implement after my explicit approval they ignore this after 2 or 3 followups and then it's back to them going down blind alleys.

Re: Some things just take time

#212

Earlier quoted context omitted.

Yes, AI can emit BS at a faster rate than ever. We can also produce more blog posts than ever. Working or useful software? AI hasn't produced any at all since 2023.

Wow, an account, just for that? I feel honored and slightly suspicious.

Altman didn't want to post from his own account

Re: Some things just take time

#213

> We pay premiums for Swiss watches, Hermès bags and old properties precisely because of the time embedded in them Lost me in paragraph three. We pay for those things because they're recognizable status symbols, not because they took a long time to make. It took my grandmother a long time to knit the sweater I'm wearing, but its market value is probably close to zero.

I agree there, but there are plenty of examples of time cost being baked into an item, regardless of status symbols.

The sweater is with whatever value a single person values it as or would pay for it. Said another way, would you sell it to me for $10? 50? 100? If you said no to all three, it's worth at least $100.

Re: Some things just take time

#215

Earlier quoted context omitted.

Okay, tell you what then. Help me learn. The problem is that I want something that listens on a TCP connection for GD92 packets, and when they arrive send appropriate handshaking to the other end and parse them into Go structs that can be stuffed into a channel to be dealt with elsewhere. And, of course, something to encode them and send them again. How would I do that with whatever AI you choose? I'm pretty certain…

GD92 packets? No idea what you’re talking about but if it has a spec then it doesn’t matter if it’s trained on it. Break the problem down into small enough chunks. Give it examples of expected input and output then any llm can reason about it. Use a planning mode and keep the context small and focused on each segment of the process. You’re describing a basic tcp exchange, learn more about the domain and how packets a…

> GD92 packets? No idea what you’re talking about but if it has a spec then it doesn’t matter if it’s trained on it.

Okay, so you're running into the same problem that LLMs are.

> Break the problem down into small enough chunks. Give it examples of expected input and output then any llm can reason about it.

So I have to do lots of grunt work?

> You’re describing a basic tcp exchange, learn more about the domain and how packets are structured and the problem will become easier by itself

I've written dozens of things that deal with TCP. I already have a fully-working example of what I want. The idea was to test if I could recreate it using LLMs.

How is it supposed to work? How does it put in the code I already know I want?

Re: Some things just take time

#217

Sounds familiar, for most of my life I have tried to remove all "friction" from life – applying that engineering mindset to make everything as efficient as possible. Only then I realized that life somehow is about that "friction".

[dead]

Re: Some things just take time

#218
post #207

The point about all the extra efficiency just making us more stressed and busy resonates deeply with me. It also stood out to me in the recent episode of the No Priors podcast with Andrej Karpathy. It's that feeling of falling behind is you're not using all available compute. Btw the earendil.com website is gorgeous.

I'm more concerned about the "falling behind" we're doing chewing up compute generating, and then running, LLM slop. That is a lot of energy used and heat generated for a less-than-optimal payoff.

Re: Some things just take time

#219
post #170
post #98

Earlier quoted context omitted.

You write a metaphore in a comment, you remove half of it, you add another one in the middle, you add the half of the first one, and… nobody understands anything.

Is it the ultimate result of LLM use? People internalising the idea that writing is about stringing words together like a Markov chain without realising they're not saying anything of substance?

That is the philosophy of "humans are just token predictors", yes.

Re: Some things just take time

#220
Went indie after a long run at a big company and this hits. The hardest thing wasn't the work, it was getting comfortable with the silence between shipping and seeing any signal. Still working on it tbh.
Post reply on HN