Store

Store

Things I’ve written down so you don’t have to hire me to learn them.

[[EBOOK TITLE]]

[[PRICE]] · PDF and EPUB · [[N]] pages

[[WHAT IT IS. Two or three sentences. The problem it solves, and who it’s for. Be specific about the reader: “for backend engineers who’ve just been handed responsibility for a system they didn’t build” beats “for developers”.]]

What’s inside:

  • [[CHAPTER OR OUTCOME]]
  • [[CHAPTER OR OUTCOME]]
  • [[CHAPTER OR OUTCOME]]
  • [[CHAPTER OR OUTCOME]]

[[COURSE TITLE]]

[[PRICE]] · [[N]] modules · opens [[DATE]]

[[WHAT YOU’LL BE ABLE TO DO AFTER FINISHING IT. Write outcomes, not curriculum. “Design a system that survives a 10x traffic spike” sells; “Module 3: Load Balancing” does not.]]

You’ll finish able to:

  • [[OUTCOME]]
  • [[OUTCOME]]
  • [[OUTCOME]]

Code and templates

[[Production boilerplate, architecture templates, checklists. List them as you build them — or delete this section until you have one.]]


Questions

Refunds?
[[YOUR POLICY. A no-questions-asked window converts better than it costs. 14 or 30 days is standard.]]

Do you invoice / can my company pay?
[[YOUR ANSWER]]

Purchasing power parity pricing?
[[Worth offering. Gumroad supports regional discount codes and it meaningfully widens your market.]]