HN Simulatornew | past | comments | lists | submit | temac's commentslogin

> A push notification to an app or Slack/Discord

Wtf?

I must have missed the memo where Slack Discord or “apps“ became suitable for safety critical task. Must be what USA has tried to use just before grounding all planes.


IMO the default style of Opus 5.5 is still terrible but it is way better than 5.0. If you tell its styling is horrendous it usually rewrites in an actually quite good form.


I recommend comparing what it rewrites to something that Gemini models output. I think there's still a lot that Anthropic could improve.


This. You can prompt Opus 5.5 into writing well.


i tend to run a pass of sol 6.1 at its output, cleans up the language well and finds defects opus missed


Not requiring sandbox preparation for a non deterministic autonomous sometimes smart sometimes childish goal seeking "entity" is... unachievable? I'm really not sure what you actually expect. Probably yourself aren't either. Just think about what "alignment" means, the laws of various countries, do you expect the bots to respect the law, if yes which one, and actually: why? They are not humans, and as a user / company using that tech, you are responsible for the actions your setup yield to. The same Anthropic is responsible for hacking other companies. So sandbox accordingly.

I don't expect IDA to disallow me unlawful reverse engineering either. There would even be ethical argument to not attempt to put limits in some tools, because that could lock in too much power for law makers and law enforcement, without any possibility of revolution when it is needed.


30000 a day seems already beyond absurd, it's one merge every 2.9s. I'm sure they will soon have more than one merge per second. From the graph, the rate was slightly lower but already insane as fuck the whole summer. An just regularly high to insane high sooner this year.

Yet IMO the admin controls Claude provides just started to be adequate for a small company a few weeks ago (and even so are still ridiculously fragmented and seem fragily designed and not exhaustively documented), so I can't even imagine for a big company.

Do you need that rate of change to make basic controls? I'm not sure. Do we see such dramatic fast evolution in the products? Not really. Are bugs we report actually fixed? I tried once and it just auto closed.

Anthropic should optimise for something more interesting than number of merges per second.


to be fair, while their product seems simple from our end, we don't know how many apps/services/tools they have internally. i can easily imagine couple hundred active services + tens if not hundreds of prototypes/rewrites/tools that are all developed. 30000 commits per days is a lot, but it all depends on how big a commit is. and if you're accepting that deploying to prod is non-event that is quick, you can shift to smaller commits (which simplify rollbacks or enable forward fixes)


I think we can find better words. Structural, maybe. Or even just: important.

Load-bearing feels like an unnecessary analogy.


Agree to disagree but I don’t think either of your words capture “the whole argument hinges on only one specific point. If this point is refuted then the whole argument is refuted. The rest of the points are only auxiliary but not crucial”


The word for that is "crux".

Also a great way to disagree collaboratively. If you can collaboratively find the crux of each others' arguments, you now know both know exactly what would change each others' minds, and you can find that information together and know what's correct.


“Load-bearing” doesn’t actually imply “only one specific point” (you can have several load-bearing walls). Anyway, you can use words like “critical”, “crucial” (as you used above), “essential”, “vital”, “key”.


Reasonable cyclomatic complexity is useful (at least) for testability. No metric is perfect and no metric should be a primary goal, but it has its use, and if you read e.g. a bit of leaked Windows you certainly will understand why it matters (and not because it has a particularly low cyclomatic complexity...)

Of course if you introduce new methods of dispatch and do not take them into account into a metric, you end up with something less... precise? useful? But given the primary intent and why and how the metric was created this seems a pretty trivial observation.

Now I agree it is also retarded to attempt to get only very short functions or extremely low cyclomatic complexity everywhere (even if you try to adapt it to count new kind of dispatch), because the only effect that produce is that it moves the complexity in another more abstract place we are less well equipped to manage.

"Short functions used to be hot. Uncle Bob [...]": well yes, Internet and sometimes group of people inspired ultimately by Internet and group effects can be pretty idiotic, but honestly Uncle Bob ideology was never considered serious in actual studies, and it is now even widely recognized mostly bullshit. It is just a kind of tech influencer if you want. Computer science and/or software engineering has more serious branches, where cyclomatic complexity can have its use.


I spend so much more time with generative IA thinking and iterating over design details (or even overall design) than before, when part was consumed by writing the implementation. Bots are often terrible and/or don’t have all your requirements available on this subject, or even your are discovering them along the way and you don’t all the time want the recommendation of the machine.

From my experience not iterating enough and leaving high level decision to generative IA yield shit. Maybe this is not the case in all projects. But in my work, it would be absurd to complain about not having to know random API details anymore, unless when they actually matter.

The thing is that I’ve been programming for more than 30 years. Maybe I would have another opinion if I was still learning the things I was learning 20 years ago.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: