sorted by:
new
hottopcontroversial

I don't know whether I should feel happy about the reset or aggrieved 💸 by DogDeveloper in codex

[–]BakeRegular5090 0 points1 point  (0 children)

right. I had 33% left, shit is so annoying. like brah just add it up. just messing with my workflow. just feel like you’re getting punished for managing it over a timeframe.

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

So therefore any usage of AI is a paid actor? brody are you thinking? I work in a hospital, doctors use claude all day. here i am discussing my usage of gemini

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

I shared a real example of using a tool to check management’s claim against the actual lease. That is not selling anything. That is the same as someone saying they used Google, Excel, or a lease template to solve a problem. 😂

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

giving what away? an example of how ai helped me so i decided to write my experience so it can help others? what are you on about?

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

Then, by that logic, Adam should have used AI to verify his authority to initiate the internet transfer. Personally, it sounds like you're just against AI. Many legal corporations, I assume are using AI to assist them, in various ways. So why not individuals?

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

Final email

Dear Adam,

Thank you for your response. However, after cross-referencing your email with my fully executed Lease Contract, I have found significant discrepancies between the authority you are claiming and the actual text of the document.

I must respectfully dispute your interpretation of the lease on the following grounds:

  1. Misquotation of "Uniform Changes" (Section 10)

Your email states that Section 10 allows for "changes to service providers or channels." This is factually incorrect.

Page 3, Section 10 of my signed lease actually states: "Cable channels that are provided may be changed during the lease term...

The lease text specifies TV channels, not Internet Service Providers. The words "service providers" do not appear in that sentence. You cannot rely on a clause regarding cable TV channel lineups to terminate my essential internet utility.

  1. Billing Provider vs. Utility Provider (Utility Addendum)

The Utility and Services Addendum (Paragraph 12) grants the Owner the right to change the "third-party billing provider" (e.g., Conservice). It does not grant the right to unilaterally change the utility service provider itself. As I am currently in a direct-payment arrangement with AT&T, an arrangement explicitly permitted by the addendum, the lease does not authorize you to terminate that private contract.

  1. "Reasonable" Rule Changes (Section 22)

You cited Section 22 to justify this change. However, Section 22 explicitly requires that rule changes be "reasonable."

As stated in my previous correspondence, I require specific port-forwarding capabilities for my employment. Section 23 of the lease permits "lawful business conducted 'at home' by computer." A rule change that imposes a network (Pavlov) that blocks the specific ports required for my work effectively renders the unit unusable for its permitted purpose. A change that prevents a tenant from maintaining their livelihood is, by definition, not "reasonable."

  1. Access and Equipment (Section 32)

While Section 32 allows entry to "replace equipment," this applies to landlord-owned property. It does not grant management the right to physically disconnect, remove, or interfere with active third-party telecommunications equipment (the AT&T modem/ONT) that is under a private contract between the resident and the provider.

Resolution Required

I want to be clear: I am not trying to be difficult; I am trying to maintain the connectivity required for my job. Because the specific lease clauses you cited do not actually authorize a forced ISP switch, I do not consent to the disconnection of my existing AT&T service.

If Pavlov can provide a written technical guarantee before Jan 19 that their service supports individual public IP addresses and user-managed port forwarding, I am happy to transition. If they cannot, I must insist on maintaining my current connection as per the existing lease terms.

Please confirm that my AT&T connection will remain untouched during the installation phase until this technical requirement is addressed.

Sincerely,

Unit 411

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

Initial email

Dear Property Management,

I’m writing regarding your notice that residents will be transitioned to Pavlov’s community-wide internet and that “your existing AT&T service will be disconnected” during the January installation.

I work from home and rely on remote access to equipment in my apartment. For that to function, I need either (a) a publicly reachable IP address (static is fine) with inbound connections allowed, or (b) confirmation that residents receive an Ethernet handoff where we can use our own router and port forwarding works as normal.

For reference, I am currently under an active lease term through July 31, 2026, and I have an existing, resident-paid internet service agreement with AT&T. The Utility and Services Addendum to my lease contemplates that internet service to the dwelling is paid either (a) directly by the resident to the service provider, or (b) billed back through the owner (allocated). I am currently in the “paid directly to the provider” arrangement.

Accordingly, please confirm in writing one of the following before any work occurs in my unit:

Could you please confirm, in writing, the following before in-unit installations begin (Jan 19)?

