Construct with Collaborators, Call with Work

This article was adapted from a Google Tech on the Toilet (TotT) episode. You can download a printer-friendly version of this TotT episode and post it in your office.

By Shahar Roth 

Classes require various objects and parameters to function. The "Construct with Collaborators, Call with Work" guideline can help you construct effective inputs: 

  • Use the constructor for collaborators—the dependencies that establish the object’s identity. Collaborators stay with the object for its lifetime to enable it to fulfill its ongoing duties.

  • Pass work—the parameters that change with each interaction—to methods. Unique to each call, these inputs provide the specific data needed for an operation such as a file path or database query.

Consider a ReportGenerator that needs a database, a formatter, and a date range to generate a report. The database and formatter, as collaborators, are injected via the constructor, while dateRange, which varies per report generation, is passed as a method parameter to the generate method:

class ReportGenerator {

  private final Database database;

  private final Formatter formatter;


  // database and formatter are passed as collaborators.

  ReportGenerator(Database database, Formatter formatter) {

    this.database = database;

    this.formatter = formatter;

  }


  // dateRange is passed as a parameter.

  Report generate(Range<Instant> dateRange) {

    return formatter.format(database.getRecords(dateRange));

  }

}

A single ReportGenerator object can generate multiple reports with different date ranges:

ReportGenerator generator = new ReportGenerator(database, formatter);

Report report1 = generator.generate(dateRange1);

Report report2 = generator.generate(dateRange2);

Following the "Construct with Collaborators, Call with Work" guideline promotes:

  • Reusability: Enables instances to be used for multiple, distinct operations.

  • Testability: Separates dependency setup from business logic.

  • Cleaner code: Hides implementation dependencies from the object’s users.

  • Predictable behavior: Locks in dependencies at creation time.

Note that the definition of "collaborator" versus "work" depends on the object's identity. For example, a RequestMessage could be a collaborator for a RequestHandler if the handler operates on a single request, or work if the handler processes different requests with each method call.



This entry was posted in Uncategorized on by .

Set custom instructions for Gemini in Google Docs

We are introducing the ability to set custom, persistent instructions for Gemini in Google Docs. These instructions ensure that Gemini adapts to your style, tone, and formatting preferences without needing to repeat them in every conversation, ultimately saving you time and ensuring consistency.

Users can add instructions and rules using Gemini in the side panel of Docs such as "Always respond in bullet points," "When summarizing Docs, always include a 3 bullet points at the top."" or "Use a concise and professional tone for all my documents."

Note that users are currently limited to 1000 active instructions.

Getting started

Rollout pace

Availability

  • Business: Business Starter, Standard, and Plus
  • Enterprise: Enterprise Starter, Standard, and Plus
  • Education: Education Plus
  • Consumer: Google AI Plus, Pro, and Ultra
  • Other Editions: Frontline Plus
  • Education Add-Ons: Google AI Pro for Education, Teaching and Learning
  • Other Add-Ons: AI Expanded Access; AI Ultra Access

Resources

This entry was posted in Uncategorized on by .