In chat, work English is short and direct: Quick question: before a question, Heads-up: before a warning and Thanks! to close. Abbreviations like FYI, ETA and EOD are common.
Easy phrases (143)
Hey, are you available for a quick sync?
When to use it: Asking a colleague for a brief chat on Slack
Just pushed my changes to the feature branch.
When to use it: Letting the team know you pushed code
Can you take a look at my PR when you get a chance?
When to use it: Politely asking someone to review your pull request
Thanks for the quick fix!
When to use it: Thanking a teammate for resolving an issue fast
I'll be AFK for about 30 minutes.
When to use it: Letting the team know you will be away from keyboard
Heads up, I'm deploying to staging in 10 minutes.
When to use it: Warning the team about an upcoming deployment
Got it, I'll pick up that ticket.
When to use it: Confirming you will work on a task someone mentioned
Is anyone else seeing this error in production?
When to use it: Asking the team if a production error is widespread
Let me check and get back to you.
When to use it: Telling someone you need time to investigate before answering
Could you share the link to that document?
When to use it: Requesting a colleague to share a resource link
Hey, quick question in the thread
When to use it: Starting a threaded conversation
I'll DM you the details
When to use it: Moving conversation to private message
Thanks for the heads up!
When to use it: Acknowledging a warning or notification
Let me paste a code snippet here so you can see the issue
When to use it: Sharing a code snippet in Slack to illustrate a problem
Posting in the wrong channel, sorry!
When to use it: Realizing you posted in the wrong Slack channel
Don't forget to update your Slack status when you're in a meeting
When to use it: Reminding teammates to keep their Slack status current
Who's on call this week?
When to use it: Asking about the on-call rotation
I recorded a quick screen capture to demo the new feature async
When to use it: Sharing an asynchronous screen recording demo instead of a live call
I archived the old project channel since the launch is done
When to use it: Cleaning up Slack by archiving channels that are no longer needed
Happy Friday, everyone! Have a great weekend
When to use it: Casual end-of-week greeting
The PR got approved, merging now
When to use it: Confirming approval and proceeding with merge
I've updated the status page to reflect the current outage, customers can track progress there
When to use it: Updating the public incident status page during an outage
The release train departs Thursday at noon, make sure your PRs are merged by then
When to use it: Informing the team about the scheduled release train cutoff
The new onboarding flow is looking really polished
When to use it: Complimenting someone's work
TIL you can use that shortcut, thanks for sharing!
When to use it: Reacting to a useful tip someone shared
Let me know if you need me to pair on that
When to use it: Offering to help collaborate
Syncing up with the design team after lunch
When to use it: Sharing your schedule plans
Good morning team, here's my async standup update
When to use it: Posting a written standup in Slack
Could you add me as a reviewer on that PR?
When to use it: Requesting to be added to a code review
Thanks everyone, that was a productive brainstorm
When to use it: Wrapping up a collaborative discussion
The documentation is outdated, I'll update it today
When to use it: Volunteering to fix documentation
Great writeup on that bug, very thorough
When to use it: Complimenting a detailed bug report
Anyone free for a quick 5-minute huddle?
When to use it: Requesting an impromptu call
Working on it now, will update the ticket when done
When to use it: Acknowledging a task and committing to update
Could you approve my PR? It's been open since yesterday.
When to use it: Asking for PR review
Let me grab the error logs and paste them in a thread.
When to use it: Sharing debugging info
I'll create a Jira ticket for this and share the link here.
When to use it: Organizing work
Quick poll: should we use REST or GraphQL for the new API?
When to use it: Starting a discussion
The deploy was successful, all health checks are passing.
When to use it: Sharing deploy status
I'm going to be in focus mode for the next two hours.
When to use it: Setting availability
Has anyone run into issues with the new SDK version?
When to use it: Asking for shared experience
That's exactly what I was looking for, thanks!
When to use it: Expressing gratitude
Please don't merge until the QA team signs off.
When to use it: Setting merge conditions
Check the pinned message for the meeting agenda.
When to use it: Directing to resources
I'll hop on a huddle if anyone wants to discuss this live.
When to use it: Offering real-time discussion
The ticket is blocked pending design approval.
When to use it: Sharing blocker
I left some comments on the PR, nothing major.
When to use it: Sharing review feedback
Can you share the Figma link for the updated designs?
When to use it: Requesting resources
Working on it, will update the thread once I have more info.
When to use it: Setting expectations
The new endpoint is live, here's the documentation.
When to use it: Announcing availability
I updated the Postman collection with the latest changes.
When to use it: Sharing tool updates
Sent you a DM with the credentials for the test account.
When to use it: Sharing sensitive info privately
I added a reaction to confirm I've seen the message.
When to use it: Acknowledging messages
The refactoring PR is quite large. I'll break it into smaller ones.
When to use it: Planning PR strategy
Can we do a quick sanity check before deploying to production?
When to use it: Requesting verification
Friendly reminder to update your sprint tasks before the review.
When to use it: Sending reminders
I'll handle the on-call rotation for the holiday period.
When to use it: Volunteering for on-call
Just a heads up, I'm going to restart the staging server.
When to use it: Warning about service interruption
The feature is behind a feature flag, so it's safe to merge.
When to use it: Explaining merge safety
Attaching the stack trace in the thread for context.
When to use it: Sharing debugging info
Thanks for jumping on this so quickly!
When to use it: Expressing appreciation
The cron job completed successfully, all records were processed.
When to use it: Sharing job status
I'll add a disclaimer in the code review about the known limitations.
When to use it: Planning PR communication
The error message is misleading, I'll update it to be more descriptive.
When to use it: Describing improvement
I ran the database backup and uploaded it to S3.
When to use it: Reporting ops task
Shoutout to Maria for catching that bug in code review!
When to use it: Giving public praise
I pushed a fix but I need someone to verify it on staging.
When to use it: Requesting verification
I've documented the workaround in the troubleshooting guide.
When to use it: Sharing documentation
I'm going to do a code walkthrough for the new architecture.
When to use it: Planning knowledge sharing
Can we add this to the retrospective agenda?
When to use it: Adding discussion topics
The new version of the SDK fixed the crash we were seeing.
When to use it: Sharing good news
The PR has merge conflicts, could you rebase?
When to use it: Asking for PR maintenance
That's a great point, I hadn't considered that edge case.
When to use it: Acknowledging feedback
Can we get a quick thumbs up if everyone's aligned on this approach?
When to use it: Checking alignment
I noticed the error rate dropped after the fix. Looks like it worked.
When to use it: Confirming fix effectiveness
The new hire needs access to the repos. Can someone from infra help?
When to use it: Requesting help for onboarding
Please keep the discussion in this channel instead of DMs so the team has context.
When to use it: Encouraging transparency
I'm sending the API contract to the partner team for review.
When to use it: Sharing external communication
The customer reported the issue again. Let me check if our fix was deployed.
When to use it: Investigating customer issue
The automated deployment pipeline just saved us a ton of manual work.
When to use it: Appreciating tooling
Thread for async code review — drop your feedback below.
When to use it: Organizing async review
Just noticed the logging is missing timestamps, I'll add them.
When to use it: Identifying quick fix
Thanks for staying late to fix the production issue, team.
When to use it: Appreciating team effort
I just wrapped up the migration — zero downtime!
When to use it: Celebrating success
I'll be late to the meeting, start without me.
When to use it: Communicating delay
I'll take the on-call pager this weekend so you can take a break.
When to use it: Offering to cover on-call
I reverted the commit that broke the login flow.
When to use it: Reporting a revert
Can we set up a recurring meeting to discuss the migration progress?
When to use it: Proposing meeting
I updated the env file template with the new required variables.
When to use it: Sharing config update
I'm going to do a quick demo in the huddle, join if you're interested.
When to use it: Inviting to demo
The staging environment is back up after the maintenance window.
When to use it: Sharing infrastructure status
Don't worry about it, it's a common mistake.
When to use it: Being reassuring
Let me loop in the security team on this thread.
When to use it: Including relevant people
The team retro is at 3 PM, please add topics to the Miro board.
When to use it: Reminding about meeting
Great work on the release, everything went smoothly!
When to use it: Celebrating team success
Let's avoid scheduling meetings during the focus time block.
When to use it: Setting boundaries
I found a workaround but it's not ideal, I'll file a proper bug fix.
When to use it: Describing temporary solution
I shared the post-mortem document in the channel above.
When to use it: Referencing shared document
The client is asking for an ETA on the bug fix.
When to use it: Relaying client request
Let's avoid this channel for non-engineering discussions, please.
When to use it: Moderating channel
The tech blog post about our architecture is live, check it out!
When to use it: Sharing content
I turned off the noisy alert until we fix the underlying issue.
When to use it: Describing alert management
I automated the weekly report generation, no more manual work.
When to use it: Sharing automation win
My internet is acting up today, I'll use my phone as a hotspot.
When to use it: Communicating connectivity issues
Can we get a consensus on the naming convention before we proceed?
When to use it: Seeking alignment
I'll be the scribe for today's planning session.
When to use it: Volunteering for a role
Please update the status page once the issue is resolved.
When to use it: Requesting action
I'll be reviewing PRs for the next hour if anyone needs feedback.
When to use it: Offering availability for reviews
The PagerDuty alert woke me up at 3 AM, but it was a false positive.
When to use it: Sharing on-call experience
I created a GitHub issue to track the technical debt item.
When to use it: Organizing work
I'll add the monitoring query to the shared Grafana folder.
When to use it: Sharing resources
The third-party service is experiencing an outage, nothing we can do right now.
When to use it: Reporting external dependency issue
I fixed the typo in the config that was causing the deployment to fail.
When to use it: Reporting a simple fix
The API documentation now includes example requests and responses.
When to use it: Sharing documentation update
I'll open a PR for the linting rule changes and tag the team.
When to use it: Planning code quality work
I'm going to mute notifications for the next hour to focus on deep work.
When to use it: Setting focus time
We should pin the working agreements to the channel topic.
When to use it: Suggesting channel organization
Quick update: the migration is at 75% and should finish by tomorrow.
When to use it: Providing status update
I'm escalating this to the platform team since it's related to infrastructure.
When to use it: Escalating appropriately
Is this still an issue or can we close the ticket?
When to use it: Following up on old issues
I set up the development environment documentation for new joiners.
When to use it: Sharing onboarding resources
I saved the Slack canvas with the architecture decision records.
When to use it: Sharing documentation
I'll send the API changelog to the partner teams.
When to use it: Planning communication
The feature is in beta, please report any bugs you find.
When to use it: Announcing beta release
Sharing a link to the sprint dashboard for anyone who needs it.
When to use it: Sharing resources
Can everyone update their availability in the team calendar?
When to use it: Requesting team action
I'll be on PTO next week, here's my handoff document.
When to use it: Planning absence
Just noticed we have two channels for the same project, can we consolidate?
When to use it: Suggesting organization
I validated the fix locally, pushing to staging for further testing.
When to use it: Sharing progress
The sprint planning is overbooked, can we cut some items?
When to use it: Managing sprint scope
I moved the conversation to a thread to keep the channel clean.
When to use it: Organizing discussion
I'm collecting feedback on the developer experience survey, please fill it out.
When to use it: Requesting participation
Let's do an async standup in the thread instead of a meeting today.
When to use it: Suggesting async communication
I uploaded the architecture diagram to the shared drive.
When to use it: Sharing documentation
I'm pairing with the new developer to help them ramp up.
When to use it: Describing mentoring
Would love some feedback on the RFC I posted yesterday.
When to use it: Requesting feedback
I finished the proof of concept, scheduling a demo for tomorrow.
When to use it: Sharing progress
I created a decision log to document why we chose this approach.
When to use it: Sharing documentation
Please add your questions to the shared doc before the Q&A session.
When to use it: Organizing meeting prep
The commit hooks are set up, they'll run linting and formatting automatically.
When to use it: Sharing tooling setup
I'll pair with the backend team on the data model changes.
When to use it: Planning collaboration
Wrapping up for today, will continue tomorrow morning.
When to use it: Signing off
Please test the new feature on both mobile and desktop before we release.
When to use it: Requesting cross-platform testing
Intermediate phrases (114)
I noticed the CI pipeline is failing on the main branch. Can someone investigate?
When to use it: Alerting the team about a broken CI build
I'm going to refactor the authentication module this sprint. I'll keep you posted on the progress.
When to use it: Informing the team about planned refactoring work
The endpoint is returning a 500 error. I've attached the logs in the thread.
When to use it: Reporting a server error and sharing debugging info in a thread
Sorry for the late reply, I was in back-to-back meetings.
When to use it: Apologizing for delayed response due to meetings
I've created a new channel for the migration project. Please join #project-migration.
When to use it: Announcing a new Slack channel for a specific project
Can we move this discussion to a thread? The channel is getting noisy.
When to use it: Asking to keep the channel organized by using threads
FYI, I've updated the environment variables in the staging server. You might need to restart your containers.
When to use it: Notifying the team about configuration changes that may affect them
I'm stuck on this caching issue. Has anyone dealt with Redis invalidation patterns before?
When to use it: Asking for help with a specific technical challenge
The design team shared the updated mockups. I've pinned them in the channel.
When to use it: Sharing design updates and pinning important resources
Reminder: code freeze starts tomorrow at 5 PM. Please merge all pending PRs before then.
When to use it: Sending a deadline reminder about code freeze
I set a Slack reminder for Friday to follow up on this
When to use it: Using Slack's reminder feature to track a pending item
The deploy bot just posted a failure alert in the ops channel
When to use it: Notifying the team about an automated bot alert for a failed deployment
FYI, the API is experiencing some latency issues
When to use it: Informing the team about a known issue
Let's take this offline and discuss in a meeting
When to use it: Suggesting to move a complex discussion out of chat
The build is green, we're good to merge
When to use it: Confirming CI passed and merge is safe
Can we avoid using @here unless it's urgent?
When to use it: Asking team to be mindful of notifications
I created a Slack workflow to automate the weekly status report collection
When to use it: Announcing a new Slack workflow automation for the team
Sharing my screen in the huddle if anyone wants to pair
When to use it: Offering to collaborate via screen share
Reminder: please update your Jira tickets before standup
When to use it: Sending a team reminder about process
The hotfix is live in production now
When to use it: Confirming a critical fix has been deployed
Just drop an emoji reaction so I know you've seen the message
When to use it: Asking teammates to acknowledge a message with an emoji reaction
I muted the alerts channel, it's been way too noisy today
When to use it: Managing notification overload by muting a busy channel
I'm blocked on this, anyone available to help debug?
When to use it: Asking for help with a blocker
Nice catch! I totally missed that edge case
When to use it: Acknowledging someone who found a bug
Is the staging environment up? I'm getting 503 errors
When to use it: Reporting environment issues
Dropping a snippet here for reference
When to use it: Sharing a code snippet in channel
Can we get a status update on the migration?
When to use it: Following up on an ongoing task
I've pinned the runbook to the channel for easy access
When to use it: Making important resources easily findable
Don't forget to update the changelog before releasing
When to use it: Reminding about release process steps
Props to the team for shipping this ahead of schedule!
When to use it: Celebrating a team achievement
I'll write up a summary and post it in the channel later
When to use it: Committing to share information asynchronously
Confirmed, the rollback fixed the issue
When to use it: Verifying a fix after reverting changes
Could you elaborate on what you mean by that?
When to use it: Asking for clarification on a vague message
Tagging the relevant people: check the thread below
When to use it: Drawing attention to an important thread
Setting my status to focus mode, will check messages later
When to use it: Letting team know you need uninterrupted time
I've updated the wiki with the new process, check it out
When to use it: Notifying about documentation updates
Muting this channel for a bit, too many notifications today
When to use it: Managing notification overload
Can you check if the webhook is firing correctly?
When to use it: Asking someone to verify an integration
I tagged you in the thread above, can you take a look at the question?
When to use it: Tagging a specific person in a Slack thread to get their attention
Anyone have experience with GraphQL subscriptions?
When to use it: Seeking technical expertise
Running a quick smoke test on production now
When to use it: Verifying production after deployment
Can we get eyes on this before end of day?
When to use it: Requesting urgent review
Is there a way to reproduce this consistently?
When to use it: Asking about bug reproducibility
Just wrapped up the refactor, much cleaner now
When to use it: Announcing completion of a refactoring task
The feature toggle is now available in the admin panel
When to use it: Announcing a new capability
Has the database backup completed successfully?
When to use it: Checking on maintenance tasks
I'll be working from a different timezone next week, heads up
When to use it: Informing about schedule changes
That's a known issue, there's a workaround in the FAQ
When to use it: Pointing to existing solutions
Please don't force-push to main, use a feature branch
When to use it: Correcting git workflow mistakes
I've added comments on the Figma file with my feedback
When to use it: Sharing design feedback location
The new hire starts Monday, let's make sure their dev environment is ready
When to use it: Preparing for a new team member
Cross-posting from the engineering channel for visibility
When to use it: Sharing information across channels
I noticed you're also working on the auth module. Can we coordinate?
When to use it: Avoiding conflicts
The error is intermittent, I can't reproduce it consistently.
When to use it: Describing a tricky bug
The nightly build failed, but it looks like a flaky test.
When to use it: Triaging build failure
Apologies for the @channel, but this is time-sensitive.
When to use it: Justifying a broadcast notification
Looks like the SSL cert expired, that's why the API is down.
When to use it: Diagnosing an issue
Can someone with admin access grant me permissions to the prod environment?
When to use it: Requesting access
The API latency spiked after the last deploy, reverting now.
When to use it: Reporting incident action
The Slack bot is reporting high memory usage on the server.
When to use it: Sharing monitoring alerts
The test coverage for this module dropped below 70%.
When to use it: Reporting quality metrics
We need to discuss the breaking changes before the next release.
When to use it: Flagging important discussion
I'll post a summary of the architectural decision in the RFC channel.
When to use it: Planning communication
Anyone available to pair on the Kubernetes deployment config?
When to use it: Asking for pairing partner
The frontend bundle size increased by 20% after the last merge.
When to use it: Reporting quality regression
Can we schedule a knowledge transfer session before Sam leaves?
When to use it: Planning knowledge sharing
I'm adding the request ID to all log entries for easier tracing.
When to use it: Describing observability improvement
I tested the rollback procedure and it works as expected.
When to use it: Verifying safety procedures
I'm configuring the webhook to notify us on Slack when a deploy fails.
When to use it: Describing integration
Let me check the audit logs and I'll share what I find.
When to use it: Investigating an issue
Posting the incident timeline for the outage we had last night.
When to use it: Sharing incident info
I enabled the debug mode on staging to trace the issue.
When to use it: Describing debugging setup
The API versioning proposal is ready for discussion in the RFC channel.
When to use it: Sharing a proposal
The user acceptance testing revealed a few edge cases we missed.
When to use it: Sharing QA results
I'll write a migration guide for the teams consuming our API.
When to use it: Planning documentation
Be careful with that table, it has over 10 million rows.
When to use it: Warning about data scale
I'm going to create a shared module for the common components.
When to use it: Planning code organization
The webhook payload format changed, I'll update the parser.
When to use it: Identifying fix needed
The response time improved from 800ms to 200ms after the optimization.
When to use it: Sharing metrics
I noticed some inconsistencies in the API responses, I'll open a ticket.
When to use it: Identifying issue
The integration test suite is taking too long, we should parallelize it.
When to use it: Suggesting improvement
I've set up a webhook to post deployment status to this channel.
When to use it: Sharing automation
Can someone from the data team verify the ETL pipeline is running?
When to use it: Cross-team request
I'm running a load test now, response times might be affected.
When to use it: Warning about test impact
Can you check if the feature flag is enabled for this user segment?
When to use it: Debugging feature flag
The team velocity has improved since we started limiting WIP.
When to use it: Sharing positive trend
I'll create a runbook for handling this type of incident.
When to use it: Planning documentation
The database failover worked perfectly during the drill.
When to use it: Sharing DR test results
Please review the access control changes before they go live.
When to use it: Requesting security review
The endpoint is deprecated, please migrate to v2 by end of quarter.
When to use it: Announcing deprecation
I proposed a new folder structure for the monorepo in the RFC.
When to use it: Sharing architectural proposal
The SLA breach notification triggered, someone needs to look into it.
When to use it: Escalating an issue
The container registry is almost at capacity, we should clean up old images.
When to use it: Flagging maintenance need
I benchmarked both approaches and option B is 40% faster.
When to use it: Sharing performance comparison
That's a breaking change, we need to communicate it to all consumers.
When to use it: Flagging impact
The error only occurs in Safari, works fine in Chrome and Firefox.
When to use it: Describing browser-specific bug
I put together a comparison table for the different database options.
When to use it: Sharing research
Heads up, I'm going to run the vacuum on the main database.
When to use it: Warning about maintenance
I just published the npm package with the security patch.
When to use it: Announcing release
The DNS propagation is complete, the new domain should work now.
When to use it: Sharing infrastructure update
I added the pre-commit hook to enforce the commit message format.
When to use it: Sharing tooling update
The experiment showed no significant difference, let's go with the simpler approach.
When to use it: Sharing A/B test results
The performance regression was caused by a missing database index.
When to use it: Explaining root cause
I noticed the tests are running in the wrong order, that might cause flakiness.
When to use it: Identifying test issue
The infrastructure cost went down 15% after the optimization.
When to use it: Sharing positive metrics
I shipped the fix behind a feature flag for safety.
When to use it: Describing safe deployment
The code coverage report is now auto-generated on every PR.
When to use it: Sharing automation
The credentials in the vault are rotated, update your local env.
When to use it: Sharing security update
The build artifacts are now stored in the artifact registry.
When to use it: Sharing infrastructure change
The unit tests are taking five minutes to run, we should optimize them.
When to use it: Identifying performance issue
I'm going to update the error codes to follow the RFC standard.
When to use it: Describing standards work
I noticed the health check endpoint is not behind authentication.
When to use it: Reporting security finding
I set up a Slack workflow for incident escalation.
When to use it: Describing process automation
The CI build time went from 15 minutes to 5 minutes after the cache optimization.
When to use it: Sharing improvement metrics
Advanced phrases (43)
I've been investigating the memory leak we discussed yesterday and it seems to be caused by a circular reference in the event listener module. I'll submit a fix by end of day.
When to use it: Providing a detailed status update on a bug investigation
Just a heads up, the third-party payment API will undergo scheduled maintenance this weekend. We should add a fallback mechanism and display a user-friendly error message.
When to use it: Warning about scheduled downtime and suggesting proactive solutions
I've set up a webhook integration between our Slack workspace and the GitHub repo so we get automatic notifications for new PRs and failed builds.
When to use it: Announcing a new automation integration to the team
Could you walk me through the architecture decision for using microservices instead of a monolith? I want to make sure I understand the trade-offs before I start implementing.
When to use it: Asking for clarification on an architectural decision before starting work
I ran the load tests and the API can handle around 2,000 requests per second before response times start degrading. Should we look into horizontal scaling or optimize the database queries first?
When to use it: Sharing performance test results and asking for guidance on next steps
The feature flag for the new onboarding flow is now enabled in the staging environment. Please test it and report any issues in this thread.
When to use it: Announcing a feature flag change and requesting testing feedback
I've noticed we're duplicating a lot of validation logic across services. I'd like to propose creating a shared validation library. Thoughts?
When to use it: Proposing a technical improvement to reduce code duplication
After reviewing the incident post-mortem, I think we should implement circuit breakers for all external API calls and add better retry logic with exponential backoff.
When to use it: Suggesting improvements based on a post-mortem analysis
Quick question: does anyone know if we have rate limiting configured on the GraphQL endpoint? I'm seeing some suspicious traffic patterns in the monitoring dashboard.
When to use it: Asking about infrastructure configuration while flagging a potential security concern
I've documented the new API endpoints in Confluence and updated the Postman collection. The link is in the channel description. Let me know if anything is unclear.
When to use it: Sharing documentation updates and making them easy to find
I'm going to be OOO tomorrow, ping Sarah for anything urgent
When to use it: Notifying team about absence and backup contact
Does this warrant a post-mortem or was it a minor hiccup?
When to use it: Evaluating the severity of an incident
I swapped on-call shifts with Alex, so I'm covering this weekend instead
When to use it: Informing the team about a change in the on-call rotation schedule
Heads up: we're doing a database migration tonight at midnight
When to use it: Warning about scheduled maintenance
Looping in the infrastructure team on this one
When to use it: Adding relevant people to a discussion
The monitoring dashboard is showing a spike in error rates
When to use it: Alerting the team about anomalies
This looks like a regression from the last release
When to use it: Identifying a bug introduced by recent changes
The automated tests caught a flaky test, investigating now
When to use it: Reporting on CI/CD test results
The endpoint is rate-limited, we need to implement backoff
When to use it: Discussing technical constraints
We should probably add this to our tech debt backlog
When to use it: Suggesting tracking of technical debt
The load balancer configuration needs to be reviewed before we scale
When to use it: Flagging infrastructure concerns
Looks like the cron job didn't run last night
When to use it: Reporting a scheduled task failure
I'm getting a 401 on the new endpoint, is auth configured?
When to use it: Reporting an authentication issue
We need to bump the dependency versions before the next release
When to use it: Flagging dependency updates needed
The memory leak seems to be coming from that third-party library
When to use it: Sharing debugging findings
The A/B test results are in, variant B wins by 12%
When to use it: Sharing experiment results
We should add an alert for when disk usage exceeds 80%
When to use it: Suggesting monitoring improvements
The cache invalidation is not working as expected
When to use it: Reporting a caching bug
Noticed some flaky tests on the CI pipeline, anyone else seeing this?
When to use it: Asking about intermittent CI failures
I'll spin up a new environment for testing this feature
When to use it: Setting up infrastructure for testing
We're seeing a 30% increase in response times after the deploy
When to use it: Reporting performance degradation
Kicking off the canary deployment now
When to use it: Starting a gradual rollout
The SSO integration is breaking intermittently
When to use it: Reporting an unreliable authentication issue
Reminder to rotate your API keys by end of sprint
When to use it: Security maintenance reminder
We should consider using a message queue for this workflow.
When to use it: Suggesting architecture
The rate limiter kicked in during the load test — we need to adjust the threshold.
When to use it: Sharing test results
I'm testing the disaster recovery plan in a sandbox environment.
When to use it: Describing DR testing
We're seeing a lot of 429 errors, the rate limiter might be too aggressive.
When to use it: Reporting API issue
I just finished the spike on WebAssembly performance.
When to use it: Sharing research results
The custom middleware is causing a 50ms overhead on every request.
When to use it: Reporting performance issue
I need to upgrade the Terraform provider before we can use the new features.
When to use it: Identifying prerequisite
I need to add request tracing to debug the intermittent timeout.
When to use it: Describing debugging approach
The service mesh configuration needs updating after the cluster upgrade.
When to use it: Identifying maintenance task
Other everyday developer situations
- Daily standup280 phrases
- Code review275 phrases
- Pull requests300 phrases
- Bug reports300 phrases
- Meetings300 phrases
- Job interviews300 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.