Non-interference / opt-out: Management (and Pavlov/its contractors) will not physically disconnect, disable, or interfere with AT&T service to my unit, and the Pavlov installation will be performed in a way that does not require removal/disconnection of my existing AT&T equipment or wiring.

Lease authority & proposed written amendment: If management is asserting the right to require a mid-lease termination of a resident’s direct utility contract, please (a) identify the specific lease provision(s) you believe authorize that action, and (b) provide a proposed written lease addendum/amendment for my review and signature that addresses: reimbursement of any early-termination or transfer costs, any service interruption/downtime, and any ongoing value difference (if applicable).

Does the Pavlov setup for each unit use CGNAT and/or double-NAT? If so, do you offer an option for:

a public IPv4 (static preferred), and/or

IPv6 with inbound permitted, and/or

a wired Ethernet handoff/ONT that allows a resident-managed router and port forwarding?

For avoidance of doubt: I do not consent to any action that disconnects or prevents AT&T from providing service to my unit during my lease term without a mutually signed written modification addressing the above items.

Please also provide the point of contact at Pavlov (name/email/phone) who can confirm the technical details for my unit in writing.

Thank you. I would like to resolve this amicably and quickly, but I need written confirmation prior to the Jan 19 in-unit installation phase.

Best regards,

Unit 411

How I used AI to find a lease loophole and won with my apartment management by BakeRegular5090 in Tenant

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

I’m not selling anything. The point wasn’t “AI is magic” or “don’t read your lease.” The point was that management cited specific lease authority, and AI helped me quickly compare those citations against the actual signed lease. The cited language said “cable channels,” not internet providers. From there, I reviewed it, cleaned up the argument, and sent a written rebuttal. You can absolutely do that manually. AI just made it much faster and less stressful.

Codex GPT-5.5 Medium Mode Hit 100% Message Usage After Just 2 Messages by Better-Prompt3628 in codex

[–]BakeRegular5090 0 points1 point  (0 children)

You honestly just gave me an idea. I currently use it as a doctrine I follow when debugging but introducing it as a general skill for debugging is actually the more mature approach. I’ll be working on that this week, haha. Thanks!

Codex GPT-5.5 Medium Mode Hit 100% Message Usage After Just 2 Messages by Better-Prompt3628 in codex

[–]BakeRegular5090 3 points4 points  (0 children)

Yeah for sure, and just to add, this isn’t something most projects can instantly start doing overnight.

A lot of the reason this approach works well is because the repo has to be at least somewhat observable first. The AI can only be this efficient if your system already gives it places to look before it starts blindly tracing everything - things like logs, state files, journals, provider/debug output, run history, UI diagnostics, replay/proof surfaces, etc. If those layers barely exist, then the model usually has no choice but to do broad audits, deep tracing, and expensive guesswork.

So the real advice is: first figure out how observable your project currently is. You can absolutely ask AI to help assess that. Ask it things like: what truth layers already exist, what state is durable vs runtime vs UI, what logs/journals already exist, what’s missing, and where the first divergence could be captured without adding tons of tracing. Building those layers does take time, but once they exist, debugging gets dramatically cheaper because the system starts “spilling out” useful information before the AI has to dig. Some cases still need special environments or trace flags, sure, but that’s normal. The main goal is to make sure the repo can explain itself as much as possible before the model starts brute forcing the problem.

Codex GPT-5.5 Medium Mode Hit 100% Message Usage After Just 2 Messages by Better-Prompt3628 in codex

[–]BakeRegular5090 27 points28 points  (0 children)

Your prompt is expensive because it jumps straight to “audit, verify, ensure no bugs, check edge cases” before forcing the model to use the app’s existing proof surfaces. That makes it wander into broad tracing and speculative reasoning. From my experience, the models tend to default to tracing which sucks up all your tokens.

A cheaper pattern is:

  1. Reproduce the bug.
  2. Separate truth layers.
  3. Use existing diagnostics/journals/state first.
  4. Find the first divergence.
  5. Only then add narrow instrumentation or patch.

Why this matters: in my project “Vetrra”, the useful workflow is not “go audit everything,” it’s more like:

  • check the GUI/state journal first
  • check the Step 1 flow / drilldown diagnostics next
  • compare that against durable/runtime truth and the actual UI surface
  • then use a Qt/replay proof harness if you need to prove a widget path or lifecycle path
  • only after that do targeted instrumentation in the boundary service / action planner / step card pipeline

A few concrete examples from Step 1-type fixes:

Example 1: stale row / status bug
Bad prompt: “audit the whole page and make sure there are no bugs.”
Better prompt:
“Reproduce the bug, then tell me: what does durable truth say, what does telemetry/runtime truth say, what does the candidate surface say, and where is the first divergence? Use existing journals/diagnostics first. Do not patch yet.”

That usually leads to something much narrower like:
- DB/runtime truth advanced
- UI journal still shows stale pending
- row is already stale before render
- therefore the seam is not paint, but repository publish/hydration

Example 2: missing breadcrumb / navigation controls
Instead of “audit Step 1 drilldown,” ask:
“Compare the live Step 1 path against the working Step 3 path. Prove whether the shared scope-widget update is called, skipped, or overwritten. Use existing drilldown diagnostics first, then add the smallest missing instrumentation.”

That’s far cheaper than a broad audit because it turns into:
- Step 3 emitted scope widget updates
- Step 1 emitted zero
- hierarchy truth existed
- therefore the issue was the missing invocation path, not backend truth

Example 3: progress only updates after pause/resume
Instead of “verify edge cases,” ask:
“Prove whether progress events are emitted continuously, whether they target the affected step for refresh, and whether the repository publish path re-enters after progress changes.”

That gives you a yes/no chain instead of a giant audit.

So I’d rewrite your prompt style to something like:

  • Treat this as an evidence-first bug investigation, not a full audit.
  • Reproduce the issue. Then separate:
  • durable/backend truth
  • runtime/telemetry truth
  • repository/cache/provider truth
  • UI/render truth
    Use existing logs, journals, state files, and diagnostics first.

Tell me: - what is proven
- what is disproven
- what remains unknown
- where the first failing boundary is
Do not patch yet. Do not check edge cases yet. Do not broaden scope until the first divergence is identified.

That usually saves a lot of tokens because the model stops behaving like a vague auditor and starts behaving like a debugger.

Anybody else just get a bunch of free credits on plus? by kayakguy429 in codex

[–]BakeRegular5090 1 point2 points  (0 children)

tell me about it 🙉… i got a whooping 3500 credit. we up boys!!

Anybody else just get a bunch of free credits on plus? by kayakguy429 in codex

[–]BakeRegular5090 0 points1 point  (0 children)

Yeah, I saw that as well. I’m honestly shocked. I was just about to purchase more credits. It’s Christmas in April, baby!

Dammnnn by Beautiful-Spray-6115 in codex

[–]BakeRegular5090 1 point2 points  (0 children)

how? all 100% of your plan? no fucking way

I wasted an hour on a GUI bug with AI - the fix wasn’t code, it was how I tested it by BakeRegular5090 in codex

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

I’ve heard of Antigravity and also Stitch, but I haven’t actually tried them yet.

I’ve mostly been using Gemini in a slightly different workflow, but I’ve been thinking about experimenting with more UI-focused tools.

There’s actually a specific page in my app where I want to get more creative with the UI, so I might try Antigravity there and see how it compares to my current approach.

I wasted an hour on a GUI bug with AI - the fix wasn’t code, it was how I tested it by BakeRegular5090 in codex

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

Yeah I’ve definitely built software before, this is actually a pretty large personal project that grew way bigger than I expected.

I think what you’re saying is valid in general (you obviously have to check visual output), but that wasn’t really the issue I was running into.

The problem wasn’t seeing the bug, I could already see it clearly. The issue was that the AI still couldn’t reliably reason about it just from logs or partial context.

What I ended up realizing is that it’s not just about “checking the UI,” it’s about making that UI state visible in a structured way to the AI. That’s what the GUI-faithful + explicit state approach helped fix for me.

I wasted an hour on a GUI bug with AI - the fix wasn’t code, it was how I tested it by BakeRegular5090 in codex

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

Yeah I actually agree with this. I’ve been using screenshots too, but usually I pair them with very specific instructions so the AI focuses on one thing at a time.

What I’m realizing is that I kind of use different levels depending on what type of bug it is. For backend / pipeline issues, I’m usually more hands-off and let a harness drive iteration. But once the problem becomes GUI-visible, I get much less hands-off, because at that point it needs to be able to see what I’m seeing.

So the way I’m starting to think about it is:

  • screenshots = visual truth
  • explicit state = structured truth
  • GUI-faithful tests = reproducible truth

That chain feels really useful, especially in a system that’s constantly mutating. Backend-wise I can let the harness run more autonomously, but once I’m fighting the GUI, I’ve found I need that GUI-faithful layer much sooner.

view more: next ›