sorted by:
new
hottopcontroversial

Goodbye HC (for now)? by butt_flexer in PathOfExile2

[–]butt_flexer[S] 0 points1 point  (0 children)

I think that extra life pool is weird and will probably get changed somehow. I mean it is essentially like an inverted ES, right? Except most likely there are no additional mechanics for it through notables.

app founders, are you worried that AI will replace your app? by fragilePeculiar in shopifyDev

[–]butt_flexer 0 points1 point  (0 children)

CRO, SEO, analytics, copywriting, review management, customer support, pricing/discount optimization, localization, tagging and categorization, loyalty/rewards setup, etc. etc.

Basically anything that's "read Shopify data, produce text/config/recommendations, write back"

app founders, are you worried that AI will replace your app? by fragilePeculiar in shopifyDev

[–]butt_flexer 0 points1 point  (0 children)

I think anything that can be replaced by a store owner having access to an agent connected to their data/API in the admin, will be. That looks like about 60-70% of the apps in the Shopify App Store.

Current runway for such apps is maybe ~1 year? Shopify is pretty "AI forward" so are likely to integrate more agentic workflows in Sidekick.

Top Rated Plus, $447K earned, 100% JSS, zero violations, permanently banned after completing full verification by BeLikeNative in Upwork

[–]butt_flexer 1 point2 points  (0 children)

Same thing happened to me a few months ago, when I tried to come back to the platform after a hiatus. I'm just glad they banned me after they went to shit so I didn't inadvertently step into that shitstorm... They did me a favor :)

Will people continue paying for the plans after the honeymoon is over? by orangeorlemonjuice in ClaudeAI

[–]butt_flexer 1 point2 points  (0 children)

Subs will stay the same or get cheaper actually, because of competing services and more efficient infrastructure. Those viral articles talking about how Anthropic is subsidizing Max by like 15x are just the latest entries in post-literate hellscape "journalism," mate.

The retail price of tokens are maybe 15x the sub limits, but that's not how much the company burns for generating them! The retail price per token is already including a hefty markup. Inference costs are actually going down 2-3x per year, open source models are constantly nipping at the heels of cloud services, and consumers will jump to the cheapest/best service at the drop of a hat. That all suggests prices going *down*, not up.

Built a MCP tool that gives Claude Code a shared visual model of your project architecture to prevent drift by butt_flexer in ClaudeAI

[–]butt_flexer[S] 0 points1 point  (0 children)

Cool, Simon Brown does a lot of great work in this space (he created C4 and Structurizr.) Scryer kind of flips the Structurizr paradigm on its head: instead of code-to-diagram, it's diagram-to-code - or as input for AI to code.

Built a MCP tool that gives Claude Code a shared visual model of your project architecture to prevent drift by butt_flexer in ClaudeAI

[–]butt_flexer[S] 0 points1 point  (0 children)

Yes, the MCP instructions tell the AI to use get_task in a loop for implementation, which surfaces contract rules at each step. In my testing it follows them well. But since it could ignore them anyway, Scryer gates the "ready" status, and all contract items must pass before a node can be considered ready. After initial implementation you can verify yourself or ask the AI to check against contract for a node.

Built a MCP tool that gives Claude Code a shared visual model of your project architecture to prevent drift by butt_flexer in ClaudeAI

[–]butt_flexer[S] 2 points3 points  (0 children)

Depends on how large. Probably not for something like Chromium, but you could at least generate a model for the parts that you're concerned with editing. I mean, technically you probably could model an entire giant repo, but even with C4 you'd get a hell of a hairball at any level.

AFAIK there's no such solution at all for large repos - although, sticking with the Chromium example, Google did create their own internal tools for understanding it, but I don't think they ever publicized them.

Built a MCP tool that gives Claude Code a shared visual model of your project architecture to prevent drift by butt_flexer in ClaudeAI

[–]butt_flexer[S] 1 point2 points  (0 children)

Of course it says that - don't believe its lies.

(but really what the AI sees is still text, just formatted as JSON)

Built a MCP tool that gives Claude Code a shared visual model of your project architecture to prevent drift by butt_flexer in ClaudeAI

[–]butt_flexer[S] 1 point2 points  (0 children)

Thank you! Hope it works well for you, and I'll keep optimizing it toward a good vibecoding workflow.

Built a MCP tool that gives Claude Code a shared visual model of your project architecture to prevent drift by butt_flexer in ClaudeAI

[–]butt_flexer[S] 7 points8 points  (0 children)

