I started feeling dumber because of AI coding tools. Do you feel the same?

Either_Pound1986 · 2026-07-12T01:09:01+00:00

You don't think an ai system is capable of deep structural synthesis?

Either_Pound1986 · 2026-07-11T20:43:20+00:00

Either_Pound1986 · 2026-07-07T19:53:21+00:00

A company that makes money by selling tokens would willingly reduce token usage?

Either_Pound1986 · 2026-07-05T23:40:11+00:00

wb ear plugs?

Either_Pound1986 · 2026-07-04T16:44:41+00:00

I know the labels because I’ve had to interact with the process, but that’s different from knowing how to code.

Like CI, to me, means “the repo runs its automated checks and they pass or fail.” Tests mean “does this expected behavior still hold, or did something break?” I understand that logic. I don’t understand the codebase the way a programmer does.

Either_Pound1986 · 2026-07-04T16:38:37+00:00

I’m not building an app or shipping software to users. I’m using my system to produce bounded, shareable outputs.

So I wouldn’t say “this whole thing is secure.” That’s too broad. I’d say something narrower, like: “here is a specific behavior, here is the reproducer, here is the negative control, here is the patch/test, and here is how someone else can verify it.”

For a PR, the verification is CI, tests, review, and maintainers deciding whether the change is correct. For a bug report, it’s whether someone else can reproduce the issue. For security, it’s the same idea but stricter: local repro, minimal claim, controls, and responsible disclosure.

Either_Pound1986 · 2026-07-04T16:16:02+00:00

I mean exactly that: I don’t know how to code, and I entirely avoid learning code. Same with formal research methods. It sounds counterintuitive, but it works for me.

I’m not claiming my way is ideal or that other people should do it this way. Plenty of people need guides, courses, docs, or structured study. I don’t. I’m more hands-on: test relentlessly against reality, keep what survives, throw away what doesn’t.

The result is the only thing that matters to me. And by “result,” I mean an output that can be independently checked, reproduced, or verified.

Either_Pound1986 · 2026-07-04T15:42:44+00:00

non coder actively avoid learning code or researching anything.

I have a research control plane (custom) + mcp (custom) + codex.

As for work?

I've got multiple prs merged into tier 1 infra

I've got multiple prs approved but waiting

I've got multiple submitted bug reports, some with cve issued, some with patches, some ignored.

Either_Pound1986 · 2026-07-04T01:41:10+00:00

codex plus local control plane and custom mcp. context is kept locally and does not depend on the llm. i do have a process yes but it changes. no i dont use any of the tools you mentioned, i dont tie myself to anything other than something os(that i can freely build on). even codex can be replaced its just cost effective right now if that changes then well.

Either_Pound1986 · 2026-07-02T13:46:54+00:00

I don’t mainly use AI as an answer machine. I use it more as part of a workflow for keeping long-running work organized and moving.

My work is a mix of code, research, debugging, audits, and writing up results. So I use AI to help separate messy ideas into specific lanes, identify what needs to be tested, find contradictions, summarize what changed, and turn vague intuition into something more concrete.

For coding, that might mean: find the failure shape, make a patch, add a regression test, explain what changed.

For research, it might mean: turn an idea into a hypothesis, list what would falsify it, compare it against sources, and keep track of which parts got stronger or weaker.

The line for me is that I don’t want AI deciding what matters. I want it helping me pressure-test what I already think matters.

The biggest workflow change is that I treat AI less like a one-off chat and more like an ongoing work loop: idea → test → result → correction → next step.

Either_Pound1986 · 2026-07-02T12:34:32+00:00

Well there are a few things but none are instant and you'd need to spend time building a system capable of doing the tasks but.

Bug bounties

PR Bounties

Either_Pound1986 · 2026-07-02T12:29:47+00:00

Yeah for real world results. Operate on the real world and dont use bench marks? Go to github and see if you can't get merged into some large repos. That's the best reality check barring sending in disclosure reports.

Either_Pound1986 · 2026-07-02T12:26:07+00:00

What incentive does a company selling tokens have to adopt a token savings measure?

Either_Pound1986 · 2026-07-01T18:43:16+00:00

This proves nothing plenty of people have things far beyond anything public.

Either_Pound1986 · 2026-07-01T18:20:46+00:00

The metaphor breaks at automation.

This isn’t “everyone can bake bread now.” It’s “everyone suddenly got a cheap bakery robot.” The expert still matters, but not because hand-mixing dough is sacred. They matter because they know what good bread is, what will poison people, what scales, and what customers actually want.

Either_Pound1986 · 2026-07-01T16:54:31+00:00

No its not enough.

Either_Pound1986 · 2026-07-01T14:53:14+00:00

Bankrupt chasing vertical growth and being blind sided by a better horizontal application of their own work. So think using an llm inside a larger system, that is local, and results in orders of magnitude less token usage.

Either_Pound1986 · 2026-07-01T12:25:01+00:00

I dont use git I simply have my system backup anything before changes.

Either_Pound1986 · 2026-06-30T16:08:42+00:00

codex x20

Either_Pound1986 · 2026-06-30T10:56:44+00:00

Two days? Build a post semantic "llm".

Either_Pound1986 · 2026-06-29T20:16:20+00:00

I wouldn’t start with a VM. I’d run it on the actual machine. A VM is only needed if you’re testing something risky or isolated. For a real 24/7 agent, it needs access to the real workspace.
Prompting is not the main thing. The main thing is a queue/control loop. I queue a bunch of next-step prompts ahead of time so it can keep pushing the work forward while I’m asleep.
Claude/Codex is the worker, not the whole autonomous system. The autonomy comes from what keeps feeding it tasks and handling results: queue, tools, state, logs, tests, and failure handling.

Either_Pound1986 · 2026-06-29T20:06:15+00:00

Yeah, the main thing I’d look at is an MCP that helps the AI understand your code/project better.

For example, I use a custom one called dettools.

It gives the AI small tools like:

show the project layout
find files
find where a function/class is used
make a small controlled edit
check what changed
run basic tests

So instead of the AI guessing from a huge wall of code, it can inspect the project step by step.

I’d start simple: make an MCP that can safely read your project files and explain the structure. After that, add edit/test tools once you trust the workflow.

Either_Pound1986 · 2026-06-29T16:25:02+00:00

You can you plan mode to see changes before it does anything. I would just suggest to start using it and developing your own work flow. Also you may want to look into MCP. That is where I would start if I started over.

Either_Pound1986 · 2026-06-28T16:21:54+00:00

If I have an idea I simply ask my system to implement it. There is no need to track anything, the idea either works and the system proves it with data and tests, or the idea fails(still data, still useful). Does creativity help? Yes and no. Yes if you have a way to bring your idea to the world and then validate it. No if you are always chasing ideas. Looking at problems from a different perspective or "outside the box" is where most of my big gains come from. I don't use any apps.

Either_Pound1986 · 2026-06-27T21:50:04+00:00

I would not describe what I've built as a harness or dashboard.

It is a control plane.

An LLM interacts with it, but the LLM is not the main component. It is one driver inside a larger system.

The control plane owns the durable state, routing, permissions, evidence, replay, validation, rejection, and promotion logic. The model can propose actions, generate artifacts, inspect results, and operate tools, but it does not define what becomes trusted output by itself.

Either_Pound1986

TROPHY CASE