A standup almost always follows the same order: what you did yesterday, what you will do today and what is blocking you. Learn one phrase for each part and swap only the subject (the screen, the endpoint, the ticket).
Easy phrases (155)
I'm working on the login feature today.
When to use it: Sharing your current task during daily standup
Yesterday I finished the API integration.
When to use it: Reporting what you completed the previous day
No blockers on my end.
When to use it: Confirming you have no impediments
I'll continue with the same task.
When to use it: Indicating you're still working on the same item
I'm almost done with my ticket.
When to use it: Letting the team know you're close to finishing
I'll pick that up after lunch.
When to use it: Committing to start a task later
I pushed my changes yesterday.
When to use it: Telling the team you committed code
The tests are passing now.
When to use it: Confirming your tests are green
I need to update the documentation.
When to use it: Mentioning a documentation task
I'm reviewing the pull request.
When to use it: Telling the team you're doing code review
I'll start the new sprint item today.
When to use it: Planning to begin a new task
Everything is on track.
When to use it: Confirming progress is going well
I fixed the bug in the checkout flow.
When to use it: Reporting a bug fix
I'll be working on the database migration.
When to use it: Announcing your planned task
I created a new branch for the feature.
When to use it: Telling the team about your branch
I'm waiting for the design to be finalized.
When to use it: Explaining a dependency on design team
I'll move this ticket to done.
When to use it: Closing a completed task
I need to write more tests.
When to use it: Mentioning testing work needed
The deployment went smoothly.
When to use it: Reporting a successful deployment
I'm pairing with Alex on this.
When to use it: Telling the team about collaboration
I updated the Jira board.
When to use it: Confirming project board is current
Good morning, everyone.
When to use it: Greeting the team at standup
That's all from me.
When to use it: Signaling you're done with your update
I'm on track to finish by Friday.
When to use it: Giving a timeline estimate
I refactored the service layer.
When to use it: Reporting code improvement work
I need access to the staging server.
When to use it: Requesting permissions
I'll add error handling to that endpoint.
When to use it: Planning to improve code robustness
Can someone review my PR?
When to use it: Asking for a code review
I'll sync up with the backend team.
When to use it: Planning cross-team coordination
I merged my branch into develop.
When to use it: Reporting a merge
I resolved the merge conflict.
When to use it: Reporting conflict resolution
I'm setting up the dev environment.
When to use it: Working on environment configuration
I updated the dependencies.
When to use it: Reporting package updates
I optimized the database query.
When to use it: Reporting performance improvement
I'm looking into the performance issue.
When to use it: Investigating a problem
I added unit tests for the new feature.
When to use it: Reporting test additions
I estimate about two more days of work on this ticket.
When to use it: Giving a time estimate for remaining work
I'm debugging an edge case.
When to use it: Working on a tricky bug
I'll work on the responsive layout.
When to use it: Planning UI work
I'm implementing the search functionality.
When to use it: Working on search feature
I'm stuck on this issue — can someone take a look with me after standup?
When to use it: Asking for help with a blocker during standup
I paired with Sarah yesterday to work through the database design.
When to use it: Mentioning you paired with someone yesterday
I'm actually ahead of schedule on this one.
When to use it: Reporting you are ahead of schedule
We'll need to update the timeline — this task is more complex than expected.
When to use it: Saying you need to update the project timeline
I'm waiting on the platform team to deploy their service before I can continue.
When to use it: Noting a dependency on another team's work
I attended the knowledge-sharing session on Kubernetes yesterday.
When to use it: Mentioning you attended a knowledge-sharing session
I spent part of yesterday onboarding the new developer on our codebase.
When to use it: Reporting you onboarded a new team member
I refactored the legacy code in the billing module to make it testable.
When to use it: Saying you refactored legacy code
I set up monitoring alerts for the new endpoints.
When to use it: Mentioning you set up monitoring alerts
I wrote integration tests for the checkout workflow.
When to use it: Reporting you wrote integration tests
I updated the CI pipeline to run linting before the tests.
When to use it: Saying you updated the CI pipeline configuration
I participated in the architecture review for the new microservice.
When to use it: Mentioning you participated in an architecture review
I migrated the user data from the old schema to the new one.
When to use it: Reporting you migrated data from old schema
I profiled the app and found a few performance bottlenecks in the rendering layer.
When to use it: Saying you profiled the app for performance bottlenecks
I fixed several accessibility issues flagged by the audit tool.
When to use it: Mentioning you fixed accessibility issues
I updated our third-party dependencies to their latest stable versions.
When to use it: Reporting you updated third-party dependencies
I documented all the API endpoints in the wiki.
When to use it: Saying you documented the API endpoints
I created runbooks for the ops team to handle common incidents.
When to use it: Mentioning you created runbooks for ops team
I implemented error tracking so we can catch crashes in production.
When to use it: Reporting you implemented error tracking
I reviewed the security audit findings and created tickets for each vulnerability.
When to use it: Saying you reviewed the security audit findings
I'll handle that.
When to use it: Volunteering for a task
Let me check on that.
When to use it: Offering to investigate something
I'll have it ready by tomorrow.
When to use it: Committing to a timeline
Nothing new to report.
When to use it: When you have no significant updates
I ran the full test suite.
When to use it: Confirming comprehensive testing
I'll sync with QA to make sure they have test cases ready for this feature.
When to use it: Coordinating with the QA team on testing
The feature is code complete.
When to use it: Reporting feature completion
I'm updating the API documentation.
When to use it: Working on API docs
I need to refactor this component.
When to use it: Planning code improvement
I'll clean up the code before merging.
When to use it: Planning pre-merge cleanup
I'm working on the frontend refactor.
When to use it: Sharing your current task
I closed three tickets yesterday.
When to use it: Reporting completed work
I'm pair programming with the new hire today.
When to use it: Describing collaborative work
My PR is waiting for approval.
When to use it: Sharing blocker status
I'll tackle the performance issue next.
When to use it: Planning upcoming work
I'll wrap up the testing by end of day.
When to use it: Setting expectations
I updated the environment variables for staging.
When to use it: Sharing infrastructure work
The build is green after my latest changes.
When to use it: Reporting test status
I'll demo the feature in sprint review.
When to use it: Planning a presentation
I'll update the Swagger docs after the API changes.
When to use it: Planning documentation
I completed the code review for the authentication PR.
When to use it: Reporting review work
I submitted the PR late yesterday and it still needs review.
When to use it: Sharing PR status
The QA team approved the feature for release.
When to use it: Sharing good news
I'll ping the team in Slack if I need help.
When to use it: Communicating availability
I had to increase the timeout on the API calls.
When to use it: Explaining a fix
I'm working through the backlog of bug reports.
When to use it: Describing bug fix work
I'll move the ticket to 'in review' now.
When to use it: Updating board status
I had to rebase my branch against main.
When to use it: Describing git operations
I'll take ownership of that ticket.
When to use it: Volunteering for work
I'm adding input validation to the form fields.
When to use it: Describing validation work
The hotfix was deployed to production last night.
When to use it: Reporting deployment
I'll handle the data migration over the weekend.
When to use it: Planning weekend work
The linter is flagging some style issues I need to fix.
When to use it: Reporting linter issues
I'll reach out to the stakeholders for feedback.
When to use it: Planning communication
I'm adding logging to help trace the issue.
When to use it: Describing debugging approach
I'm adding dark mode support to the settings page.
When to use it: Describing UI feature
I'll finish writing the unit tests this morning.
When to use it: Setting a timeline
I'll create a separate PR for the refactoring.
When to use it: Organizing work
I had a productive pairing session with the tech lead.
When to use it: Sharing collaboration
I'm updating the error messages to be more user-friendly.
When to use it: Describing UX improvement
I'll schedule a meeting with the architect to discuss the design.
When to use it: Planning a meeting
The automated tests caught a bug before it reached production.
When to use it: Sharing positive outcome
I'll tag the release after the final round of QA.
When to use it: Planning release
I fixed the broken import statement that was causing the build to fail.
When to use it: Reporting a fix
I'll add the loading spinner for better UX.
When to use it: Describing UX work
I finished setting up the staging environment.
When to use it: Reporting setup completion
I'll fix the failing snapshot tests today.
When to use it: Planning test fixes
I onboarded the new team member on our git workflow.
When to use it: Describing mentoring
I'll be focusing on tech debt reduction today.
When to use it: Sharing today's focus
I wrote a helper function to reduce code duplication.
When to use it: Describing refactoring
I'll coordinate with the mobile team on the API contract.
When to use it: Planning collaboration
I cleaned up the unused feature flags.
When to use it: Reporting cleanup
I'll share the technical design document for feedback.
When to use it: Planning collaboration
I'll follow up on the open questions from yesterday's design review.
When to use it: Planning follow-up
The database migration ran successfully in staging.
When to use it: Reporting migration result
I need someone to help me reproduce the issue on Windows.
When to use it: Asking for help
I'll create a runbook for the deployment process.
When to use it: Planning documentation
The code freeze starts tomorrow, so I'm wrapping up my changes.
When to use it: Sharing timeline awareness
I'll update the changelog before the release.
When to use it: Planning release documentation
I attended the incident retro yesterday afternoon.
When to use it: Sharing what you did
I'm reviewing the pull requests from the open source contributors.
When to use it: Describing community work
I triaged the incoming bug reports and prioritized them.
When to use it: Reporting triage work
I'll run the performance benchmarks after my changes.
When to use it: Planning performance testing
I need to bump the version number for the next release.
When to use it: Describing release prep
I debugged the issue and it turned out to be a null pointer exception.
When to use it: Explaining root cause
I'll clean up the temporary workarounds after the proper fix lands.
When to use it: Planning cleanup
I need to update the API documentation with the new endpoints.
When to use it: Planning documentation
I'll pair with the frontend team on the component library.
When to use it: Planning collaboration
I updated the README with the troubleshooting guide.
When to use it: Reporting documentation work
I reproduced the bug and I'm working on a fix.
When to use it: Sharing debugging progress
I'll update the CI config to include the new test suite.
When to use it: Planning CI changes
I'll be working from home today, but I'm fully available.
When to use it: Sharing availability
I enabled compression on the API responses.
When to use it: Describing optimization
I just picked up the highest priority bug from the backlog.
When to use it: Sharing what you picked up
I'll add smoke tests for the critical user flows.
When to use it: Planning testing
I'll verify the fix on staging before promoting to production.
When to use it: Planning verification
I'll share the retrospective action items with the team.
When to use it: Planning communication
I need help reviewing the database schema changes.
When to use it: Asking for help
I just deployed the new version of the mobile app to TestFlight.
When to use it: Reporting deployment
I replaced the hard-coded values with environment variables.
When to use it: Describing config improvement
I'll add the feature to the beta channel first.
When to use it: Planning gradual rollout
I updated the TypeScript types to match the new API response.
When to use it: Describing type safety work
I resolved the dependency vulnerability by bumping the package version.
When to use it: Reporting security fix
I cleaned up the dead code after the feature was deprecated.
When to use it: Reporting cleanup
I pinpointed the root cause — it was a missing null check.
When to use it: Explaining root cause
I need to look into why the nightly build keeps failing.
When to use it: Identifying investigation
I'll send a summary of my findings in Slack after standup.
When to use it: Planning communication
I'm done with my updates. Does anyone need help with anything?
When to use it: Offering help at end of standup
I'll refactor the tests to use the new test utilities.
When to use it: Planning test improvement
I need to discuss the rate limiting thresholds with the product owner.
When to use it: Planning discussion
I'll be offline for a couple of hours this afternoon for a dentist appointment.
When to use it: Sharing availability
I wrote a database seed script for the development environment.
When to use it: Describing tooling
I removed the console.log statements I left during debugging.
When to use it: Reporting cleanup
I need to add the CORS headers to allow cross-origin requests.
When to use it: Identifying task
I'm wrapping up the documentation for the new API version.
When to use it: Describing documentation work
Intermediate phrases (90)
I'm blocked on the payment integration because the third-party API is returning 500 errors.
When to use it: Explaining a blocker with specific technical details
I had to revert my last commit because it broke the build.
When to use it: Explaining a rollback situation
I've been investigating a memory leak in the service worker.
When to use it: Reporting deep debugging work
Could someone from the backend team help me with the GraphQL schema?
When to use it: Requesting cross-team help
I'm going to split this into smaller PRs to make it easier to review.
When to use it: Explaining PR strategy
I've been working on improving the test coverage for the authentication module.
When to use it: Reporting testing efforts on a specific area
I've been working on improving the test coverage for the payment module.
When to use it: Reporting testing efforts on a specific area
I've been working on improving the test coverage for the notification module.
When to use it: Reporting testing efforts on a specific area
I've been working on improving the test coverage for the search module.
When to use it: Reporting testing efforts on a specific area
I've been working on improving the test coverage for the analytics module.
When to use it: Reporting testing efforts on a specific area
I need to coordinate with the QA team before we can release this feature.
When to use it: Explaining a dependency on QA
I discovered that the issue is related to a race condition in the async handler.
When to use it: Sharing a debugging discovery
I noticed the staging environment is behaving differently from production.
When to use it: Flagging an environment discrepancy
I'll need to pair with someone on the infrastructure changes.
When to use it: Requesting collaboration
The feature flag is ready, so we can do a gradual rollout.
When to use it: Explaining release strategy
I'm going to add some logging to help us debug this issue in production.
When to use it: Adding observability
I realized we need to handle the edge case where the user has no internet connection.
When to use it: Identifying a missing scenario
I ran into a dependency conflict.
When to use it: Reporting a blocker
The code review took longer than expected.
When to use it: Explaining time spent
I found a regression in the latest build.
When to use it: Reporting an issue
I'm going to spike on the new payment provider.
When to use it: Describing research work
I need the product team to clarify the acceptance criteria.
When to use it: Expressing a dependency
I'm writing the migration script for the new table.
When to use it: Describing database work
I'm waiting on the DevOps team to provision the new server.
When to use it: Reporting external dependency
I need to add caching to improve the response time.
When to use it: Identifying improvement
I'm investigating why the webhook isn't firing.
When to use it: Describing debugging work
I'm setting up end-to-end tests for the checkout flow.
When to use it: Describing testing work
I'm implementing the search filters as per the latest designs.
When to use it: Describing UI work
I noticed some flaky tests in the CI pipeline.
When to use it: Reporting CI issues
I need to set up a feature flag for the new experiment.
When to use it: Describing feature flag work
I'll cherry-pick the fix to the release branch.
When to use it: Describing git workflow
I optimized the image loading to reduce bundle size.
When to use it: Reporting optimization
I completed the spike on the real-time notification system.
When to use it: Reporting research results
I'm going to shadow the on-call engineer today to learn the process.
When to use it: Describing learning activity
I fixed the CORS issue on the staging server.
When to use it: Reporting a fix
The API response time improved after the indexing changes.
When to use it: Sharing performance results
I need to update the SSL certificate before it expires.
When to use it: Reporting urgent task
I'll add retry logic to the failed API calls.
When to use it: Describing resilience work
I'm writing a script to automate the database seeding.
When to use it: Describing automation
I'm upgrading the Node version across all services.
When to use it: Describing infrastructure work
I'm configuring the new monitoring dashboard.
When to use it: Describing observability work
I had to roll back the feature toggle because of a bug.
When to use it: Explaining a revert
I set up the pre-commit hooks for the team.
When to use it: Describing tooling work
I'm extracting the shared logic into a reusable module.
When to use it: Describing code reuse
I'm looking into upgrading our authentication library.
When to use it: Describing research
I'm adding pagination to the list endpoint.
When to use it: Describing API feature
I added structured logging to the payment service.
When to use it: Describing observability
I'm containerizing the service with Docker.
When to use it: Describing DevOps work
I'm converting the callback-based code to async/await.
When to use it: Describing modernization
I'm working on the accessibility improvements for screen readers.
When to use it: Describing accessibility work
I submitted the security patch to the upstream repository.
When to use it: Reporting open source work
I verified that the rollback plan works correctly.
When to use it: Reporting validation
I'll write the postmortem document for the outage.
When to use it: Planning documentation
I'm adding health check endpoints to all our services.
When to use it: Describing infrastructure work
I configured alerts for when CPU usage exceeds eighty percent.
When to use it: Describing monitoring
I'm migrating the cron jobs to a task scheduler.
When to use it: Describing infrastructure change
I removed the deprecated API endpoints as planned.
When to use it: Reporting cleanup
I optimized the SQL queries to reduce the page load time.
When to use it: Reporting optimization
I'll set up the continuous deployment pipeline today.
When to use it: Planning DevOps work
I'm adding support for internationalization to the frontend.
When to use it: Describing i18n work
I'm refactoring the API to follow RESTful conventions.
When to use it: Describing API improvement
I'll create a shared library for the common utilities.
When to use it: Planning code sharing
I added database indexes to speed up the search queries.
When to use it: Reporting optimization
The security scan flagged a vulnerable dependency.
When to use it: Reporting security issue
I migrated the tests from Jest to Vitest.
When to use it: Describing tooling migration
I'm adding request validation middleware to the API.
When to use it: Describing security work
I cached the API responses to reduce latency.
When to use it: Reporting optimization
I added the error boundary to prevent the whole app from crashing.
When to use it: Describing resilience
I refactored the middleware chain for better readability.
When to use it: Describing refactoring
I set up the new Grafana dashboard for the backend metrics.
When to use it: Describing observability
I'm working on lazy loading the images to improve initial page load.
When to use it: Describing performance work
The load balancer configuration needs to be updated for the new instances.
When to use it: Identifying a task
I created a shared context for the authenticated user state.
When to use it: Describing architecture work
I'm working on the file upload feature with drag and drop.
When to use it: Describing UI feature
I'll add the cron job to clean up expired sessions.
When to use it: Planning maintenance task
I automated the release notes generation from commit messages.
When to use it: Describing automation
I need to add a retry queue for failed email deliveries.
When to use it: Identifying a task
I reduced the Docker image size by switching to Alpine.
When to use it: Reporting optimization
I adjusted the retry policy to be more aggressive during peak hours.
When to use it: Describing configuration change
The API gateway is now routing traffic correctly to the new service.
When to use it: Reporting progress
I'm building the admin dashboard for managing user accounts.
When to use it: Describing feature work
I'll set up the mock server for the frontend team to start working.
When to use it: Enabling other team
I'm adding the soft delete feature so we can recover deleted records.
When to use it: Describing data safety
I'm working on the GraphQL resolvers for the new entity.
When to use it: Describing API work
I configured the CDN to cache the static assets.
When to use it: Describing infrastructure
I rolled out the feature to ten percent of users for A/B testing.
When to use it: Describing gradual rollout
I standardized the error response format across all endpoints.
When to use it: Describing API improvement
I set up the integration tests with the real database.
When to use it: Describing test infrastructure
I'm setting up GitHub Actions for the automated deployments.
When to use it: Describing CI/CD work
I noticed the memory usage has been increasing steadily and I'll investigate.
When to use it: Identifying investigation
Advanced phrases (35)
I've been going down a rabbit hole trying to figure out why the WebSocket connection drops intermittently.
When to use it: Describing a complex debugging situation
I think we should consider breaking this monolith into microservices, but that's a bigger conversation.
When to use it: Suggesting architectural change carefully
The tech debt is starting to snowball — we might want to allocate a sprint for cleanup.
When to use it: Advocating for tech debt time
I'm leaning towards using a pub/sub pattern for this, but I'd like to get a second opinion before committing to the architecture.
When to use it: Seeking consensus on a technical decision
We might want to add a circuit breaker around this external service call to prevent cascading failures.
When to use it: Suggesting a resilience pattern
I'm refactoring the state management to use Redux.
When to use it: Describing architecture change
I'm implementing rate limiting on the public API.
When to use it: Describing security work
I resolved the timeout issue by implementing connection pooling.
When to use it: Explaining a technical fix
I'm investigating a spike in error rates since yesterday's deploy.
When to use it: Describing incident investigation
I fixed the race condition in the order processing pipeline.
When to use it: Reporting a complex fix
I'm splitting the monolithic service into smaller microservices.
When to use it: Describing architecture work
I need to update the API versioning strategy.
When to use it: Describing API work
I'm working on reducing the cold start time for our serverless functions.
When to use it: Describing performance work
I'll add the API key rotation mechanism today.
When to use it: Describing security work
I'm setting up the blue-green deployment strategy.
When to use it: Describing deployment work
I'm implementing the webhook retry mechanism with exponential backoff.
When to use it: Describing resilience work
I'll set up the canary deployment for the new version.
When to use it: Planning deployment
I updated the Terraform configuration for the new resources.
When to use it: Describing IaC work
I'm implementing the new OAuth flow for third-party integrations.
When to use it: Describing auth work
I'm adding two-factor authentication to the admin panel.
When to use it: Describing security feature
I fixed a memory leak in the image processing pipeline.
When to use it: Reporting a fix
I'm working on the data export feature for GDPR compliance.
When to use it: Describing compliance work
I'm implementing the event-driven architecture for the notification system.
When to use it: Describing architecture work
I'm handling the edge case where the session token expires mid-request.
When to use it: Describing edge case handling
I wrote a custom linter rule for our coding standards.
When to use it: Describing tooling work
I'm implementing server-side rendering for better SEO.
When to use it: Describing SSR work
I'm adding WebSocket support for real-time updates.
When to use it: Describing feature work
I'm implementing the GraphQL subscriptions for the chat feature.
When to use it: Describing feature work
I'm implementing the queue system for background jobs.
When to use it: Describing backend work
I'm setting up distributed tracing across our microservices.
When to use it: Describing observability
I'm adding the database connection pool to handle more concurrent requests.
When to use it: Describing scalability work
I added the OpenTelemetry instrumentation for better observability.
When to use it: Describing observability work
I'm looking into the failing health checks on the production pods.
When to use it: Describing investigation
I'm handling the graceful shutdown of the service.
When to use it: Describing reliability work
I'm implementing the circuit breaker pattern for the external API calls.
When to use it: Describing resilience pattern
Other everyday developer situations
- Code review275 phrases
- Pull requests300 phrases
- Bug reports300 phrases
- Meetings300 phrases
- Job interviews300 phrases
- Slack and chat300 phrases
- Email298 phrases
- Technical discussions299 phrases
- Polite phrases300 phrases
- Pair programming300 phrases
- Documentation300 phrases
Guides with more context
Take it to your phone
In the Devlingo app you get 10 new phrases a day, each with real-world context, pronunciation and examples, and the widget shows the phrase of the day on your iPhone Home Screen.