How to use LLMs effectively in your daily work — a practical tutorial 1. Core principles for dev work LLMs are best at transforming and iterating on artifacts (requirements → design, design → code, code → tests, code → docs). You get better results from small, focused prompts than from “build my whole system” requests. Always run outputs through a structured review (alignment, accuracy, completeness, risk) rather than trusting “smart‑sounding” text. Exercise: Next time you’re stuck, instead of “write this whole feature,” ask: “Which artifact is missing here (requirements/design/code/tests/docs)?” Then ask the model for that artifact only. 2. Prompt patterns that actually help Several prompt patterns are particularly useful for software engineering. a) “You are X” role prompts Give the model a role, constraints, and an output format. Pattern You are a senior {language/framework} engineer in a {domain} team. Goal: {one clear goal}. Constraints: {standards, stack, limits}.…