c-fe

> they just don't need the data anymore.

Thats the wording of GDPR.. that you should delete data after you dont need it anymore for the original purpose..

Unfortunately, it seems noone is enforcing it enough.

What approach did you take with AI to make it discover an edge? Give the AI autonomy to search for edges itself and build e.g. a backtest it can use to confirm, or narrow it done with research (possibly AI) and then investigate specific approaches with AI? Or in other words, how autonomous was the AI in finding that edge?

going on a bit of a tangent here - some discussion there seems to be imply that AI bots mostly use IPv4s, which makes sense to me given that they are probably bots hosted by some cloud. Whereas IPv6 may be more organic traffic from e.g. mobile users (not in this case probably)... which made me think if at some point IPv6 may at some point win against IPv4 just because its more organic traffic (i.e. not from big tech cloud), leading to pages blocking IPv4? Just speculation on my side

I also enjoyed it. Something about the writing really made me enjoy it, it was so different from the llm text i read all day long

will claude platform on aws offer the same nerfed (dumb) opus 4.5/4.6/4.7 of the recent weeks, or will it be possible to use opus 4.5/4.6 from february/march?

This is very similar to SBE encoder/decoder flyweights over raw memory? What are the differences?

> Maybe it arrives while the first request is still running. Now your idempotency layer is part of your concurrency control.

I recently designed a system where this had to be taken into consideration. I find my solution very elegant: When the request arrives, I put the pending request into a map, keyed by the idempotenceId. This whole operation is executed in one step. Now the event loop may process other requests. If one of them has the same key, it will await the same response object from the store. And then, once i have the response, I resolve both promises with it.

funnily enough, I talked recently to someone working on the swift compiler (not an Apple employee) to make Swift functions differentiable. So its not all dead yet

> In the Write-Only Code story, that same engineer becomes a systems designer, a constraint writer, and a trade-off manager.

This is also what I see my job to be shifting towards, increasingly fast in recent weeks. I wonder how long we will stay in this paradigm, I dont know.

interesting. Do you have an example of what exactly it outputs and how you store that? how do you use the outputs? As a pointer to a new agent with fresh context to get them up to speed?

uninstall the app. Works really well to me. The conscious effort of reinstalling it is enough to prevent me from doing it. Whereas using the awfully implemented screentime guards, I just find myself clicking on "Allow for 15 minutes" before I even understand what I do.

select in finder the file that currently opens with XCode, then press Cmd+i. It opens the information panel. There in the Open with section, you can chose the app and then also Change all to not use XCode.