Tools we actually use (2018)
Most “tool stack” lists turn into shopping carts. This one is simpler: a snapshot of a setup that keeps small projects moving. The theme is low friction and plain formats — so you can switch machines, collaborate, and pick things up again months later.
If you’re building as an indie dev (or on a small team), the best tools usually share the same traits:
- They work well with text files.
- They’re boring in the best way.
- They don’t fight your workflow.
- They help you recover when something goes wrong.
Editor + terminal: pick something you can live in
Your editor doesn’t need to be perfect; it needs to be reliable after a long day.
Baseline setup that pays off quickly:
- Format-on-save (or a single command) so style doesn’t become a team argument.
- Linting that catches mistakes early, but doesn’t spam noise.
- Fast search and decent file navigation.
If you want one “start here” reference, the Git documentation is still the best place to build strong fundamentals.
Version control: treat it like a seatbelt
If it’s not committed, it’s easy to lose. If it’s not pushed somewhere you don’t control, it’s easy to regret.
Practical habits that scale from solo to team:
- Commit small and often.
- Write commit messages that help Future You.
- Push to a remote regularly.
- Keep at least one backup outside your primary host.
The official docs are worth the time: Git docs.
Design + assets: lightweight, portable tools
Indie projects rarely need a huge creative suite, but most need some graphics: icons, screenshots, basic banners.
- Inkscape for vectors (logos, icons, simple diagrams).
- GIMP for raster edits (cropping screenshots, quick touch-ups).
Both are widely used, well documented, and they keep your output files easy to share.
Docs, notes, and references: write like you’ll forget
The highest-leverage “tool” is a habit: leaving yourself breadcrumbs.
What works:
- A short README per project with run/build instructions.
- A “notes” file with the weird edge cases you hit.
- Links to upstream docs rather than copying big chunks.
For web-facing work, keep MDN Web Docs close.
Shipping simple sites: Hugo + Nginx + a CDN
For static content (docs, small marketing sites, notes), you get a lot by keeping the stack simple:
- Generate the site (Hugo).
- Serve it fast (Nginx).
- Put a CDN in front (Cloudflare).
Start with the official docs:
There’s also a practical walkthrough here: /guides/hugo-nginx-cloudflare/
A security baseline that fits in your day
Security doesn’t have to be intense. A few “cheap wins” remove a huge amount of risk:
- Use a password manager.
- Turn on MFA for your email and code hosting.
- Keep recovery methods up to date.
- Assume email is the root account for everything.
If you only read one page this month, make it a phishing guide:
And here’s our short checklist: /security/phishing/
A reasonable starter kit (if you’re overwhelmed)
If you’re starting from scratch, don’t overthink it:
- An editor you like.
- Git + a hosted remote.
- Inkscape + GIMP for visuals.
- A simple deployment path (static when possible).
- MFA and a password manager.
Everything else is “nice to have” and can be earned later.
Related
- RailsGirls note: /release1-2-railsgirls.html
- Bacon Screensaver: /release1-2-bacon.html
- About: /about/