A Web Developer based in Belgium, specialized in PHP & JS development
- php - js - SilverStripe
Ah yes, six months later, nobody remembers the pain :-) but adding a timestamp is not a real solution either: a rule should have a recoverable reason for existing. And that's the point, because once your agents.md grows too big, then you might need to refactor it. What stays is a simple rule, and a good reason for it. This rule might move to another document, or be merged with another one.
While I might just as well use Typescript since I have all the tooling in place, it would bring very little benefits over using a couple of jsdocs tags (for me, and for my use cases, anyway.. i can very well understand in larger projects or with a team that typescript makes more sense). Using typescript also forces you to follow updates or potential breaking changes... one less thing to worry about for me :-) But maybe some day I will see a decisive benefit and decide to switch, who knows :-D
My use case is that I needed to synchronize a product database. Basically, I get a really big set of data, that needs to work offline. My first naive approach was inserting them one by one, basically replicating one row per product. But that didn't work, so I ended inserting them as "pages" then dealing with it in memory. I'm not saying this works for every situation, but for me, it made such a big difference. The app feels really instant and that works really well :)
