The latest articles on DEV Community by DevEnglish (@devenglish). https://dev.to/devenglish https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3973103%2F487a6f58-571d-4d6e-879c-acea218e0f59.png https://dev.to/devenglish en DevEnglish Sun, 07 Jun 2026 22:49:24 +0000 https://dev.to/devenglish/stop-saying-yesterday-i-was-working-in-in-your-daily-stand-ups-do-this-instead-2pfc https://dev.to/devenglish/stop-saying-yesterday-i-was-working-in-in-your-daily-stand-ups-do-this-instead-2pfc <p>We’ve all been there. The Daily Stand-up starts, the microphone is on you, and you try to translate your thoughts from Spanish to English on the fly. </p> <p>Often, we rely too much on generic AI translations or school English, which makes us sound unnatural or, worse, destroys our technical authority in front of international clients.</p> <p>Let's fix the most common mistake developers make when talking about yesterday's tasks.</p> <h3> ❌ The "AI-Generated" Mistake </h3> <blockquote> <p>"Yesterday I was working in the new login feature and I uploaded the code."</p> </blockquote> <p>Why does this sound off to a native English-speaking client or tech lead?</p> <ol> <li> <strong>"Working in" vs. "Working on":</strong> In English, you work <em>in</em> a building, a company, or a country. But you work <strong>on</strong> a task, a feature, or a bug. </li> <li> <strong>"Uploaded the code":</strong> This sounds like you are uploading a photo to Facebook or a video to YouTube. Devs don't upload code; they use Git terminology.</li> </ol> <h3> The Native Dev Way </h3> <p>If you want to sound like a natural part of a global tech team, use these exact phrases tomorrow:</p> <ul> <li> <em>"Yesterday, I worked **on</em>* the login feature and <strong>pushed</strong> the code to the repository."*</li> <li> <em>"I **merged</em>* the PR for the dashboard issue."*</li> </ul> <p>See the difference? It’s short, direct, and uses actual tech jargon.</p> <h3> Want the full Survival Guide? </h3> <p>This is just a tiny snippet of the <strong>DevEnglish Survival Guide</strong>. </p> <p>If you want the complete cheat sheet that includes:</p> <ul> <li>How to professionally explain server blockers and bugs (without saying you are "trapped").</li> <li>A plug-and-play template to copy/paste before your meetings.</li> <li>Pronunciation alerts for tricky tech words (like API, Archive, and Develop).</li> </ul> <p>You can get it instantly for free here: <strong><a href="https://devenglish.substack.com/" rel="noopener noreferrer">devenglish.substack.com</a></strong></p> <p><strong>About Me:</strong><br> Hi, I'm Valeria. I specialize in helping developers and tech professionals bridge the gap between their technical brilliance and their English communication. Traditional academies teach you how to order a coffee, but not how to explain a Git merge or a server blocker. I built DevEnglish to give you the precise, no-nonsense tools you need to crush your daily meetings and advance your international career.</p> english beginners productivity career