borrow

4 ms·

1. 1.▲
   by borrow 2y ago

   It's self-reinforcing. If commit history is reasonably clean, the barrier to doing code archeology is lower, so you reach for it more often. And if you do code archeology often, you develop a better sense of what's a clean commit
2. 2.▲
   by borrow 2y ago

   Sounds interesting. What reading on such modern architectures would you recommend?
3. 3.▲
   by borrow 3y ago

   Novel among mainstream languages, but not unseen before: https://blog.adamant-lang.org/2019/operator-precedence/
4. 4.▲
   by borrow 3y ago

   Postgres (which is a wrapper around tokio-postgres, and as a result drags the whole tokio bloated dependency graph). I would love to have a purely sync alternative to that.
5. 5.▲
   by borrow 4y ago

   SEEKING WORK, EU, part-time remote contracts only A generalist, programming since ~2000 (professionally since 2008). Some areas I can help with: * math * advanced algorithms * interfacing with experts in other technical fields * prototyping
6. 6.▲
   by borrow 5y ago

   What if that particular unique ID is deleted right before the client requests the next page?