Interview Q&A

Short answer: In web applications or forms, the Memento Pattern can be used to save the state of form inputs at various stages. This allows users to undo their changes or restore the form to a previous valid state.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: You can extend the pattern to support multiple levels of undo by adding more sophisticated memento management (e.g., limiting the number of mementos kept in memory or implementing a more efficient undo/redo system). Real-Time Use Case Examples:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Caretaker class manages the mementos. It’s responsible for saving and undoing changes to the TextEditor. The Save() method pushes the current state (memento) onto a stack. The Undo() method pops the most recent memento off the stack and restores the TextEditor to that state. public class Caretaker

Example code

{
private readonly Stack<TextMemento> _mementos = new Stack<TextMemento>(); public void Save(TextEditor editor) => _mementos.Push(editor.Save()); public void Undo(TextEditor editor)
{
if (_mementos.Count > 0)
{ editor.Restore(_mementos.Pop()); }
}
}

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: While the mediator reduces direct dependencies between colleagues, it can also create a dependency on the mediator itself.

Explain a bit more

Over-reliance on the mediator can lead to issues if the mediator needs to change.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: In a graphical user interface (GUI) system, the Mediator Pattern can be used to manage interactions between various components like buttons, text fields, and labels. For example, clicking a button might update a text field, and the mediator ensures that these updates are propagated correctly.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Instead of having complex direct interactions between objects (users in this case), the mediator simplifies the process, as objects only need to communicate with the mediator.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Users don’t need to know the identities of other users or how to reach them. The mediator centralizes communication, and the users only rely on the mediator to send and receive messages. Benefits of the Mediator Pattern:

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The ChatMediator class is the concrete mediator that implements IChatMediator. It manages a list of users and is responsible for broadcasting messages to all registered users, except the one who sent the message. The mediator decouples the user objects from each other, so they don't need to know about each other's existence. public class ChatMediator : IChatMediator

Example code

{
private readonly List<User> _users = new List<User>();
public void RegisterUser(User user) => _users.Add(user);
public void SendMessage(string message, User user)
{
foreach (var u in _users)
{ // Message should not be sent to the user who sent it if (u != user)
{ u.Receive(message); }
}
}
}

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: When querying a database, the results often come back in the form of a collection (like a list of rows). The Iterator Pattern is used to iterate over these rows to access the data, rather than exposing the internal structure of how the data is retrieved from the database.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Iterator Pattern allows the collection’s internal structure to be hidden from the client. The client interacts only with the iterator, which means that changes to the underlying collection (e.g., changing it from a list to a linked list) do not affect the client code.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The IAggregate<T> interface defines a method CreateIterator() that returns an iterator instance. Any class that represents a collection should implement this interface to provide an iterator. public interface IAggregate<T>

Example code

{ IIterator<T> CreateIterator(); }

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Interpreter Pattern can be extended to support more complex grammars. For example, adding new operations like subtraction or division can be easily done by introducing new non-terminal expressions (e.g., Subtract, Divide).

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Interpreter Pattern is commonly used in building parsers for domain-specific languages (DSLs) or simple programming languages. Each statement or expression in the language can be represented as an object, and the interpreter evaluates these statements to execute the program.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: New operations (e.g., subtraction, multiplication, etc.) can be added easily by creating new non-terminal expression classes (e.g., Subtract, Multiply). This makes the pattern highly extendable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Number class is a terminal expression in the interpreter pattern. It represents a number in the expression and directly returns its value when the Interpret method is called.

Example code

public class Number : IExpression
{
private readonly int _number;
public Number(int number) => _number = number;
public int Interpret() => _number;
}

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Flyweight Pattern could be extended to support composite objects where each flyweight can contain references to other flyweights.

Explain a bit more

For example, a complex character (e.g., with styling information) could consist of several flyweight components (like the base character, font style, size, etc.).

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: GUI frameworks that display multiple similar graphical elements (e.g., buttons, labels, icons) can use the Flyweight Pattern to reuse common elements while only storing the unique aspects (such as position, text, or color).

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: When the program requests a Character for each letter in the string "Hello World", the CharacterFactory checks if the character already exists. If it does, the existing object is reused; otherwise, a new Character object is created. As a result, memory is saved, and performance is improved by reusing common objects. Key Benefits of the Flyweight Pattern:

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The CharacterFactory is responsible for managing the flyweights. It keeps track of the existing character objects and ensures that no duplicate instances of the same character are created. If a character already exists in the dictionary, it is reused. Otherwise, a new Character object is created and stored for future use. public class CharacterFactory

Example code

{
private readonly Dictionary<char, Character> _characters = new
Dictionary<char, Character>();
public Character GetCharacter(char symbol)
{
if (!_characters.ContainsKey(symbol))
{
_characters[symbol] = new Character(symbol);
}
return _characters[symbol];
}
}

Real-world example (ShopNest)

ShopNest’s NotificationFactory creates Email or SMS senders based on user preference.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Instead of directly instantiating the factory within the client code, you could use dependency injection to pass the correct factory implementation into the client code.

Explain a bit more

This would make the code even more flexible and testable.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A document generation system might have different types of document formats, such as PDF, Word, or HTML. A Factory Method can be used to create the appropriate document generator based on user input, allowing for flexible document creation without hardcoding the specific document format classes.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The ILogger interface is implemented by the concrete classes FileLogger and ConsoleLogger. These classes define how the log message will be handled, either by writing to a file or outputting to the console.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: These classes implement the ILogger interface, defining how the messages are logged (either to a file or the console). FileLogger: public class FileLogger : ILogger

Example code

{
public void Log(string message) => Console.WriteLine($"Logging to file: {message}"); } ConsoleLogger: public class ConsoleLogger : ILogger
{
public void Log(string message) => Console.WriteLine($"Logging to console: {message}"); }

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The facade can be enhanced with better exception handling.

Explain a bit more

For example, if a component fails (e.g., DVD player is missing), the facade could display a user-friendly message or take an appropriate action.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A Facade Pattern can be used in financial systems where complex operations like credit checks, account updates, and transaction processing are abstracted into a simplified process, allowing users to perform transactions without understanding the underlying complexities.

Real-world example (ShopNest)

Use a GoF pattern in ShopNest only when it removes duplication or makes a change safer—explain the problem it solves in the interview.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.