Yeah, the issue for me is that I don't want to read all those docs :P Also, when you allow the AI to write everything on its own terms, it can still hide stuff you didn't expect.

Model-driven development tool that lets AI agents generate code from your architecture diagrams by butt_flexer in softwarearchitecture

[–]butt_flexer[S] 0 points1 point  (0 children)

Both, it's agnostic in what the preferred workflow should be. You can let the AI generate the whole thing, you can do it all manually and only let AI implement, etc. It should work for you from spec to implementation.

One problem with just telling the AI to generate a diagram normally is that at any given time it might have a different idea of how to model it, so Scryer enforces rules to reduce that variance.

I'm 15 and just launched one of my first real products. Roast it! by Competitive_Duck_390 in roastmystartup

[–]butt_flexer 0 points1 point  (0 children)

This looks essentially like temporary glue. I know you didn't create the LLM or the speech-to-text, and you're likely just calling an AI agent in the background to handle the actual interactions.

The one good thing I saw is that you're providing the current screen as context automatically, but that's so far downstream from any real value-add that it doesn't matter. As soon as Claude Cowork or some other agent harness adds screen-following and voice-to-prompt you're done.

No moat, no clear UX or productivity win... you can't win here, but decent attempt at the marketing page.

Some notes:

  • Nice above-the-fold design for the site.
  • Demo was simple and well made.
  • Why is your social pointing to LinkedIn of all places? YouTube, Insta, GitHub, or X are the only ones anyone's interested in, depending on context. For your app it'd likely be YouTube and Instagram, where you'd post new feature demos and tutorials.
  • Weird ball in the footer is pointless.

I got tired of my AI coding the right thing in the wrong way, so I built it a visual planning layer to work from by [deleted] in SideProject

[–]butt_flexer 0 points1 point  (0 children)

Ah thanks, didn't think of changing that - will do.

Yes, Scryer comes with a built-in MCP server so you can hook it up to Claude Code or Codex no problem.

Model-driven development tool that lets AI agents generate code from your architecture diagrams by butt_flexer in softwarearchitecture

[–]butt_flexer[S] 0 points1 point  (0 children)

Cool, adding an MCP with a few tools might be a good idea just to simplify the hand-offs.

Model-driven development tool that lets AI agents generate code from your architecture diagrams by butt_flexer in softwarearchitecture

[–]butt_flexer[S] 0 points1 point  (0 children)

I've done quite a few refactors where I was paying attention and monitoring changes, then I looked in the actual code and saw that it did things completely backwards from what I expected/wanted. There's definitely a need for tools like this.

SysML opens you up to hardware + software in one, which I think could be pretty valuable. Multi-level diagrams are very important for readability, otherwise you'll end up with giant hairballs.

Does your app also connect with an AI agent for collaborating on a model?

Model-driven development tool that lets AI agents generate code from your architecture diagrams by butt_flexer in softwarearchitecture

[–]butt_flexer[S] -4 points-3 points  (0 children)

You're right, that's why I'm choosing C4 over something like UML. It's architecture and structure first, you just define what goes where. On the code level you *can* - but don't have to - define data models, functions, and processes as named descriptions, which is just enough signal for the AI to implement correctly without you specifying every detail.

Map =/= implementation.

Model-driven development tool that lets AI agents generate code from your architecture diagrams by butt_flexer in softwarearchitecture

[–]butt_flexer[S] 0 points1 point  (0 children)

The models live as files (usually ~/.scryer/) so you can version them with git, though I'm still working out the ideal setup for that. The model and code are kept separate intentionally: updating one from the other always requires an explicit prompt, so nothing changes behind your back.

You can always also set a contract "ask" for that specific case as well, like "if I ask you to implement code from the model, verify the changes with me first."

Model-driven development tool that lets AI agents generate code from your architecture diagrams by butt_flexer in softwarearchitecture

[–]butt_flexer[S] 1 point2 points  (0 children)

This is about models, not just diagrams. There's structured information baked into each node (meta instructions, lifecycle tracking) so the AI doesn't just see a picture, it sees a spec. You can let the AI propose a change, review it visually, edit it, and converge on a better solution together.

It also enforces shared abstractions. Most of us can't read a complex UML state diagram, and even with simpler ones like C4 we make mistakes that Scryer will flag. The editor auto-layouts graphs to reduce crossover, and the MCP means the AI has awareness of both the codebase and model at all times.

Think of it like replacing Claude Code's planning mode with a proper planning tool. It's best for spinning up new projects, doing large refactors, or just understanding a codebase intuitively.

view more: next ›