350 karma · joined May 2, 2019
Bookmarked. I'll think more about implementing it as a shell script.
Reminds me of this comment https://news.ycombinator.com/item?id=9224
Edit: I don't mean to dismiss your comment. I just mean to say I'm obviously comfortable doing what you described but it's not a trivial amount of effort even if it is conceptually straightforward.
Re: ssh-based chat. I found that post very very early on while exploring gitern as just an idea! Very formative of gitern.
You: Is this for food kiddies that want to be called foodies? All the foodies I know realize dumplings are just sheets of dough wrapped around a filling.
I'm currently working on a way to optionally add an email address for recovery.
Edit: Meant to add I've had a similar idea but it should probably be optional and configurable in a git config type way.
Assignment and rotation happens automatically. A chore is setup with a frequency, etc, then as users are assigned they are notified and they only need to intervene when they do the chore.
create: ssh git@gitern.com gitern-create <path>
delete: ssh git@gitern.com gitern-delete <path>
list: ssh git@gitern.com gitern-list [<path>]
pubkey add: ssh git@gitern.com gitern-pubkey-add <account> (pubkey on stdin)
pubkey remove: ssh git@gitern.com gitern-pubkey-remove <SHA256 fingerprint> <account>
pubkey list: ssh git@gitern.com gitern-pubkey-list
Edit: Eventually the cli will provide a lot more (and self document what's available) so I do recommend using it, but you can happily get along with these "raw" commands for now.
Current git hosts don't feel like they were made for programmers which is nuts! Even for the most essential and basic actions (all of what gitern provides at the moment), they feel kludgy. My intent is to carry a programmer-first approach for all needs programmers have around git hosts. I have SO many ideas on how to do this.
If you couldn't tell, I'm very happy to hear you had a positive impression lol. Thank you!
Assuming you're using the chore chart with others, you are now assigned the chore twice rather than once in the rotation of the chore. It's no more than a weak disincentive for missing chores. (A better disincentive would be fines as I write about here https://keyankousha.com/the-best-chore-chart-in-the-world.ht... ... which I haven't implemented because I didn't need them in my housing situation as the weak disincentive of more chores worked fine.)
(I don't use that rsync service so I'm just guessing as to how you use it. If you can provide more context, I might be able to help further.)
At the moment, the feature set around git workflows is not more than just providing authorized access for several users to a git repo itself but I'll be providing more features around this soon in a way that improves on what currently exists on git hosts.
If you're at a small startup, you'll want a lot.
When you're at a larger company, things typically get specialized, there will be dedicated product folks, and you'll find programmers with 0 product knowledge.
You can come up with complicated models as some do, but I prefer simple models (3 dimensions or less): What do you want? What are you willing to build/iterate on for years? What can you find feedback on fast?
(1) because if you're using it you'll build something nice and have a lot of insight internally.
(2) because you'll need to work hard, fast, and for a long time to make something great.
(3) your reward systems depend on feedback.
Sometimes answering these questions isn't straightforward so I recommend building a lot of smallish things without an outcome in mind before answers to these questions become clear. You tend to know when you're well suited to something because you can't stop yourself from coming up with ideas and working on it.
Example: I spent a long time building/understanding http://choremate.co because it's something I NEEDED. Despite finding insight, (1) I found the work hard to do because it was boring (I don't enjoy CRUDing web apps), (2) I'm not innately interested in the research domain (behavioral and institutional economics), (3) feedback is best found living in a large shared household like a coop or fraternity and I don't live in that situation.
Perhaps I'm an odd duck (I am) but I think current git hosts are no longer meant for hackers and I really wanted a git host that is and that's why I'm building gitern.
Gitern is just getting started and only has essential features today but we already have a few differentiators: - all auth is done with ssh keys (no password or email required) - arbitrary repository paths allowing for (1) familiar namespacing and (2) access control (eventually) - a cli-first ui - private repos are default
I think better tools make for better hackers and I think git hosts can be a lot better.
I'll be in the comments if anyone wants to ask questions or scold me or something :). Very very open to feedback!
Cheers everyone
Even with the huge financial incentives supply of developers is constrained by the mental capacity/desire to do the often time consuming and tedious task of learning the development skills.
Yes you have to write it out but this cost:
1. forces you to only save what matters 2. encourages you to compress the info which requires you to understand its essential parts
I record the notes as I encounter noteworthy things. At the end of a book the trello list is effectively a compressed book and index to the actual text.
- https://en.wikipedia.org/wiki/John_Carmack - https://twitter.com/ID_AA_Carmack
He might not be a 10+ digit billionaire but he's likely at least a 9 digit millionaire.
People really do underweight enjoyment when they choose something to build. There's a lot of dimensionality when choosing something to work on, but enjoyment is one of the most important.
You're in pretty rarefied air. There's only 20-25 a year and they've been doing it for ~10 years. So maybe there are 250 Thiel Fellows total. [1]
There's a list of notables on [1] that you might be able to reach out to, or maybe you could contact someone doing admin at the Fellowship to connect you.