Spyke

Syndicated from the fediverse. Read and engage on the original instance.

View original on programming.dev

7 replies

A great example from the article on the benefits of "getting freaky" and experimenting with different architectural ideas:

To see why this matters, let’s look at a miniature example: building a collaborative document editor.

Team Standard uses the default AI stack. They prompt Cursor to build a React frontend with a Node.js backend and PostgreSQL. The AI generates it perfectly. But as users start collaborating, they hit race conditions. Team Standard responds by throwing money at the problem— adding Redis pub/sub, writing complex conflict resolution logic in JavaScript, and spending weeks debugging edge cases where a user’s cursor inexplicably deletes an entire paragraph. Their feedback latency is massive because the architecture fights the inherent reality of distributed users.

Team Weird decides to use a Local-First architecture with CRDTs. The learning curve is brutal. They have to deeply understand distributed state. But once they cross that threshold, they use AI to generate the boilerplate for their CRDT data structures. The result? Every user edits locally with zero latency. Syncing happens silently in the background. If the server goes down, nobody notices.

Team Standard shipped faster. Team Weird shipped a fundamentally superior product that Team Standard cannot easily copy without rewriting their entire architecture from scratch.

3
programming.dev

Great article. This is so true: You have to use the AI to eliminate the mundane, reserve your brain for formulating your most sick and twisted tech opinions, and then use the AI to actualize them. You have to get weird.

Exactly how I'm using it. I'm sure you catch a lot of heat because this comm deals with AI, but I appreciate you and this community!

2
codeinaboxreply
programming.dev

Thank you, that comment made my day! There is no denying that agentic coding is a divisive topic, which is all the more reason it's worthy for discussion.

3

Very welcome! I think AI is something we need to talk about rather than just hate, because it’s a tool that isn’t going away. We have to adapt. People who don't are going to find themselves behind the curve.

I think the positives of AI outweigh the negatives, and there are plenty of negatives. But I’d much rather see well-reasoned criticism than another boring comment from someone screaming, “Slop!”

Screaming isn’t going to stop it. It'ss going to keep advancing whether Lemmy likes it or not.

There’s an entire generation of kids in their early teens right now, sitting in their bedrooms, experimenting with AI and learning how to use it. Just like the earlier generations of kids who taught themselves programming, computers, and hacking the same way by fucking around with games and shit.

In around eight years, a lot of those kids will be entering the workforce with years of AI experience already behind them.

They’re going to look at today’s “AI is slop!” crowd with the same amusement people now reserve for boomers yelling, “Get off my lawn!” lol

It feel's like I'm watching Lemmy become Boomers in real time. Boomer Lemmys scared and angry about new technology. It's sooo weird to see a tech crowd be so resistant to tech. Most of these guys here would have been all over AI if it would have came out in their teens.

2
lemmy.world

Surely, someone who makes prescriptions about "the age of AI" would know that readers don't want to sift through articles which read like AI slop

1
codeinaboxreply
programming.dev

What makes you think this article is written by AI? Slop doesn't come with clever cultural references to the recent film Obsession.

2

If it's recent, maybe the readers also don't yet know the references

1

You reached the end