
在這個根本分不出是槓精、網軍、還是 LLM 的時代、與其追逐流量不如先確定流量是活人吧
https://aphyr.com/posts/389-the-future-of-forums-is-lies-i-guess
yeah I highly agree. For instance there is a saying in programming "first make it work, then make it fast"
@farooqkz @uffke @metaphil @kenney
I find that writing the docs helps me find both bugs and potential usability improvements, because it helps me step out of my own mind into an imaginary newcomer's, and that newcomer uses the code quite differently from the way I do. The newcomer is also less forgiving than I am. Thus careful documentation is important for the output it produces, but also for the effects it has on the developer and the code.
A hastily-drawn circle that isn’t quite closed, titled “Just make it exist first”.
Beneath it, a perfectly closed circle, titled “You can make it good later”.
@tomtrottel @kenney
Yes and no.
Something existing gives more concrete details, and at that new point you see more and clearer.
It is debt only if you leave it there for a long time. But initially it was a step that supported you in your climb of unknown and complexity.
Those do no mistakes, who start nothing.
make a mockup
management decides it is good enough
now mockup is in production and never touched again
I can't tell you how often this happened to me. I learned pretty quickly not to show my work until I was absolutely forced to. And when that finally happened, which it always did, I made sure to plaster warnings ("test system" or "WIP - output not verified" or "demo only") all over it and all its output. That still didn't stop them from trying to put unvetted systems that were still a WIP into production but at least I could say 'I told you so' later.
@kenney mvp
:
small good first prototype
make it great ( give it enaugh space to breath )
scale it
:
minimum viable product
:
Sir R.A. Watson-Watt would be proud of you.
Distance from couch now exists.
This is the only way I know. Sometimes even the draft is good enough.
@kenney There is however a fine art to making it exist first without digging any enormous holes that will haunt you for the rest of the product lifetime. That's one of the signs of a really good systems architect
For open source it's also often the case that make it work will pull in "make it work nicely" and "I've written an install document" people.
Sometimes even "I can't stand the random formatting in your repository can I please fix it" people!
@kenney this can be great advice for individuals like me who procrastinate.
Not so great when adopted by for-profit corporations. Case in point: "AI" companies.
There are no great writers. Only great re-writers.
@kenney My brother, who gets more shit done than anyone else I know, has a saying: "If it's worth doing, it's worth doing badly".
Which I think is pretty much the same idea.
I remember asking him many years ago what the key to getting shit done was, and he said "Start."