tmslnz

Troika! Hello from a friend in London :)

You took the words from my mouth :) Selling tents to clueless SV customers with disposable cash, with a not-so-veiled promise they can rent them out on Airbnb.

It's the lime scooters of "housing": no permits, no safety, lawless, convenient, short-sighted.

The guru guy, and his tasteless leveraging of someone's personal tragedy to his own grift is incredibly out of touch – provided even that is not made up.

We use a loose version of it in my small company.

It helps with two things: - 1. A little easier to be consistent across projects so not to reinvent the wheel every time - 2. The prefix increments as new folders are added during a project, painting a convenient picture of “progress” as things move along.

We tend to have: 10 to 19 reserved for admin stuff, like Admin, Incoming, Outgoing, Documentation, Meeting notes, etc.

Then anything from 20 onwards is ad-hoc per project

We also timestamp children of Incoming and Outgoing, with an ISO prefix. This is very useful to keep track of what was received and shared and when.

Overall the goal is to have as little protocol as possible to prevent total chaos. Anything more than that is usually too much to ask or doesn’t stick longer than a single project.

  10. Admin
  11. Incoming
    2023-10-12 sender, subject
  12. Outgoing
    2023-09-01 Estimate
  13. Documentation
  20. Design
  30. Production
  40. Blah

I say FruitMaster

We use and swear by Opalstack.com, which is made by some of the same peeps that worked for the may-as-well-be-defunct Webfaction.

Full SSH access, generous limits, very active community.