For people curious about the Roam API and confused by the syntax, or interested in why Conor went with Datomic/Datascript and not a traditional database, this older talk by Roam developer @mark_bastian is a great overview.

Here’s a SPAC thread covering some basics for new followers. I will pin this to my profile if you want to share to anyone interested in SPACs.

SPAC timelines consist of these stages:
IPO – SPAC raises cash and begins trading as a unit. The cash is placed in Trust.
Searching phase – After IPO, the SPAC management team looks for a company to merge with. This is typically 24 months but can be shorter depending on the SPAC

LOI/Rumor – A letter of intent is announced publicly or Bloomberg/Reuters etc. breaks news of a rumor that a SPAC is close to a deal with a target.

The LOI/rumor stage does not always happen, most go straight to a definitive agreement. Rumors should only be considered to have value if from a trusted news source, internet rumblings are pure speculation. During this stage, a deal can still fall apart and not be signed.

Definitive agreement (DA) – deal officially inked. The SPAC begins filing paperwork with the SEC to have the merger approved to take the target company public. This process typically takes 4+ months after the DA is announced.

I’ve been flooded with Snapchat Spotlight questions after posting I’ve qualified for a payout 4 times. Here are the answers to the most common questions I’ve gotten in my DMs. These answers are my own experience and may differ from others .

Q: How will I know if I am getting paid?
A: You will get a message from Team Snapchat that looks like the below message 2-3 weeks after the snap has gone live. At this point it important that you verify your email address.

Q: How long after I’ve been notified I qualify, will I know for how much?
A: my experience is that usually 7-10 days after you get the qualifying message, you get a message with the amount, it will look like this. This message will include a unique access code for HyperWallet.

Q: How do I set up my HyperWallet?
A: Around three weeks after you get the payment amount you will get an email to your verified email from Snapchat Pay. It will look like this and will require you to fill out some tax forms, takes like 10 min.

Q: How long does it take to actually get the money in my account?
A: it took me like 7 days from when I had my HyperWallet approved before I got the money into my HyperWallet account. I recommend you set up auto withdraw. You can send money to PayPal, Venmo or bank account.

The 2018 State of JavaScript survey is out. They got 20,000 responses and have some delicious, delicious data. I'mma thread in some highlights:

First up: JavaScript flavors. There's TypeScript at 47% adoption, a tad higher than npm's own survey results (which said 46%). npm's survey is coming up again soon and will ask about TypeScript in a lot more detail.

I really, *really* like SoJ's "would not use again" question, which lets people who've abandoned a tech self-identify. This is noticeable in the graph above with Flow users -- 41% of people who've used Flow say they wouldn't use it again.

Now JavaScript frameworks. It's been a full year since npm's survey, so these numbers differ from ours in the directions I expected:
React 65% (vs. 60%)
Vue 29% (vs. 24%)
Ember 5% (vs 4%, I was expecting a bigger rise)

But there's a shocker in here: Angular.

npm's survey had Angular at 40% last year and SoJ has it at either:
- 58% (if you include those who don't want to use it again)
- 24% (if you count only those who like it)
Since npm's question didn't ask if they intend to *continue* using it I think that might explain this.

@zkat__ I'm in the position that I actually find npm / yarn the best ecosystem. Whenever I use something else I always end up stubbing my toe into something thats missing / feels wrong.

Ex. Cargo seems to neither have a concept of devDependencies nor peerDependencies.

I also can't understand why it wouldn't have an "add" command to add a new dependency. And I'm no fan of Toml, json is greate (easy to parse and build tooling around), and the better option in my opinion would be json5.

C / C++ seems to just not have language package managers. The linux / bsd crowd seem to have decided that the system package manager also should be the language package manager. Which might have been fine if every Linux distro used the same system package manager.

Instead we end up with a N x M problem. Where we have a bunch of different operating systems and they all support multiple system package managers. So there's no easy way of distributing, referencing and updating C / C++ packages.

It is also my opinion that the compiler / runtime should be a package dependency. I don't like Rust's split between rustup and cargo (they should have been one tool). Similarly it would be better if you added Node as a dependency to package.json, that way we wouldn't need NVM.

A thread about Eastshade's bike mechanic!

When I originally thought of putting a bicycling in Eastshade, I was pretty sure it wasn't going to work, for the simple fact that if it was easy, we'd see a lot more rideable bikes in games. Well, I was wrong. It took a mere week.

Its essentially a first person controller with extra momentum, resulting in the the movement direction lagging behind your look direction. Then I used the angle between the look and the movement to dictate camera "bank" and handle bar rotation, and voila! Game changing feature!

The look of the bike was harder than the movement. Bicycles are fairly modern, so it was tricky to fit it to the setting. I took some artistic liberties and settled on a penny farthing (but wooden), ignoring how impossible that would be to ride on the rugged terrain in Eastshade.

Surprisingly, the hardest part was sound. It didn't feel like riding a bike until I found the right sounds and how to trigger them. For a while I was stuck thinking too realistically. A penny farthing is fixed gear, pedaling sounds nothing like a regular modern bike.

Finally I abandoned realism and went with sounds normal people would associate with biking. We're all so used to modern bikes that we strongly associate the distinct ticking of a freewheel mechanism (think of the sound when you stop pedaling and coast on a modern bike).