Skip to content

How I approach problems #36

Open
Open
@coderbyheart

Description

@coderbyheart

I should try to explain how I approach problems I am presented:

  1. Look at the problem from the user's point of view.
    → write down the User Story, this becomes the source for the acceptance test(s).
  2. Collect all interaction within the system that are affected, and not down new ones. Use Domain Driven Design principles: which Actor(s) cause which Entities to change/appear through which Events?
    → write it down as a Domain Story.
  3. Collect all the systems that are affected by the problem, and figure out which existing systems to re-use and modify and which new systems to introduce to solve it.
    → write it down as a technical concept.
  4. Prioritize the needed changes and find the smallest useful set to get to a working release.
    Repeat until done.

See also:

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs explanationThis issue needs a better explanationprocessingI am thinking if this is actually a good idea

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions