3 ms·
> A lot of these things happen with or without AI. Of course the AI had to learn from somewhere. In previous discussions I've been told that certain kinds of e
by zahlman 1y ago
> A lot of these things happen with or without AI.
Of course the AI had to learn from somewhere. In previous discussions I've been told that certain kinds of executives may naturally write like this and/or prefer for others to write like this. But now the style has become homogenized and ubiquitous, and I personally just find it extremely grating.
> This site is run by a VC.
Sure. But the VC culture here is about trying to connect VCs with people who want VC funding. It's not about marketing the resulting product.
> So what is the right way to write about projects? I've thought about writing something up that I'm building and it probably would have been similar to this structure.
Be up front about what your project does, and use only the plainest language to explain what it actually is. If you contrast with known alternatives, make sure we can directly understand your design taste/aesthetic and why you were motivated to make another one. Are you trying to provide something faster? simpler? more featureful? Or on the other hand, is it something you just re-created because you have a personal interest in things like it? It's perfectly okay to do that, and preferable to be honest about it.
If you're passionate about the underlying design, consider describing it in long-form prose.
Give a brief overview of how to use it. Not in a way that tries to convince us that it's easy to use, but in a way the directly illustrates that. Show, don't tell. Even if you have a full README already, repeat a simple example or three.
And please, don't say things that should already be obvious from the fact that you're posting it in the first place.