Measuring Developer Goals - IEEE Article

muras.eu 2 miesięcy temu

List of a developer goals from IEEE article: Measuring Developer Goals.

Information gathering:

  • Ensure documentation is up to date
  • Understand the context to complete a work item
  • Explore the method solutions (e.g. bugs, design)
  • Finding information (e.g. documentation, codelabs, API examples)
  • Find an expert

Plan and track work, and manage approvals:

  • Know what to work on next
  • Coordinate work with peers
  • Ensure my launch complies with legal, privacy, and safety requirements
  • Have my cross-functional squad aligned on launch readiness
  • Get my plan approved
  • Design and paper a considered plan

Develop, test and commit code:

  • Write advanced quality code
  • Ensure the code contributed by others (e.g. teammates, AI) is advanced quality
  • Understand the behaviour of existing code
  • Create or keep holistic test coverage
  • Investigate unexpected behaviour locally
  • Integrate fresh tools / technology into existing services and systems

Experiment, release and rollout:

  • Safely rotation out changes to production (e.g. features, models, fresh releases)
  • Run an experiment
  • Analyze experimentation results

Monitoring, reliability and configuring infrastructure:

  • Ensure my product stays within SLO commitments
  • Investigate issues in production (e.g. crashes, outages, unexpected behavior)
  • Improve strategy performance
  • Ensure my builds stay greem (e.g. build gardening rotations)
  • Improve reliability and avoid production problems

Data management:

  • Ensure data I’m liable for is fresh, reliable and of advanced quality
  • Develop and manage data processing pipelines
  • Ensure data I’m liable for is safe and complies with regulations
  • Analyze, visualize and realize data to make insights
Idź do oryginalnego materiału