Peter Steinberger prompt engineering tips did you know claw was vibe coded? 1. btw the first Peter’s rule: “vibe coding” is a slur. 2. do not rely on one llm. use claude, codex, gemini, grok and others. some might be better at exactly one thing or just understand your prompt better. 3. say “take your time” at the end of the prompt. do not underestimate its power, believe me. 4. empathy is not only an indicator of high intelligence, it brings better results. it might seem crazy when it comes to talking to a machine, but it helps you structure your thinking. it does not mean you need to say thank you or please. it’s about small details that bring your prompt to the next level, like the third point. 5. the programming language chosen for your specific request matters. in some cases it’s a must to pick the most suitable one. for example, if you need low latency, using python instead of rust can cost you precious milliseconds. 6. Peter talks to llms instead of typing when it’s not command-related. 7. Peter changes llm configs so they do not optimize memory and disables artificially imposed restrictions. 8. Peter starts from scratch instead of endlessly editing generated code while chasing the “perfect” prompt. 9. Peter uses 4 screens at the same time. for people who are too lazy to watch the 4 hour interview with Lex Fridman, this might be a savior tweet. obviously i did not cover everything, but the most important bits are here.