The latest articles on DEV Community by Michael Dausmann (@javascriptmick). https://dev.to/javascriptmick https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F157349%2Fe7d8b96d-42f0-4cec-ac2c-b73cc4d13e33.jpg https://dev.to/javascriptmick en Michael Dausmann Fri, 14 Aug 2026 00:27:17 +0000 https://dev.to/javascriptmick/loveyourclankerorg-4ap4 https://dev.to/javascriptmick/loveyourclankerorg-4ap4 <p>I created an open web resource for Software Engineers. </p> <p><a href="https://loveyourclanker.org/" rel="noopener noreferrer">https://loveyourclanker.org/</a></p> <p>It highlights different patterns we can consciously choose use when interacting with our AI Coding tools (a.k.a 'Agents'... a.k.a 'Clankers') to stay in control, maintain quality and sensibly increase efficiency.</p> <p>I was prompted to do this (no pun intended) by observing some pretty alarming signals coming from this community. Token leaderboards, engineers being encouraged to use tools to "stay current" or "keep up" or "not be redundant", engineers quitting tools entirely to stay sane, engineers leaving social gatherings to get back to their agents, engineers setting up whole systems that automate away human engineers and then calling that "agentic engineering".</p> <p>I'm hoping that if we normalise and share how we use the tools, and show that there are different ways where you maintain more control and agency (... pun?) that it might promote a better </p> <p>If you find it helpful, share. If you disagree or want to contribute, raise a PR or ping me. It's all open and NFP.</p> agents ai llm softwareengineering