Skip to content

Instantly share code, notes, and snippets.

@kevincoleman

kevincoleman/Considerations.md

Last active November 26, 2019 18:18
Show Gist options
  • Save kevincoleman/e20b5ad846ce9f3f587f9937a4769954 to your computer and use it in GitHub Desktop.
Save kevincoleman/e20b5ad846ce9f3f587f9937a4769954 to your computer and use it in GitHub Desktop.
Download ZIP
Things to consider when writing features.
Raw
Considerations.md

Considerations when writing code features

  • code complexity
  • overall amount of work
  • speed/time to production
  • code obfuscation vs simple readability
    • developer skill threshold for comprehension?
  • extensibility
    • modularity for reuse
    • separation of concerns
  • testability
    • useful test boundaries

Who’s it for?

When architecting a feature, it’s important to ask “who’s it for?” While writing a code feature very quickly to please the client, it may damage the experience for future devs. On the flip side, architecting a feature with excellent test boundaries might be great for future devs (and ultimately the client), but it could ignore the urgency requirements of the client. By asking who we’re architecting for, we can gain clarity in what factors should be most important.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment