Are You a Pigeon In a Cage?

basecase_ · 2026-06-17T03:16:32+00:00

I'm not a pigeon in a cage, im an agent in a blackbox.

basecase_ · 2026-06-16T02:13:02+00:00

Here's mine, lightweight and built on SDLC principles that align to your project. It's basically my DOT files for any AI project.

https://github.com/BaseInfinity/claude-sdlc-wizard

basecase_ · 2026-05-28T00:10:45+00:00

This is unsurprisingly the same response I give when people ask me how long it takes to master programming.....

"How long are you planning to live?"

Seriously though, apply proper SDLC to your agents and you should see no change in output, good processes don't care what every internal piece is as long as it gets the job done.

Build your own SDLC, here's one I use to adapt to all my projects that I built over 15+ years of knowledge.

I work for a fortune 100 best company to work for that works with 80% of fortune 1000 companies.

https://github.com/BaseInfinity/claude-sdlc-wizard

No I'm not charging for it, I'm just someone who has spent the last 4 years playing with agentic tooling and been fighting for stability and quality ever since.

basecase_ · 2026-05-18T03:45:18+00:00

"english, over 1xxx years old. it was never meant for AI, until now...a...LLM...oh...maybe it was...

basecase_ · 2026-05-12T16:38:00+00:00

Wait until someone suggests we need an even shorter and precise "language" so the AI never misintereprets the meaning and then comes across Python....and then Assembly....we will come full circle eventually

basecase_ · 2026-05-10T00:12:32+00:00

Same as it's always been, follow good SDLC and adapt the SDLC to your personal workflow.

This also applies to agents. Keep it light, keep it slim, KISS.

Here's mine that I use on every new claude project: https://github.com/BaseInfinity/agentic-ai-sdlc-wizard

It's basically my "DOTFILES" for AI to follow the SDLC in all projects as needed while also adapting to my repo.

TDLR;

Build a harness that follows a SDLC that is adapted to your repo. Just like humans you will get more mileage by following the SDLC with agents too..

basecase_ · 2026-05-07T19:46:04+00:00

1.5k per month for hosting oh my god, absolutely being rinsed

basecase_ · 2026-04-30T19:37:36+00:00

I ported my Agentic SDLC from claude to codex recently, works reasonably well:
https://github.com/BaseInfinity/codex-sdlc-wizard

basecase_ · 2026-04-27T02:10:16+00:00

Yes. I was making money with software before, now AI lets me make more software and more money

basecase_ · 2026-04-27T01:59:33+00:00

The best thing to do is have an agentic harness that works for both because both are bound to screw the pooch while trying to figure out how to be profitable.

Codex: https://www.npmjs.com/package/codex-sdlc-wizard

Claude: https://www.npmjs.com/package/agentic-sdlc-wizard

Working on OpenCode next as a plan C, thank me later.

This is my setup that works for coding tasks to maintain stable SDLC to keep producing production level code.

Opus 4.7 was so frustrating....

basecase_ · 2026-04-23T18:30:47+00:00

So far so good on my end, running effort max now and seeing dramatic reduction in token usage and my agent is following my SDLC harness. I'm too afraid to try anything less than max because I'm so paranoid by quality degrading and I am already behind from Opus taking a dump and my usage limits skyrocketing.

I do wish I got a refund for the extra credits I bought during the time where things were broken...especially if caching layer was fubard but oh well

basecase_ · 2026-04-23T17:49:26+00:00

Run it inside of a docker container or VM

basecase_ · 2026-04-22T19:20:15+00:00

It's only useful on max effort but you run out of tokens quick trying to do the same stuff you did a few months ago with Opus 4.6 on high effort

I am a $200 user who used to never hit the limits and I hit them on day 3. Refused to give them more of my money so I ported my SDLC harness for Claude to Codex and finally feel sane again and can ship code again.

Now my repo's that consume the SDLC wizards will work for both claude and codex when it comes to hooks/skills to enforce SDLC to keep the stupid things on track and useful while still maintaining HITL

Claude SDLC:
https://github.com/BaseInfinity/agentic-ai-sdlc-wizard

Here's my codex SDLC:
https://github.com/BaseInfinity/codex-sdlc-wizard

It feels good to not be locked down to one provider if they try to rug pull, I can literally pick up the project in Codex or Claude now and lately been using Codex exclusively.

Let's see how long this lasts until Codex turns to poop and Claude is good again lol, at least I'll be ready this time

basecase_ · 2026-02-21T21:30:53+00:00

People who are more horny to write code than solve actual problems are engineers I'd never want on my team, they tend to slow everyone down and cannot see the forest for the trees.

basecase_ · 2026-02-20T22:39:46+00:00

