> Please stop discussing one of the most pivotal moments in history

This reminds me of prescientific explanations of the sun and stars

Like the best thing we have to remark on is the fact it is blue when this is probably the least remarkable thing about it

You know Steve Jobs would have said it's 2x too thick, 2x too big and way too asymmetrical

Claude is like

> The last one guesses its own refusals, marking the door open before we walked around it. Say the word and I'll do the joinery

Like WTF are you even talking about

I think it's reinforcement learning. It's been trained to give coding results but some of the conversation it gives as a side effect of its coding are absolute garbage

I think it's just that people who can't individually contribute end up doing... whatever else.

And managers that hired those people don't want to admit that they are bad at hiring people.

The Dunning-Kruger effect is very relevant here. Competent companies do not have this problem. Incompetent companies are completely oblivious to this problem.

> Only the five subjects of the Berkeley experiment have officially seen olo.

Basically equivalent to

source: trust me bro

There's a link to Dynomight's webpage in another comment thread. I've seen olo myself with it. It's to cyan what ultramarine is to sRGB blue.

I'd heard of weasel words but now that you mention it they do tend to be rather wiggly

Except that this requires extremely specialized equipment to individually trigger specific cone cells in your eyes, so I expect they have a pretty damn good idea of who has seen this and who hasn't.

So, source: trust me bro.

I started making a programming language that is designed to encompass frontend, backend, database, container, and cluster, so that there it is not necessary to stitch together other languages.

It uses functional programming and event sourcing to try and effectively "solve" modern distributed web application development, so that your app code in this language can be extremely simple but not have bad architecture and gaps.

I'm probably oversimplifying the complexity, so I don't even know if it's feasible, but it's pretty fun to give Claude my crazy ideas and see what happens.

https://github.com/georgestephenson/beck

It does demonstrate that to some extent: specular light is omitted from the normal map, so it correctly maps the room behind the light.

The last example also correctly identified broken panes of glass in the background, so that the glass is a solid and the spaces have nothing there.

I found similar from experience with lifting weights.

If my gym sessions are 300+ minutes per week, I end up too tired to increase the weight and I get weaker, it's counter productive.

180 minutes per week feels good but is pretty easy if it's 30 mins 6 times per week (or 60 mins 3 times per week). But that's where the effort-level really comes into it, how long are you resting between sets, etc.

So 150-300 minutes per week feels right but it depends on many factors. Elite athletes are genetic freaks, etc.