5 ms·
The most successful company I ever worked for (late 90's, the founder was a billionaire for a few months after the IPO, 99.9% of HN readers use an evolution of
by faster 8y ago
The most successful company I ever worked for (late 90's, the founder was a billionaire for a few months after the IPO, 99.9% of HN readers use an evolution of what we built every day) had a policy of rejecting any proposal for a tech feature or significant improvement unless it was properly documented.
We had a collection of templates for the types of documents we used. I could create a feature proposal in an hour or two, and the template ensured that all first-round questions were answered out of the box, saving many hours of staff time.
The tech founders set this up and forced everyone else to use it and once we saw the value, peer pressure kept it going. It worked incredibly well.
We weren't writing RFCs, but we had a doc process that respected (and saved) everyone's time and attention. That helped us move fast together. It really worked.
- username3 8y ago99.9% of HN readers use an evolution of what we built every day Electricity?
- quickthrower2 8y agoBrowser? 0.1% use curl maybe.
- audiolion 8y agoROI (Radio Over Internet)
- seb1204 8y agoAren't the bug templates on github the same approach. A template to ensure key questions are addressed and information provided. The key is to find the sweet spot on asking just enough and not much time for something that might not go ahead.
- dalex00 8y agoAny chance you share those?
- faster 8y agoI could probably find them, but we used Framemaker and I don't know whether I have anything that can open them now.
- renox 8y agoFramemaker? This brings back old memories (circa 1993) the only editor I liked.. All the other editors I've used since then feels like a downgrade (for technical documentation purpose at least)