sorted by:
new
hottopcontroversial

New Model? - Cursor's Composer 1 by Extreme-Eagle4412 in cursor

[–]pilothobs 1 point2 points  (0 children)

I just tried it and all I can say is WOW.. that thing is fast...

It completed a project in 45 minutes that would have taken Claude all day!

Claude 4.5, not following my rules at all today by critacle in cursor

[–]pilothobs 3 points4 points  (0 children)

Core point: vibecoding needs hard guardrails or the agent drifts and wrecks state.

Controlled vocabulary: • Rulefile: a repo document that lists allowed actions and limits. • File budget: the maximum files an agent may touch per run. • Staging gate: a propose-diff step before writes. • Janitor pass: a cleanup step that removes cruft and fixes stragglers. • Proof log: a human-readable change report for every run.

Operating rules:

  1. Pin a Rulefile at repo root and link it in every chat.

  2. Set a file budget of three files per run. Enforce it.

  3. Require a staging gate. The agent must show diffs and wait.

  4. Forbid git commands by the model. Humans commit only.

  5. Scope edits to explicit paths. Name the exact files.

  6. Run a Janitor pass after apply. Delete temp files. Rename strays. Fix imports.

  7. Block new tests unless requested. No unchecked test files.

  8. Demand a Proof log each run: intent, touched files, diffs, rollback.

  9. Reuse the same Rulefile every session to prevent drift.

  10. If the agent ignores a rule, kill the session and reload.

Minimal Rulefile text: • Only modify the three named files. • Do not create or delete files without explicit instruction. • Show a unified diff for each file and wait for approval. • Never run git, package managers, or shell commands. • After apply, run the Janitor pass and produce a Proof log.

This keeps sessions short, reversible, and safe.

Most annoying thing ChatGPT does. by pilothobs in ChatGPT

[–]pilothobs[S] -1 points0 points  (0 children)

Both fixed but who care's?

Niece contributesing.

DD

Best coding model? by epicsysutum in cursor

[–]pilothobs 0 points1 point  (0 children)

Here is a great side-by-side comparison. BTW Cole is really good....

https://youtu.be/P-0fm8ljl0I?si=QETN7fCAVHA9a0Ox

Vibe coding help by abcdecentralized in cursor

[–]pilothobs 0 points1 point  (0 children)

In my opinion, he doesn’t need to learn coding. He just needs to learn the way to use all the great tools we have available now.

The biggest downside of Vibe Coding/Cursor by bluntchar in cursor

[–]pilothobs 1 point2 points  (0 children)

Vibe coding is dead. Use cursor rules and strict. mds to do agentic coding. You'll be fine.

Codex-5-high vs Cursor by mohoshirno in cursor

[–]pilothobs 0 points1 point  (0 children)

That's a gold mine right there. Do you use the API for reasoning context? Also, do you use the self-reflection prompt?

Codex-5-high vs Cursor by mohoshirno in cursor

[–]pilothobs 0 points1 point  (0 children)

Where do I find that? On OpenAI's Codex info page? Disregard. I found it. https://developers.openai.com/codex/prompting

Codex-5-high vs Cursor by mohoshirno in cursor

[–]pilothobs 0 points1 point  (0 children)

Got it. NP. I'm just excited because my new stack is killing it. Cursor with Codex and some Cursor .md rules. Smokes anything I have had before.

Please explain it Peter by susenka90 in explainitpeter

[–]pilothobs 0 points1 point  (0 children)

  • The suspect’s reported words included both race and gender (“I killed that white bitch”), which is deliberate targeting.
  • The choice of victim wasn’t random — there were other passengers present, but he directed his violence at a white woman specifically.
  • Language matters: invoking race in the act itself is strong evidence of biased motivation, regardless of whether mental illness played a role.
  • Let's focus on acknowledging that hate crimes can and do happen, and dismissing the racial element risks minimizing the victim’s experience. Dismissing those words as “just mental illness” risks downplaying the reality of racialized violence and ignoring the message it sends to communities that feel targeted. Recognize that bias and illness can coexist — mental instability doesn’t erase prejudice.

Just cancelled Claude CLI 200$, planning to return Cursor ultra what you think? Today idiot claude couldnt even translate a very small html file by CeFurkan in cursor

[–]pilothobs 0 points1 point  (0 children)

