Ryan Edge

If you're building a terminal-based AI coding agent, it should have:

1. The ability to configure different models for ask vs. act modes.
2. The ability to select an Auto mode, where the model is autoselected depending on the task.
3. Something akin to Claude's insights command.

🚀 Flutter & AI @SoFi: Join us in San Francisco
To dive deep into what’s next, our next Flutter San Francisco Meetup is heading to the SoFi office on Wednesday, February 25th.
RSVP on Luma:https://luma.com/5uzi5ws4

#Flutter #Dart #GenerativeAI #MobileDev #SFTech

Ideas Over Implementation People tend to get attached to a specific concept of what they are trying to accomplish rather than the idea it represents

Don’t get attached to what you built. Get attached to what you’re trying to achieve.

When you fall in love with specific choices — the architecture, the tool, the approach — you’re forced to get everything right up front. That’s a high bar, and usually the wrong one.

boz.com/articles/ide...

What AI is actually good for, according to developers
github.blog/ai-and-ml/ge...

AGENTS.md outperforms skills in our agent evals
vercel.com/blog/agents-...

How to write a good spec for AI agents
addyosmani.com/blog/good-spec

How does AI impact skill formation?
www.seangoedecke.com/how-does-ai-...

When AI writes almost all code, what happens to software engineering?
newsletter.pragmaticengineer.com/p/when-ai-wr...

How I estimate work as a staff software engineer
www.seangoedecke.com/how-i-estima...

The rise of one-pizza engineering teams
www.jampa.dev/p/the-rise-o...

The third golden age of software engineering
newsletter.pragmaticengineer.com/p/the-third-...

Good tech reads from January...

Standardization = easier adoption, better interop, thriving ecosystem.

It would be nice if spec-driven development tools adopted some standardization.

Every tool has its own:
- Spec format
- CLI interface
- Config structure

Right now we're speedrunning the "14 competing standards" xkcd.

Stranger Things feels like it's just turned into a Wikipedia page for the 80s.

Google for Developers Blog - News about Web, Mobile, AI and Cloud

Everyone else: spec-driven-development
Google: context-driven-development

🤣🤣🤣

developers.googleblog.com/conductor-i...

Tech predictions for 2026 and beyond We’ve caught glimpses of a future that values autonomy, empathy, and individual expertise. Where interdisciplinary cooperation influences discovery and creation at an unrelenting pace. In the coming year, we will begin the transition into a new era of AI in the human loop, not the other way around. This cycle will create massive opportunities to solve problems that truly matter.

Tools evolve and complexity increases, yet creativity, curiosity, and systems thinking continue to define great developers.
Lowering the barrier for entry doesn't eliminate the need for human expertise—it amplifies it.

www.allthingsdistributed.com/2025/11/tec...

The whole Midoriya wants to save Shigaraki thing seems kinda pointless in retrospect 🤷🏾‍♂️

These first episodes of Stranger Things aren't hitting for me like it used to.

"I don’t believe CSS was ever designed to be an application UI tool. CSS was built for the web."

I agree, what we build today is a dramatic departure from what we built in 1994. To the 2nd part, I can't speak towards a condescension targeting CSS enthusiasts but toxicity in software is the norm 😢

CSS-in-JS: The Great Betrayal of Frontend Sanity CSS-in-JS promised simplicity but delivered performance issues. Learn why ditching it for native CSS solutions leads to faster, more maintainable web apps.

I would not call CSS broken, but it's a relic from a bygone era that no longer reflects how developers actually want to build UIs today.

thenewstack.io/css-in-js-t...

Rating the Alien/Predator movies by director:

1. James Cameron (Aliens)
2. Dan Trachtenberg (Prey, Predator: Badlands, Predator: Killer of Killers)
3. John McTiernan (Predator)
4. Noah Hawley (Alien: Earth)
5. Fede Álvarez (Alien: Romulus)
6. Ridley Scott (solely for Alien)

Then everybody else...

An important call-out is there's a certain amount of reliability and long-term maintainability that comes with every solution they provide, even though it is OSS.

TanStack | High Quality Open-Source Software for Web Developers Headless, type-safe, powerful utilities for complex workflows like Data Management, Data Visualization, Charts, Tables, and UI Components.

Basically Tanstack is an OSS org focused on DevEx. Their tools are modularly built. It started with Tanstack Query which is a framework for data caching of which Riverpod is heavily inspired. Now they have tools for everything from the offline database to routing and forms.

tanstack.com

@tanstack.com is an amazing OSS ecosystem and I wish @flutter.dev had something similar.

Dan Trachtenberg is a treasure that must be protected at all costs.

Predator: Badlands movie review (2025) | Roger Ebert An exceptional sci-fi action thriller with memorable characters and lead performances that deserve to be included in discussions of the year's best.

“Predator: Badlands” is an exceptional sci-fi action thriller with memorable characters, beautiful and terrifying animals (and plants), a structurally airtight script, and lead performances that deserve to be included in discussions of the year’s best

www.rogerebert.com/reviews/pred...

Engineering is about maximizing value while minimizing waste. This economic thinking is what separates developers from software engineers.

Ignoring the business impact of your technical decisions isn't just bad engineering—it's bad for the business you're building.

The greatest compliment I can give to #Flutter is that it "got it out the mud."

Flutter succeeded on merit, without a trendy pre-existing language or ecosystem, or a large zealous community. It achieved global success from a challenging start, with little to no external help.

An engineer who deeply understands 10K lines of code > one with 50K lines they vaguely grasp. With vibe coding, the temptation is volume. The wisdom is selectivity.

The bottleneck shifted from writing code to reviewing and maintaining it. The valuable skill isn't prompting—it's having the judgment to know what code to keep.

Vibe coding works best on well-understood problems in familiar domains. Using it for novel, complex challenges will create comprehension gap that increase cognitive load.

Vibe coding crushes boilerplate and syntax (accidental complexity). It doesn't solve architecture, business logic, or edge cases (essential complexity). You still need senior engineers for the hard parts.

"Adding AI to a late project makes it later." Generating code without proper review and integration just creates a bigger mess faster. Speed isn't the bottleneck—understanding is.

How many lines of code can a senior engineer maintain? AI can generate thousands of lines in a week. But optimistically, if a senior engineer can only maintain half of that, generation speed outpaces comprehension capacity. That's the new technical debt.