zomtorg

> Now that most clocks are networked, there's no reason to stop at 8.

The watch enthusiasts would like to have a word with you.

I think the bigger issue is skipping the process through which you learn. Personally I learn the most when I am stuck on something for hours trying to figure it out and I miss all of that when AI gives a solution right away.

You get more done without realising you're learning less.

And the closest known galaxy to the Milky Way, Canis Major Dwarf Galaxy, is just 25,000 light-years away - it's almost incomprehensible how vast the universe is!

And so the enshittification begins

Assuming that data degradation is not an issue and your data is available on a magnetic drive perhaps a future archeologist would have access to a quantum machine that would make decryption of the media possible.

The upside might be the return of CDs?

And so the rebranding continues... "artificial intelligence" in the 1950s was used to differentiate itself from "cybernetics". Then once it became unmarketable due to the AI winters, we saw "machine learning", and all kinds of "<term> recognition". Now that we have "AI" as a term for any classifier, people who meant the more ambitious version moved to "AGI". Seems like "super intelligence" just moves the treadmill up another step. Curious what we would call it next.

I wonder if we would see more engineering teams transitioning away from git to Sapling. We do need a refresh on how we review and ship code.

I'm aware that GH recently released stacked PRs, but it still seems like a long way to go both from usability and reliability perspective compared to what Meta and likely Anthropic have internally.

Mainly gRPC for cross-service communication, k8s, and all the workflows on Temporal with the agent logic as activities.

For tracking and adding guardrails across many agents and having caps (e.g. the same agent type can do at most X of this action in 24 hours) I have created https://actera.dev/

I wonder if the credits are just a list of everyone it was trained on

My 2c is that agents are not at the level where companies can easily just have unconstrained LLM with tools and let it be. Different parts of the workflow can have different models, different tools, different constraints, guardrails, etc.

The entrypoint still has to come from somewhere, and it's much more convenient to be able to explain the security and legal teams how data is handled, what is logged, how you can have control over a scenario where the agent does something unexpected.

Sure, for a personal project that could be enough, but we all know those companies target enterprise customers, and you would be surprised how little adoption there is when it comes to workflow automation due to the lack of controls.

This is great write-up and it's great that we can use AI tools to peek behind the curtain of how games like these were made.

Hopefully it gives more people a creative kick and we see a revival of more games inspired by some of those game mechanism and potentially even move away from using the well-known set of engines to build games with.

I also think the context of building software matters quite a bit as well.

In a big corporation where ownership is fragmented and initiatives that are big enough for the mythical man-month problem to become tangible, big part of the problem becomes aligning the different engineering teams around why something should be built now, why team X and not team Y should do it, doing it securely and having enough confidence for a release.

I'm interested to know the following:

Is selling vaporwave songs legal, such as those that remix Michael Jackson? If not, who is liable - is it the creator of the song or the seller of floppy disks?