But I don't enjoy UX work at all.
So if I can get it to a "mud fence" level of usability, I'll need people with a shred of aesthetic sensibility, since I'm done around vi with the UI.
11–20 of 80 posts
But I don't enjoy UX work at all.
So if I can get it to a "mud fence" level of usability, I'll need people with a shred of aesthetic sensibility, since I'm done around vi with the UI.
> I didn't realize this going into it. I wasn't asking for a baby.
> It was a complete surprise to me, after 20-odd years of industry experience, that even writing a simple interpreter would produce a lifetime of work.
https://steve-yegge.blogspot.com/2007/06/rich-programmer-foo...
The things you do for themselves are the only things worth doing - because the value of all other things is merely derived.
Months go by, with lots of refactoring, "core" features and no progress at all. Some weeks were most productive than others though and just last month there was something usable.
So instead of doing what I always did, building more stuff, I setup a server, nginx, certbot, and released the damn thing. By released I mean it was available on a URL, but nobody knew about it. And that was calming, because it was out there and that was the goal.
That helped me mentally to just share it with other people and see what happens. And I did, and it wasn't bad, and it was fine.
I still don't have much time to spend on it, but I know it's outhere with people using it, and I can always work on it.
It does feel like you should know... but knowing all the parts does not mean you know the whole. The rules of chess do not make you a gramdmaster. The axioms of geometry, of predicate calculus do not make you know all theorems and proofs. Being able to program does not mean you know all programs.
I don't know if that's where true wisdom starts, or if it's procrastination at work.