This person takes specific claims from the book and tries to dispute them, while ignoring that the book’s number one big-picture idea of “trauma is unprocessed emotions and memories physically stored in the body” remains the conceptual grounding for all modern non-cognitive trauma processing methods like EMDR (which are clearly effective, even as we do not fully understand e.g. the neurological mechanism by which the adaptive information processing network functions). He then points you to an older article of his that is behind a paywall.
I have my issues with van der Kolk’s work (I would personally not recommend The Body Keeps The Score to most people), but this is sloppy embarrassing clickbait.
I have criticisms of both tools like Claude Code and how applicable the 'pair programming' metaphor is here, but strong disagree that the person driving during pairing is the one who learns the most (or perhaps the implied "and the non-driver doesn't learn enough"). A good dynamic pairing session is equally valuable for both participants, even if there's a skill gap, and even if you're not alternating drivers as often as you should.
For folks who are interested in the UX design of chorded layouts, Artsey and Ardux (https://ardux.io) might be of interest. Artsey is a specific 2x4 one-handed chorded layout (of which Ardux is now a more robust implementation, with optional variations for slightly larger numbers of keys) that borrows a lot from colemak. I'm a big fan.
I particularly appreciate the simplicity of a 2x4 layout — OP's device rocks, but I worry about the ergonomics of thumb movement.
This project is or will be a worker-owned co-op, as evidenced by the strict requirements placed on anyone who registers a .coop domain name. I imagine at least equal ownership (if not risk and power) is a given in this specific instance, and profits will explicitly not flow upwards to shareholders who are not also workers.
Just basing things off of Android won't get you the "measured in days to weeks" battery life people appreciated about the Pebble, and building your own watch OS from scratch optimized for battery life but still supporting BLE connection to a phone sounds like a great way to spend several years.
For most people, using e-ink for general-purpose computing tasks is going to be so jarring and unpleasant that it's extremely difficult to recommend to anyone who doesn't have severe eyestrain issues and has tried and failed more typical accommodations. I adore e-ink for reading, and own several e-ink readers in various form factors, but the tradeoffs just don't make sense for a desktop computer for most people unless staring at your monitor for eight hours a day is causing you physical harm.
This looks great! I’d love to see some of the fantastic context in your lovely Twitter thread included on the website.
As someone who’s currently in industry rather than academia, I interpreted “virtual conference” as “a Twitch or YouTube stream, and likely some sort of chat space like a Discord”. That landing page does a great job of explaining the technical underpinnings of your tool, but doesn’t actually explain what sort of site/services the web server actually serves!
Even just including the GIF from the beginning of your Twitter thread would be super helpful.
It's really not fair to describe the current situation as a "forced WFH experiment". We're trying to work and be even remotely productive during an unprecedented global pandemic, and also happen to be working from home.
You can't copyright a game mechanic, but you can copyright content. This is why Words With Friends has a different board layout, tile distribution, and tile point values from Scrabble.
In that Set C&D, the infringing implementation is using art assets from the copyrighted Set game. Presumably, a version with different colors/shapes/etc (and a different name, so as to also avoid trademark infringement) would be totally fine.
These days it's mostly still just "use Cordova/PhoneGap", yeah.
For Flappy Royale (http://flappyroyale.io, https://github.com/flappy-royale/flappy-royale) we built our own native web view wrappers for both iOS and Android, but that's mostly because we already had extensive native iOS/Android dev experience ourselves and wanted more control.
In my experience Cordova/PhoneGap come with a lot of cruft and bloat if all you care about is a canvas and a handful of other hyper-specific native API hooks. At least in the sense of engineering and tooling complexity; I can't speak to runtime performance considerations, except that it should be irrelevant on iOS since everything's using the same WKWebView under the hood.
I'm guessing that means you rolled your own canvas API code, rather than using a library like PixiJS. Is that something you'd consider open-sourcing, or is it so tightly integrated with game-specific logic that it wouldn't make sense?
I have a smart trainer, rather than a 'dumb' stationary bike, because the thing that gets me to ride a bike in my apartment without the satisfaction of getting somewhere or feeling the wind rushing in my face is getting to measure my performance and see numbers improve over time.
I get that I'm not Peloton's market (they don't care about nerds who build their own kit, and that's probably the right choice) but I 100% understand why this stuff matters.
This is a cool idea, but also a pretty unsolved problem, even in digital games. Heck, computers can't even procedurally generate decent crossword puzzles.
Best comparison point I can think of are roguelikes, but even if you can figure out a way to make custom hardware build-out easy, roguelikes largely work by making replayability cheap. It's hard to build an on-ramp to teach players about the interactions of complex systems when each playthrough costs them $50+ and takes an hour plus transpotation time.
I wouldn't necessarily frame that as an inevitability of Dropbox as a product, as much as an inevitability of the traditional VC funding model.
It's likely you could build a very healthy business selling people file syncing — I personally use a tiny minimalist Dropbox competitor that seems to be doing just fine. The hypergrowth demanded by investors when you take on $1.7B in funding is what's the challenge.
An answer there would likely be smaller teams. For context, when I was at Pivotal (on the consulting side, years ago) a team of 4-5 pairs would be considered quite large.
Also a problem that's solved by the combination of pairing and frequent communication. You don't need full context on anything yourself, as long as the combination of you, your pair, and anyone you can grab within arms reach can fill in the blanks.
I have my issues with van der Kolk’s work (I would personally not recommend The Body Keeps The Score to most people), but this is sloppy embarrassing clickbait.