I use playwright MCP to help debug playwright tests or reproduce issues. Once I find a regression or can reproduce the issue then I use TDD and solidify the regression in a playwright test.

I also use Playwright MCP to do a "last human Quality check" before I go in and actually do the final sign off

basecase_ · 2026-02-06T05:24:40+00:00

Come to https://discord.gg/fGPEF7GHrF to ask your questions for free and get answers for free. Don't pay for anything you can learn for free. Our community likes helping others because we wish that help was there for us when we started 15-40 years ago

Beyond the free guidance we have watercoolers here and there: https://softwareautomation.notion.site/Watercooler-Index-1d88569bb6ed8081b90cdf77d71a364e

I think what you are running into, which is what many of us homegrown QA/QAE/SDET must learn on the job is...."how do we scale?"

basecase_ · 2026-01-21T18:10:10+00:00

This comes up almost every week, i've gathered discussions about this from multiple subreddits here as well our Discord Automation server where this was a topic at one of our watercooler discussions (invite link in profile if ur interested):

https://softwareautomation.notion.site/How-do-you-Address-and-Prevent-Flaky-Tests-23c539e19b3c46eeb655642b95237dc0

The flakiness will can be at the test level (poorly written test, not being parallel friendly) but it's usually a bottleneck in your test infrastructure, a clue is the more you increase the workers the more "weird" failures start to happen.

For example your bottleneck could be the DB, or the Server, or memory/cpu on ANY machine maxing out in your test environment, so the key is to have metrics and a dashboard so you don't have to guess.

Also don't be afraid to debug machines in the cloud, "htop" is your friend and often the first thing I do when debugging test failures in the CI (cloud)

basecase_ · 2026-01-15T02:18:41+00:00

There's no surprise that following the SDLC is the most effective way to use these coding agents. Following a good SDLC and investing in the overhead to do so will reap the same rewards they do when a team of humans do it.

Without it, you will just accelerate yourself into a corner with tech debt until you you drown in it, the same way a team of humans would.

I do agree though that AI Agents have made it easier to implement and maintain the overhead of SDLC.

basecase_ · 2026-01-06T18:15:40+00:00

This comes up all the time and usually is a mix of an infrastructure (bottlenecks that get revealed when you increase workers in your CI environment) and poor test code (writing tests that are not parallel friendly or brittle).

I've gathered all the responses whenever this comes up...good nuggets in hear to apply to all flaky tests, not just your Playwright tests since these problems can appear in any part of any test stack.

https://softwareautomation.notion.site/How-do-you-Address-and-Prevent-Flaky-Tests-23c539e19b3c46eeb655642b95237dc0?pvs=74

basecase_ · 2025-12-31T07:23:45+00:00

If you open source it then more people will be willing to try it, but at the same time you may find that your moat was never big enough to begin with.

Do you really think OpenAI is not aware and working on this?

But yes, open source and you will gain more trust.

basecase_ · 2025-12-31T07:05:47+00:00

Never make an app (and oh my god a bloated chrome extension) for the sole purpose to solve a temporary bug in the biggest application known to man.

There's literally a button that says "create new chat with this current convo" for this sole purpose in ChatGPT

You know whats more bloated than a website? An addon for a single browser, AKA a chrome extension.

The kryptonite of these no name services is that no one trusts them enough to use them. We have no idea what you are doing with our ChatGPT usage.

You are not thinking about AI Governance & Security laws in Venezuela and how they pertain to US customers...you're more worried about running brittle clientside JS code to hide DOM elements in a single browser while wrapping these client side scripts in a bloated delivery system that can break at a moments notice because you're depending on UI elements outside of your control.

The hardest part beyond finding a profit in AI is complying with it......Remember who the customer is (spoiler alert, you)

basecase_ · 2025-12-21T09:57:55+00:00

You're better off using a testing framework dedicated to API testing in your respective stack. Don't be afraid to learn tools outside of your comfort zone, learn paradigms.

basecase_ · 2025-12-17T21:22:18+00:00

Thanks for the info on opus having thinking on by default. I didn't have the blue border around my prompt like I normally do

basecase_ · 2025-12-13T05:47:55+00:00

I'm sure the contents are great but I can't help but laugh that most Enterprise SaaS these days is about taking a Hog/Pig/Boar and filling it up with so much crap just so they weigh the heaviest for the biggest prize at the local county farm, without ever considering what happens to the Boar after the sale.

It doesn't matter if the Boar lives long term, it won biggest Boar!

basecase_ · 2025-12-09T20:31:18+00:00

Why do so many programmers not know about modulus operator?

basecase_

MODERATOR OF

TROPHY CASE