PureType
Get started
  • Overview
    • What is PureType?
    • Getting started
    • Supported languages and technologies
      • Elixir
  • The knowledge journey
    • Overview
    • Approach to learning
    • Activities and exercises
    • The knowledge landscape
  • The learning platform
    • Overview
    • Learn
    • My Progress
    • Team Progress
  • Integrating PureType
    • Overview
    • Feedback principles
    • SCM integrations
      • GitHub
    • IDE extensions
      • Cursor / Visual Studio Code
    • Learning integrations
  • Working with PureType
    • Data handling
    • Data residency
    • Privacy policy
  • Support
    • Help
Powered by GitBook
On this page

Was this helpful?

  1. Integrating PureType

Feedback principles

The scope of feedback that PureType aims to provide

During the feedback stage — regardless of time or location — PureType aims to be guided by the following principles:

  • Empower Developers: Enhance the skills and capabilities of developers.

  • Identify High-Level Issues: Detect problems that occur between modules and functions, rather than at the single line level

  • Embrace Subjectivity: Focus on subjective suggestions; leave objective rules to traditional linters.

  • Promote Idiomatic Code: Guide developers to write idiomatic code from the start to avoid bad habits setting in

  • Teach Something In Each Interaction: Don’t just rearrange code. Refactor (correctly) and attach a lesson with each change

  • Take a Load Off: suggest patterns that are hard to notice, but make the code much simpler

PreviousOverviewNextSCM integrations

Last updated 6 months ago

Was this helpful?