An easier (more fun) version of this with some context is here: https://x.com/olshansky/status/1892069988707729614
964 karma · joined August 20, 2012
An easier (more fun) version of this with some context is here: https://x.com/olshansky/status/1892069988707729614
drizzle.team is alway delivering.
Add support for Paul Graham's outdated RSS Feed. OpenAI research. Etc...
Leave a request or a star!
Also wrote a full blog post about it here: https://olshansky.substack.com/p/no-rss-feed-no-problem-usin...
1. X account: https://x.com/johnrushx
2. Directory guide: https://johnrushx.substack.com/p/directory-playbook-build-grow-and
I've been following him since 3K followers and his free X account is an absolute treasure trove of knowledge.I would start by going back and studying all of his threads.
I'm comfortable git fooing w/e is necessary, but ever since we adopted this, git related conversations went to almost zero. It's great.
Move Fast & Document Things [1]
My goal wasn't to be philosophical but share actual tips on how our small team [2]
enforces (not automated, not AI, but deep, hard reviews) a culture for
writing code for ourselves and each other.All my personal friends who are engineering leaders at other orgs said "We do the same thing but you actually wrote it down".
Would appreciate ↑ if it brought anyone value!
[1] https://olshansky.substack.com/p/move-fast-and-document-thin... [2] https://github.com/pokt-network/poktroll/graphs/contributors
Sometimes you get so much value out of a free service you feel the need to tell the world :)
I wrote a blog post about this: https://olshansky.substack.com/p/from-pc-personal-computer-t...
I keep it public here: https://github.com/Olshansk/olshansky-bot
- Ratio of code:documentation INSIDE the source code
- Directory structure depth is “just right”; not too deep nor too shallow
- Number of dependencies is “just right”; don’t build things yourself, but also don’t import the whole world
- TTLD (Time To Local Dev); how simple is the getting started guide in terms of copy-pasta commands + automation + the right amount of context + easy-to-use tooling
- Code culture; follow industry best practices and make it clear where & why you deviate
My personal favorite one: `make todo_list`
We use keywords (TODO, OPTIMIZE, HACK, etc…) through the codebase and make them easily searchable with make helpers.
Ref: https://github.com/pokt-network/pocket/blob/main/Makefile#L5...
Message me on twitter @olshansky (DMs are open) if you want to join a < 10 person team to build out the next version of the protocol!
The best part of the story for me is the work-life-balance he's able o achieve.
``` After realizing how much anxiety having a phone nearby that is on all day long has caused, I have a feature request for a future version of iOS: Dumb & Dumber.
Dumb: Voice and text mode. Dumber: Voice only mode. ```
If you think about it, there are many improvements that could be made to basic networking protocols (TCP, IP, HTTP), but since the standards were set "in stone" so long ago, it is difficult to change now.
I should have said that it's very limited and much more difficult to use than Ethereum's smart contracts.
I also wanted to avoid going into a deeper discussion that would involved the potential adoption of segwit, which would enable lightning networks and a bunch of other sidechains.
- No one ever