Mo
396 posts

Mo
@heyitsmo_1
Building in public, Sharing tools and knowledge.

Me to Claude: "Make no errors. DO NOT HALLUCINATE. YOU ARE AN SOFTWARE ENGINEER EXPERT"

𝘆𝗼𝘂 𝗱𝗼𝗻'𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗯𝗲 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝘁𝗼 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿 𝗽𝗿𝗼𝗺𝗽𝘁𝘀. prompt engineering is a real discipline. it needs 3 things: 1. 𝗗𝗼𝗺𝗮𝗶𝗻 𝗞𝗻𝗼𝘄𝗹𝗲𝗱𝗴𝗲 - understand your problem deeply 2. 𝗠𝗼𝗱𝗲𝗹 𝗨𝗻𝗱𝗲𝗿𝘀𝘁𝗮𝗻𝗱𝗶𝗻𝗴 - know what the ai can and can't do 3. 𝗠𝗲𝘁𝗵𝗼𝗱𝗶𝗰𝗮𝗹 𝗔𝗽𝗽𝗿𝗼𝗮𝗰𝗵 - test, iterate, refine (like version control in software) example: a lawyer writing legal document prompts needs domain knowledge (contracts), model understanding (what language models miss), and method (testing different instructions to get consistent output). that's engineering. not guessing.






𝗺𝗼𝘀𝘁 𝗽𝗲𝗼𝗽𝗹𝗲 𝘂𝘀𝗲 𝘁𝗵𝗲 𝘄𝗿𝗼𝗻𝗴 𝗽𝗿𝗼𝗺𝗽𝘁 𝘁𝘆𝗽𝗲. here are the 3 that matter: type 1 - 𝗜𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗶𝗼𝗻𝘀 + 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻 (use when you need advice or guidance.): "how should i write my essay? cover sections, tone, and words to avoid." type 2 - 𝗜𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗶𝗼𝗻𝘀 + 𝗗𝗮𝘁𝗮 (use when you want the AI to create something from your input.): "write 4 paragraphs from this bio: [your background and experience]." type 3 - 𝗤𝘂𝗲𝘀𝘁𝗶𝗼𝗻 + 𝗘𝘅𝗮𝗺𝗽𝗹𝗲𝘀 (use when you want recommendations or pattern matching.): "i like breaking bad and peaky blinders. hate ted lasso. what should i watch?" match the prompt to the task. better prompts → better results.


developer stuck on a bug







