Newsletter
Get a new collocation every weekday
Pick your role and I will send collocations that match the kind of English you actually use at work.
Subscribe
Use your email and choose the audience you belong to.
Example
This is what you should expect to receive:
Subject
And the collocation of the day is...
Hi! How’s everything going?
Hey dev, the rule 'separate concerns' is like a clean merge for your brain—keep UI, business logic, and data access in separate lanes and debugging stays classy.
separate concerns
Here you are a few examples you can use in your role as Software Engineer:
- During a refactor, I separate concerns by moving authentication logic into its own module.
- When implementing a new feature, I separate concerns by splitting API calls into a client service and UI state into components.
How to apply this collocation today?
To apply this today, map your codebase into three buckets: UI, business rules, and data access. Then migrate one cross-cutting concern at a time.
- Identify a recent patch that touched multiple layers and move the non-UI logic into a small service.
- Introduce a clear interface between layers and wire them through dependency injection or simple factories.
- Run focused tests to ensure your separations didn't break behavior.
Example: break a monolithic module that handles API calls and UI state into an ApiClient that talks to the backend and a separate UiState module; the UI now renders based on the state provided by those services.
See you on monday! 🙌