Dev.to
7/17/2026

I named the same side project nine times before I wrote any of it down
Short summary
A developer recounts stalling for months on an Amazon seller profit-tracker side project because it was scattered across nine folder names with no shared documentation. The real blocker was never Amazon's API complexity but the absence of a single source of truth for identities, credentials, and decisions. The fix: one living page, updated in the same sitting whenever anything changes, read before touching anything else.
- •Nine folder names for one project meant every session restarted from zero
- •Amazon SP-API has four login types and non-obvious credential rotation rules
- •Solution: maintain a single documentation page updated immediately on any change
Generated with AI, which can make mistakes.
Is this a good recommendation for you?



