DEV Community

@ThePracticalDev

The Twitter account that launched dev.to. Built on @forem 🌱 On Bluesky @/dev.to No DMs — please email us for support!

[email protected]

dev.to

Replies Reposts Media

DEV Community
@ThePracticalDev
2h
Navigation, content, affordances. This dev argues every frontend architecture of the past 30 years handles these three, maps HTMX, LiveView, SPAs, Astro, and Server Components onto one grid, then brings in SolidJS 2.0. { author: @RyanCarniato }
The Grand Unifying Architecture of Frontend
From dev.to
DEV Community
@ThePracticalDev
5h
An MCP server is almost always a thin adapter over a REST, GraphQL, or gRPC API. This dev breaks down who each one is built for, the production problems MCP still has, and what the stateless spec update changes. { author: @thesnehamk }
MCP vs. API Explained: Do We Still Need APIs After MCP?
From dev.to
2
DEV Community
@ThePracticalDev
11h
A new teammate's AI assistant has to relearn months of conventions the rest of the team's assistants already know. This dev introduces memshare, an open-source MCP tool that treats AI memory as shareable, user-owned JSON. { author: Uri Shmueli }
The missing layer in AI tooling: sharing what your assistant already knows
From dev.to
5
DEV Community
@ThePracticalDev
15h
Opus for planning and debugging, Gemini 3.1 Pro for routine work, ChatGPT for throwaway questions. This dev unpacks the AI pecking order we build without deciding to, and why risk may explain it better than quality. { author: Dhruv Jani }
We All Have a "Serious Work" AI and a "Just Vibing" AI. When Did That Happen?
From dev.to
3
DEV Community
@ThePracticalDev
Sep 26
"Write small functions" is easy to enforce. "The wrong abstraction is more costly than duplication" is not. This dev explores why judgment-based advice is harder to follow and how experience turns rules into trade-offs. { author: @RemoHJansen }
Why the Best Software Advice Is the Hardest to Follow
From dev.to
1