amplified.dev is a single-page essay arguing developers are amplified, not automated. One HTML file, inline CSS, vanilla JS. No frameworks. We wrote 11 checks for it. Checks don't have to protect code — they can protect taste. Here's what ours look like.

We are evolving from vibe coding → vibe engineering → Continuous AI - Vibe coding = fast AI experimentation - Vibe engineering = sophisticated AI-assisted production development as individuals - Continuous AI = orchestrating agents across your entire dev lifecycle as a team

So 🔥 I love when startups do research and just ship in product. Skip the benchmarking theatre.

Introducing Instinct 🐺, a new state-of-the-art open Next Edit model trained by @continue.dev Runnable with @ollamabot.bsky.social and available today in VS Code

There is so much room for context engineering improvements at large organizations

“Developers will be the ones who drive how many languages we have. Their actions and their stewardship of their niche programming languages will determine whether we have more or less” - @ty.energy in 'The programming languages facing an AI-driven existential crisis' by @karimcmack.bsky.social

@continue.dev is hosting the AI Native Dev - SF Meetup at GitHub HQ (thanks to Kevin Crosby!) with @jedi.be and friends ️‍🔥

@ty.energy joined Balaji Sivasubramanian on the DevAI podcast to discuss the open architecture that we believe will underlie the future of AI-native software development 😎 www.youtube.com/watch?v=FwZq...

We launched on Hacker News yesterday! There was a great discussion on custom AI code assistants. In case you, missed it:

It’s critical that an open architecture underlies the future of AI-enhanced software development. This is why we are launching Continue 1.0 with hub.continue.dev today: techcrunch.com/2025/02/26/c...

I am now @ty.energy 👋

Lineages of information structuring matter have led me to this Recursive Worlds lecture by Sara Imari Walker (and Bluesky, hello world!) antikythera.org/films/recurs...