Aris Adamantiadis 
💲PaidI don't want to be a "akshualy I'm a prompt engineer" type of person, but my impression while coding with Claude is that knowing what you're doing and managing this as you would do a real dev project immensely helps at writing relevant prompts and giving right directions.
Andreas Schneider@aris It can do nice things for you, but I also watched it punching security holes into Software. You need to unterstand what it is doing too.
@cryptomilk Totally. I tried designing a new telescope imaging system. The pattern I use is
- describe my problem, the hard requirements, the type of design I'd like and what I don't want.
- ask for ideas how to solve the problem
- Explain the design
- Explain the tech stack it wants to use
- Go
While giving my input at all steps. Sometimes I don't know the tech it wants, I guess that's my blind spots.
@aris I start with a markdown file, I write down all the things I want. Then I let it read it, do research and update the document. Then I read it and refine it and reiterate that way till I have all edge cased and a design I think is sound and safe. Then I start with implementation is small steps. I often work for several days on that markdown file.