I wrote a post that explains prompt caching by walking through the actual transformer pipeline step by step: tokenization, embeddings, positional encoding, attention (Q/K/V), and KV caching.

Most explanations I found online stop at "identical prefixes get cheaper." That never satisfied me. I wanted to understand what exactly is being reused, why a single whitespace change breaks the cache, and why temperature doesn't affect cache hits. So I built it up from scratch.

Tried explaining every concept with illustrations to make it easier to understand. The other thing I wanted to try: there's a "Margin Notes" button on every paragraph. Select any text you find dense, pick an action (simplify, analogy, step-by-step, quiz), and an LLM rewrites that section for you as you see fit. The idea is to customize the reading experience for everyone, some people want the math, some want an analogy, some want to be quizzed.

Would love feedback, it would help me figure out whether to keep adding content in this format. Thanks!

I think he is talking about Reality Labs division

I think it is better to prefer brokers that have their own clearing house

https://investorjunkie.com/stock-brokers/broker-clearing-fir...

Would like to leave this here: https://github.com/rcdexta/react-trello

Again, this is a pluggable trello-like kanban board built using React and Redux. It's highly customizable, uses event-bus to publish triggers/actions and supports touch devices.

Are you referring to this book: https://www.amazon.com/Zen-Buddhism-Selected-Writings-Suzuki...?

You mean Drawing on the right side of the brain? http://drawright.com/

I was wondering if there was another school of thought that I missed out completely till now! :)

Yeah, that's the one. Guess all the upside drawing confused my left and right :D

Found this recently: https://annot.io/

I learnt a lot about react codebase reading through this: https://annot.io/github.com/facebook/react

Easier to read annotated code unless the source code is well documented.

For a mobile app, I developed recently, I tried the following services:

https://www.nexmo.com/product/verify/ https://getprove.com/

In terms of ease of use and reliability, I preferred Nexmo. But however, I faced issues sending sms to VOIP numbers with Nexmo.

I ended up using Twilio and Parse (it was the backend anyway) to get a verification service running. You can use this http://shamadeh.com/blog/web/mobile/twilio/parse/2014/07/31/... as a starting point!

Here is a link to Twilio Lookup https://www.twilio.com/lookup

Twilio lookup gets you details about the carrier and whether it is voice/sms enabled. Basically used to validate if you have number that enables communication. This service is not the same as the verification API the OP is talking about!

There is are many including http://www.pro.com, http://www.redbeacon.com, http://www.homeadvisor.com/. Apparently the first one is backed by Bezos Expeditions! http://www.bloomberg.com/bw/articles/2014-09-24/pro-dot-com-...