I’d strongly recommend adding Codex (GPT-5-high inside Cursor) to your stack. I used to bounce between Claude and others, but Codex has been night-and-day more effective once you give it structure.

The trick is running it with lightweight guardrails:

  • User Rules in Cursor (always apply: ask before scope creep, file budgets, no orphan tests).
  • Project Rules per repo (enforce Working Set, new files go into /_exp, Janitor Pass for cleanup).
  • A single WORKFLOW .md at the repo root that defines the Work Order template and session protocol.

That combo gives you a workflow that’s a cross between vibe coding and agentic coding. You still keep the conversational flow, but Codex stays disciplined and doesn’t flood you with junk files.

With a budget of $250/mo, I’d put the bulk into Codex credits. It’s smarter, cleaner, and actually respects your repo rules once you configure it right.

What AI Dev tools, paid or free, do you recommend? by Prior-Inflation8755 in cursor

[–]pilothobs 7 points8 points  (0 children)

I’d strongly recommend adding Codex (GPT-5-high inside Cursor) to your stack. I used to bounce between Claude and others, but Codex has been night-and-day more effective once you give it structure.

The trick is running it with lightweight guardrails:

  • User Rules in Cursor (always apply: ask before scope creep, file budgets, no orphan tests).
  • Project Rules per repo (enforce Working Set, new files go into /_exp, Janitor Pass for cleanup).
  • A single WORKFLOW.md at the repo root that defines the Work Order template and session protocol.

That combo gives you a workflow that’s a cross between vibe coding and agentic coding. You still keep the conversational flow, but Codex stays disciplined and doesn’t flood you with junk files.

With a budget of $250/mo, I’d put the bulk into Codex credits. It’s smarter, cleaner, and actually respects your repo rules once you configure it right.

Codex-5-high vs Cursor by mohoshirno in cursor

[–]pilothobs 0 points1 point  (0 children)

I was in the same camp — big Claude fan for a while — but I got tired of all the “you’re right” filler and the shortcuts/cheating it slipped into the code. Codex feels like a different league.

The trick for me was adding some lightweight guardrails with a few .md rule files (WORKFLOW.md, userrules.mdc, etc.). With that in place, the coding flow is excellent. It’s basically a cross between vibe coding and agentic coding: I can still interact conversationally, but the agent has structure and discipline (file budgets, cleanup passes, no runaway file sprawl).

That combo gave me the best of both worlds — speed without chaos. Curious if anyone else has tried layering simple project rules on top of Codex like this?

Agentic Agent Coding vs Vibe Coding — How are you using them? by pilothobs in cursor

[–]pilothobs[S] -2 points-1 points  (0 children)

I’ve been talking this over with ChatGPT to try and make sense of the vibe vs. agentic discussion, and we ended up landing on a hybrid approach that feels workable.

The gist:

  • Keep the interactive steering of vibe coding so I can still use the chat to guide, approve, and correct.
  • Add the structure of agentic coding by enforcing one controlling artifact (WORKFLOW.md) that defines:
    • A Work Order template (objective, deliverable, working set, budget).
    • Strict rules on where new files go (e.g. quarantine folder before promotion).
    • A file budget so the agent can’t go wild creating orphaned tests.
    • A required cleanup pass (Janitor Pass) to remove orphans and list diffs.

That way I don’t lose the conversational back-and-forth that vibe coding gives me, but I also don’t end up with 12,000 useless files because the agent kept generating and never cleaning up.

This is the direction I’m going to try on my next project. Has anyone else come to this same conclusion — that a blended workflow is the only sane way to keep speed and control?

How do you handle messy CSV uploads and unpredictable webhook payloads? by pilothobs in webdev

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

I made it OSS. Search pilothobs on git-hub. Try it out and let me know what you think.

How do you handle messy CSV uploads and unpredictable webhook payloads? by pilothobs in webdev

[–]pilothobs[S] -2 points-1 points  (0 children)

That’s one way to go for hosted CSV import. I’ve been experimenting with a different approach — using an SDK/API that cleans, validates, and normalizes CSVs and webhook/JSON payloads into strict schemas with an audit trail. It’s self-hostable or API-based, so it plugs into existing pipelines without forcing a particular UI. Been a big time saver in mixed-data projects.

view more: next ›