Riley Drake

I think my agentic dev stack is too simple. How are you setting up your dev environments for your agents? What tools are you using? How many agents are you running? Are you more hands on or are you running loops? I’m using Claude code with some skills for repeated tasks. I operate a few agents at a time but I work through each feature hands on with the agents. If a task is complex I use plan mode. And if context runs out I use handoff docs and spawn it in another agent. That’s it. Am I missing out on the winning architecture or is keeping it simple the right play? What’s your setup?

Publicity stunt

The best vibe coders are the most effective communicators and how would someone who understands less layers of abstraction (non technical person) be a better communicator than someone who understands more layers (technical person). This will never change no matter how advanced AI gets it is still bound by the efficiency of humans communicating ideas to it.

SaaS companies that survive will likely monetize on outcomes, not seats. SaaS isn't dead yet but per user pricing is

Knowing the destination still matters. Vibe coding from ground 0 risks over reliance on AI in the planning phase making the end result an expression of the mean

Architectural clarity before agent handoff is the new senior engineering skill.

The harness is the moat, not the model.

Each lab watches the others closely and adjusts launches to avoid being overshadowed. Parallel delays often reflect shared infrastructure limits, not alliances.

Western hyperscalers built moats on compute scale. If frontier models train cheaper in the East that moat may not hold

Knowledge and effort commoditized fast. Emotional clarity is the last durable advantage.

Email was too informal for business, cloud was too insecure, now AI hallucinates too much.

Building an agentic AI X growth assistant to help users identify what content works and scale it effectively. As builders on X, what features would you want out of an X growth optimization agent?

When AI closes the skill gap, the differentiator shifts to judgment, context, and knowing what to build.

Hosting DeepSeek gives Microsoft leverage over OpenAI pricing while hedging on model dependency. Azure wins either way the model war plays out.

The clearest edge humans hold is in low data environments where pattern recognition from lived context outweighs statistical frequency. First mover advantage in any new domain still belongs to the human who generates the signal before the model can train on it.

Slop is about adherence to the mean. If the models get better so does the output of one shot prompts, the results may be useful but there’s no ingenuity. It will raise the bar of quality across the board no doubt but one shot prompts will always deliver similar results. Think about the “slop” SAAS landing pages popping up right now. They’re objectively good sites, but they all look the same. True value is in the ingenuity.

Top tier rage bait

IMO slop has nothing to do with it being AI generated. AI tools can enhance content and greatly. True slop is low effort, one shotted output that is not refined. By definition one shotted poorly prompted content will always converge to the most mediocre average output but clever prompting and refinement can create impressively valuable content.

ROI on AI capex takes years to materialize. The glitches and bad chatbots are early deployment failures. I definitely agree the bubble is bursting but it will recover with tremendous value long term.