Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How I approach problems #36

Open
coderbyheart opened this issue Jun 29, 2020 · 0 comments
Open

How I approach problems #36

coderbyheart opened this issue Jun 29, 2020 · 0 comments
Labels
needs explanation This issue needs a better explanation processing I am thinking if this is actually a good idea

Comments

@coderbyheart
Copy link
Owner

coderbyheart commented Jun 29, 2020

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:

@coderbyheart coderbyheart added needs explanation This issue needs a better explanation processing I am thinking if this is actually a good idea labels Jun 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs explanation This issue needs a better explanation processing I am thinking if this is actually a good idea
Projects
None yet
Development

No branches or pull requests

1 participant