dopetalk does not endorse any advertised product nor does it accept any liability for it's use or misuse


Our Discord Notification Server invitation link is https://discord.gg/jB2qmRrxyD

Author Topic: That old chestnut ! Keeping AI on traclk with code maintance  (Read 48 times)

Offline smfadmin (OP)

  • SMF (internal) Site
  • Owner
  • Sr. Member
  • *****
  • Administrator
  • *****
  • Admin
  • ****
  • Join Date: Dec 2014
  • Location: Management
  • Posts: 820
  • Reputation Power: 0
  • smfadmin has hidden their reputation power
  • Last Login:Yesterday at 10:24:36 PM
  • Supplied Install Member
📝 Inline Markdownv4.7.4 · 2026-11-20

Me: WOULD A generated MandatoryPSEUDOEPHEDRINECODE file help us out so you don't have to process all the code again or is this a typical context insuffiency ? and it is actully a it complex ! so, testing ain't cutting it so what would ?

Claude: [November 20, 2026, 10:24:12 AM]

Yes, it would help, and it's the piece that's been missing. Context wasn't the problem. I had all the code. What I didn't have was your requirements written down. The rule "the theme in the tag always wins" existed only in your head and in your phrase "it used to work." v4.6 broke that rule by design, and nothing anywhere said so. My tests then checked the code against my own design, so they passed.

Why testing alone fails: a test checks code against a rule. With no written rule, it checks the code against itself, and that always passes.

What would fix it is two plain-language files kept in the package.

  1. Behaviour rules. A numbered list of what LMV must do, in your words, with a clear order of priority wherever two things compete. For example:

   - LMV-T1: a theme named in the tag always loads, for every reader.    - LMV-T2: a reader's dropdown choice is remembered only on cards whose tag names no theme.    - LMV-T3: a change on one card never affects another card.

   You approve this list, and only you change it. 2. Pseudocode map. About a page describing what each function does and which rules it carries out. I read this instead of all 1,300 lines, and it's also where you review behaviour without reading code.

How they work together:

  • Every test names the rule it checks.
  • Every change I deliver lists the rules it touches before I build it, so a design that breaks one gets flagged then.
  • A rule with no test counts as a gap, and the release card shows it.

You're right that this is genuinely complex. Tag words, themes, display modes, saved browser state, the 2.0 and 2.1 template patches and Live's line-joining all multiply each other. A written order of priority is what tames that.

I can draft the LMV behaviour rules from the readme, the code and today's fixes, and mark anything I've inferred rather than taken from your own words.

friendly
0
funny
0
informative
0
agree
0
disagree
0
like
0
dislike
0
No reactions
No reactions
No reactions
No reactions
No reactions
No reactions
No reactions
measure twice, cut once

Tags:
 


dopetalk does not endorse any advertised product nor does it accept any liability for it's use or misuse





TERMS AND CONDITIONS

In no event will d&u or any person involved in creating, producing, or distributing site information be liable for any direct, indirect, incidental, punitive, special or consequential damages arising out of the use of or inability to use d&u. You agree to indemnify and hold harmless d&u, its domain founders, sponsors, maintainers, server administrators, volunteers and contributors from and against all liability, claims, damages, costs and expenses, including legal fees, that arise directly or indirectly from the use of any part of the d&u site.


TO USE THIS WEBSITE YOU MUST AGREE TO THE TERMS AND CONDITIONS ABOVE


Founded December 2014
SimplePortal 2.3.6 © 2008-2014, SimplePortal