Are you asking me for session logs or what? Here are two examples from just this week:
1. I created an authz lib for the app that enforces both at runtime and with types. I wanted to extend it to check not only the base DTO type shapes, but also DTOs with related record DTO properties. The context that is checked a triple of Role (e.g, admin, etc), Action (e.g., read, modify, insert, delete), and Entity.
Claude Opus initially tried to implement this enhancement by adding a role generic parameter to the DTOs (which kind of duplicates my utility type that accepts a DTO type and authz context and returns the narrowed type) and also, weirdly, wanted the role narrowing to apply only to nested DTOs. I had to throw out all that work, and ask it to enhance the existing utility auth types, and make that the authz narrowing applies to both the main DTOs and their related sub-DTOs always, at the same time.
2. I wanted to create a messaging system for the web app I'm developing. For example, where certain users with specific roles create specific entity records, admins are supposed to an email or SMS (depending in factor they registered with) plus an in-app message. These messages, especially the emails, are not just text, but formatted. Claude Opus wanted to embed formatting in the code that creates and send the messages. But this code works better when split up into various responsibilities: the message factory, the messages template, an the actual sender.
So I had it separate out the templates, implemented as JSX. Now if I want to change the templates, it is simple for me change just that, rather than hunting in some monolithic code to do that.
Are you asking me for session logs or what? Here are two examples from just this week:
1. I created an authz lib for the app that enforces both at runtime and with types. I wanted to extend it to check not only the base DTO type shapes, but also DTOs with related record DTO properties. The context that is checked a triple of Role (e.g, admin, etc), Action (e.g., read, modify, insert, delete), and Entity.
Claude Opus initially tried to implement this enhancement by adding a role generic parameter to the DTOs (which kind of duplicates my utility type that accepts a DTO type and authz context and returns the narrowed type) and also, weirdly, wanted the role narrowing to apply only to nested DTOs. I had to throw out all that work, and ask it to enhance the existing utility auth types, and make that the authz narrowing applies to both the main DTOs and their related sub-DTOs always, at the same time.
2. I wanted to create a messaging system for the web app I'm developing. For example, where certain users with specific roles create specific entity records, admins are supposed to an email or SMS (depending in factor they registered with) plus an in-app message. These messages, especially the emails, are not just text, but formatted. Claude Opus wanted to embed formatting in the code that creates and send the messages. But this code works better when split up into various responsibilities: the message factory, the messages template, an the actual sender.
So I had it separate out the templates, implemented as JSX. Now if I want to change the templates, it is simple for me change just that, rather than hunting in some monolithic code to do that.