HN user

movedx01

43 karma
Posts0
Comments39
View on HN
No posts found.

Yes, they basically pioneered lootboxes, they shaped and scaled microtransaction economy around randomized outcome purchases under disguise of gaming and then slapped a marketplace on top of it(to take even further cut %% nonetheless).

I can't even picture gaben with a wispy moustache to twist evilly.

Add a 500m gigayacht to the picture, maybe it will make it easier. Or a fleet.

"addictive design of the algorithms"

Any self improving loop where the user is not in control, thats it.

If I subscribe to A and get more of A - thats fine.

If the algorithm detects that I spend 0.5 second longer on average looking at content with feature A and so decides to show me more of A - thats bad. At most it might be allowed to ask me if I want to subscribe to more of things with explicitly defined feature A, but even that assumes we are fine with collection of behavioural data like this in the first place and so it is a stretch already.

Transparency and control is what makes the difference here in my opinion.

Why not restrict the addictive design of the algorithms instead? No need to blanket ban social media access if the social media cannot optimize to steal every last inch of their attention. Anything on the feed becomes opt-in only and no engagement data coming from the user or from the outside can be used to optimize it, thats it. Control is back in the hands of the content consumer, parental restrictions become trivial, no black box algorithm deciding what bubbles up and what gets buried deep down.

Claude Tag 29 days ago

From what I've seen trying to play around with Claude Tag, it uses shared credentials. You set it up with Github org access, add it to public channel, and all random people in that channel can now ask it to do stuff with code. It's opposite of what Cursor does - each Slack member needing to connect their own Github account. It's a security nightmare basically.

So why are you looking at this code?

Because I am getting the call to fix it when it breaks. I don't have to fix assembly by hand because compilers are deterministic and I have maybe encountered a single real compiler bug in my whole career. Compilers have earned my trust. LLMs are eroding that trust more and more every day I work with them. I encounter LLM-created problems in basically every single diff they surface for me, just over the months the diffs are getting bigger and harder to review and uncover the problems.

LLMs are not an abstraction(not even a bad one) because by design what they are doing is disambiguation. Compilers are not doing that, what you put IN the compiler has to be unambiguous in the first place.

Disambiguation is not a functionality of an abstraction layer. A good abstraction layer is the one I don't have to understand and can trust, if I have to understand its inner workings to use it it ceases to be an abstraction. Except with LLMs you can't even do that, they are a black box you can have no hope of understanding.

And it is not to say LLMs and agentic coding tools are not useful, they are absolutely very useful. They are just not an abstraction layer.

coming soon

The developers are literally on the bleeding edge here, it might be the most developed of the AI use cases right now. The most advanced tooling for LLMs revolves around SWE work, there are multiple prolific benchmarks that the labs are actively targeting in this area, and new ones are being built, whole product categories being spawned, software companies bleeding money for tokens.

It's the other professions that are to follow once the training data is in place to go reach for their livelihoods. SWEs got the early taste of what is coming. And the blender news is exactly that.

Average is only a tombstone of someone having failed to do better. And settling for average means pulling down.

When it comes to bs dashboard where "average is all you need", maybe the "better than average" result would be asking yourself if it's even worth doing in the first place?

Probably the same way other models learned to surpass human ability while being bootstrapped from human-level data - using reinforcement learning.

The question is, do we have good enough feedback loops for that, and if not, are we going to find them? I would bet they will be found for a lot of use cases.

I am vibe-porting an old game, Knights & Merchants(actually its Delphi rewrite - KAM Remake) to WASM. It's going well, I even have multiplayer working, will release it publicly at some point.

Learned more about WASM, OPFS, JSPI and other exotic browser stuff more than ever, also learned more about pascal than I ever wanted to, but it's been immensely fun.

Not having a code review process is archaic engineering practice at this point(at any point in history, really), be it for human written or AI written code.

You know what is an insult? Supermarket on my street putting on display sloppy ads with ramen bowl that has 3 different thickness chopsticks and cartoon characters with scrambled faces. Now that is an insult, because there was a human being doing that job, and I am sure there was a great "productivity boost" related to that change.

I am a heavy AI user myself, and sure as hell I am not putting my foot in that place again.

Is that even possible? Last time I checked it wasn't, while it was possible with OpenAI. Since that moment(early this year) - OpenAI has removed that option and their "Project budget" feature turned from being a hard limit into an email notification.

Is that true though? Every time i tried to get Sonnet to write out any actually complicated layout/component, I ended up with a novel of classNames with a ton of duplication and useless additions. Those are very hard to spot inside a soup of tailwind classes, whereas I can see them immediately in a nicely laid out stylesheet. This happened extremely often when I tried to iterate with Cursor/CC on the given design, instead of giving up immediately after it failed to one-shot it.

This is great, and I keep my fingers crossed for Hatchet!

One use case I imagine is key here is background/async agents, so OpenAI Codex/Jules style, so that's great if I can durably run them with Pickaxe(btw I belive I've read somewhere in temporal docs or some webinar that Codex was built on that ;), but how do I get that real-time and resumable message stream back to the client? The user might reload the page or return after 15 minutes, etc. I wasn't able to think of an elegant way to model this in a distributed system.

That's great! It would be even better if one of the features included in the table was whether given MCP supports OAuth Dynamic Client Registration, which optional in the MCP standard.