Interview Q&A

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.

Short answer: The Facade makes the system more readable. If the subsystem's complexity changes, the facade can be updated without affecting the client code.

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 Pattern enables the user to work with a single entry point (i.e., the HomeTheaterFacade), which internally delegates tasks to the complex subsystem classes. This makes the system much easier to use while hiding unnecessary complexity. Key Benefits of the Facade 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 Facade class simplifies interactions with the subsystem by providing a unified interface for the user. It wraps the complex subsystem and provides higher-level methods that internally call the appropriate subsystem methods. public class HomeTheaterFacade

Example code

{
private readonly Amplifier _amplifier;
private readonly DVDPlayer _dvdPlayer;
public HomeTheaterFacade(Amplifier amplifier, DVDPlayer dvdPlayer) {
_amplifier = amplifier;
_dvdPlayer = dvdPlayer;
}
public void WatchMovie(string movie)
{ _amplifier.On(); _dvdPlayer.Play(movie); }
public void EndMovie()
{ _amplifier.Off(); }
}

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: Add functionality to dynamically change the properties of the decorated object.

Explain a bit more

For instance, you could add a feature to customize the size of the coffee (Small, Medium, Large) which would change both the cost and description.

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 text editors, the Decorator Pattern could be used for adding formatting options to text (bold, italic, underline) dynamically, without needing separate classes for each combination of formatting.

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 original SimpleCoffee class remains unchanged, which means you don’t need to touch existing code. The new functionality is added without altering or subclassing the core class.

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 CoffeeDecorator class is abstract, and all concrete decorators (MilkDecorator, SugarDecorator) extend this class. The decorator wraps the SimpleCoffee object (or other decorated objects) and enhances or alters its behavior, like adding extra cost or modifying the description.

Real-world example (ShopNest)

Logging and caching decorators wrap IProductRepository so core SQL code stays clean.

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 SimpleCoffee class is the basic concrete implementation of the ICoffee interface. It represents a basic coffee order with a cost and description. public class SimpleCoffee : ICoffee

Example code

{
public double Cost() => 1.00;
public string Description() => "Simple Coffee";
}

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 file system to support additional metadata for each file or directory, such as size, creation date, and file type. This could be added as properties in the File and Directory 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.