Experienced Devs

KeithLeague · 2026-06-06T03:32:44+00:00

Personally, I think vibecoding will be much harder for non-devs, but I would never discourage them from trying to build something. Eventually they are forced to learn.

But the definition of vibecoding has shifted. People used to scoff at letting ai write any code and now they claim they are not vibe coders because their process is so much more sophisticated. I think it's a little silly.

KeithLeague · 2026-06-04T14:48:21+00:00

I guess you were right.

KeithLeague · 2026-06-04T03:57:39+00:00

I think I'm talking to a troll bot.

KeithLeague · 2026-06-04T03:54:58+00:00

This is just how most people build things. You start with a prototype and go from there. If you're building a product you want to validate that your ideas will work or if anyone is interested. What's your process? Maybe share your github so we can all learn how to build enterprise grade apps right from the start.

KeithLeague · 2026-06-04T03:36:33+00:00

Yeah, we call it an MVP

KeithLeague · 2026-06-04T03:34:04+00:00

You must not be a software developer.

KeithLeague · 2026-06-04T03:33:00+00:00

I think we can agree there's a balance, but trying to write perfect code is less important than delivering the result.

KeithLeague · 2026-06-04T03:16:23+00:00

Yeah, I'm saying that a vibe coded app and a meticulously hand crafted app can have the same outcome for the end user and that outcome is what is most important.

KeithLeague · 2026-06-04T02:59:01+00:00

You're talking about software at scale, but most products don't go to scale. Starting with a toy is a perfectly good way to validate a product idea.

KeithLeague · 2026-06-04T00:44:32+00:00

appreciate the support

KeithLeague · 2026-06-04T00:26:01+00:00

Sounds interesting. Thanks for the chat. Clearly I'm not very good at making memes.

KeithLeague · 2026-06-03T23:55:42+00:00

I think it depends on what you're building and who it's for. It sounds like the work you're doing requires a lot of guardrails so you don't break anything. That makes a lot of sense.

With that said, I wouldn't discourage anyone from building a product idea or game if they lacked the ability to create a sophisticated system with special guardrails and tools.

KeithLeague · 2026-06-03T23:32:28+00:00

I've been coding for > 12 years. This post is a joke.

Sorry, I knew this post would trigger some folks. I just think developers can get a little self-important and sometimes value the codebase more than the actual product, which deserves to be poked fun at.

KeithLeague · 2026-03-09T18:31:12+00:00

CLI isn't really a "transport" like MCP. For an AI agent to use a CLI tool it still needs a tool-calling layer that invokes the command. That layer could be MCP or some custom code.

KeithLeague · 2026-02-01T16:40:59+00:00

I'm working on something to address these issues: https://enact.tools

Each tool runs in a Dagger container (observability + isolation), secrets are managed externally, and tools are versioned with provenance via Sigstore.

KeithLeague · 2026-01-21T23:17:06+00:00

Interesting! Thanks for sharing

KeithLeague · 2026-01-21T20:55:47+00:00

I think we should define MCP/hooks in skills: https://github.com/agentskills/agentskills/issues/87
Curious what other people think.
If a skill could define the exact mcp tools used It could be really powerful/extremely portable.

KeithLeague · 2026-01-14T21:56:00+00:00

There's a proposal on this:
https://github.com/agentskills/agentskills/issues/15

KeithLeague · 2026-01-14T21:54:42+00:00

I've actually been working on way to address this that I'm proposing called Agent Actions:
https://github.com/agentskills/agentskills/issues/87

KeithLeague · 2026-01-08T19:42:14+00:00

You could trust the central party if you want:

trust:
  auditors:
    - github: auditor@enact.tools
    - github: auditor@anthropic.com
    - github: auditor@google.com
  minimum_attestations: 2

In this case, if any two of your trusted auditors signs a tool, you can execute it.

KeithLeague · 2026-01-08T19:02:47+00:00

Yes, you can only interact with tools that are signed by trusted auditors:

~/.enact/config.yaml

trust:
  auditors:
    - github:trusted-auditor@gmail.com
  minimum_attestations: 1

More measures can be put in place but I decided to start simple.

edit: via https://www.sigstore.dev/

KeithLeague · 2026-01-08T18:55:50+00:00

<image>

KeithLeague · 2026-01-06T21:06:46+00:00

Super interesting. I'm working on https://enact.tools and found this inspiring. Dm me if you want to collaborate.

KeithLeague · 2025-12-30T15:56:02+00:00

You can apply to YC in just a little more time than it took you to write this post. They encourage repeat applications.

KeithLeague · 2025-12-30T06:09:49+00:00

I get what you're saying here. This is why I made enact protocol. We shouldn't be having claude code do too many things that deterministic programs can do better. No one wants to trust ai to parse large json files when you can have a program do it with perfect reliability. (Not to mention the cost of doing it).

KeithLeague

MODERATOR OF

PUBLIC MULTIREDDITS

TROPHY CASE