Captain's log-

Deciding on analysis pricing model and implementing analysis types

What I worked on today

  • Had limited time and felt a bit depressed about handling analysis pricing.
  • Debated whether to allow multiple analyses per monitor, ultimately deciding not to for now due to added system complexity.
  • Concerned that forcing extra monitors for the same URL may be unfair for users/B2B from a pricing standpoint.
  • Implemented analysis types, choosing a model-based approach for better flexibility in future expansions.
  • The implementation path was bumpy, with multiple variations before settling on a structure.
  • Not proud of today's progress, likely impacted by poor sleep.

Lessons learned

  • Simplicity vs. fairness is an ongoing challenge in pricing models.
  • Choosing a scalable implementation early on prevents future refactors.
  • Productivity is closely tied to mental and physical well-being.

Challenges faced

  • Struggled with the pricing model decision and system complexity.
  • Lack of sleep affected motivation and decision-making.

What’s next

  • Finish the monitor header UI.
  • Implement job logic based on the analysis type structure.
Photo of captain Davy de Vries

Davy de Vries

Captain 🏴‍☠️