7,151 karma · joined December 22, 2008
You can also book time with me at tim.do/rr
timdorr.at.hn
https://twitter.com/PodcastAddict/status/1261651512947691520
Plenty of proprietary engines are in use today. And you've got FOSS options like Godot and Blender. UE's definitely the biggest, but other options aren't going away any time soon.
Meanwhile, our testing rates have shot up to the ~7500/day range and our positive test rate has gone from ~25% down to 13.2% today: https://docs.google.com/spreadsheets/d/1wrGsD3T_JIvKwsudQwVH...
It's likely that simply setting a particular cookie with a dummy value would bypass this.
Meet == Zoom. It's video conferences for businesses.
Duo == FaceTime. It's video calling, with integrations into the Phone app on Android.
I converted the streaming and Autopark clients in the Tesla API gem from EM to Async and has been great: https://github.com/timdorr/tesla-api/blob/master/lib/tesla_a...
No more globals, which makes it much safer to use inside of threaded job runners like Sidekiq.
This is the Electron app: https://github.com/stream-labs/streamlabs-obs/
This is the wrapper library for Node: https://github.com/stream-labs/obs-studio-node
Or the virus mutates with deletions, the fatility rate goes down.
Or when testing capacity finally reaches demand and lets us find infected folks sooner, the fatility rate goes down.
I'm not trying to be mean to you, just pointing out that there are potential positive outcomes ahead. We honestly don't know what's going to happen next, but there are plenty of reasons to have hope.
But if you're done with that notification, why would you want to stick around? You wouldn't yet be done by definition.
It's a fantastic tool for accountability and can be a huge driver for performance. Including some sort of metrics is really the key. You can see those grow and change over time, which can be a great motivator. And you can change them whenever they stop making sense, so they're more flexible than something like OKRs that might be locked to a quarter.
I recommend it even to solo bootstrapped founders. Just having this history of progress is great to look back on. And even sending it to yourself gives you something to work towards every week.
Example: https://github.com/timdorr/tesla-trip/pull/107
The show the recent release notes, changelogs, and recent commit history behind what you're about to upgrade. That's immensely helpful when deciding what you want to update in your dependency list, especially if there are breaking changes. Dependency management is much less of a pain this way.
Bonus points if it renders to Markdeep (or an equivalent) to be re-rendered as SVGs or whatever later on.
Edit: Here we go - http://asciiflow.com/
We've still got a lot to build, but the goal is zero config deployment for any app/service.
I like it because of its minimalism and function over form.
I hate it because I have no idea what any of it means.
That's not a critique. It should stay high on the SNR, as it clearly serves a purpose. I'm just jealous because I know other folks that have figured this stuff out and are likely far smarter than me are making a ton of money right now. PEBCAK.
Any idea where I should start so I can grok this site better?