662 karma · joined September 21, 2018
Most 1:1s have been driven by me, at the explicit behest of the manager. "I'm here for you" and "this is your time" are/were common phrases. I found this particularly annoying as a new grad when I really didn't know what I didn't know and just wasn't getting a lot of mileage out of those conversations.
You would have a case if Vercel has no revenue, or no chance of becoming profitable. I don't know their numbers, and I'm sure the multiple is high, but relating this to EVs is a non-sequitur.
Why?
You could also have some kind of AI-driven testing/verification program -- Copilot and <other program> could go back and forth multiple times until the program is deemed correct and returned to the user.
The negative is not even true -- no one can guarantee that no countries will ever be covered in water at any point in the future, even if we had presumably gotten the rising temperatures "under control" twenty years ago.
Also, the app has sooooooo much more functionality than people realize. Plus, there is a lot of functionality that ships with the app but is behind a feature gate, meaning that it is turned off for the majority of users. There's lots of internal tools for adjusting feature gates on a per-user, per-region, per-whatever basis, in the name of user research as well as just safely deploying new features at scale.
This being open source is a HUGE draw. It means I don't have to trust you as much, because the code is out in the open for security researchers to poke at. Do you have a bug bounty program?
I assume this works via an API as well, not just web based sessions? My use case is an online multiplayer game written in Unity.
Most people at Facebook believe that FB is good for the world, Zuck is a good leader, and that we are working to address dubious ethical decisions made in the past. Sure, FB itself may be a bubble, but HN is even more of a bubble :)
You know that person who you always go to when your program malfunctions? Or the high level engineer at your company who also seems to know how to diagnose a site incident or other strange software problem? What about the technical founder who leads a startup to do something new and extraordinary? Or how about the person who wrote your framework/language of choice? These are people who understand CS fundamentals, irrespective of whether they have a formal CS degree.
A few are, such an hjkl being on the home row, but the rest are more semantic (for example, "t" is "unTil", "f" is "From", "a" is "append", "i" is "insert", etc. So all of those lend themselves to muscle memory from repeated use but aren't particularly better or worse on any keyboard layout. Dvorak keeps "j" and "k" together (in the place where "c" and "v" are, respectively), which is a nice touch.
> This thread convinced me to try switching to Dvorak but I'm a bit scared after reading your comment. It's not clear from your comment, did you switch back to QWERTY or are you still giving it a shot?
I switched to Dvorak about a month ago, and have no plans to switch back! It is a definite improvement in comfort, which I expect to translate to a speed improvement eventually. Nowadays when I type anything at all in QWERTY I wonder how I ever put up with contorting my fingers into such strange shapes to type the simplest words -- not to mention how so many words have almost zero hand alternation.
I recently made the switch from QWERTY to Dvorak, during a 2 week period while I was in between jobs, and it was one of the most frustrating things I've ever done. Over a month later and I'm back up to a plodding 60 WPM (from a glorious 120 with QWERTY). Not to mention how shot my vim keybindings are!
Maybe if I eventually switch again it will be less painful, but the experience has taught me that typing is almost 100% an exercise in muscle memory.
Anyway, my point is, I wish I could be the kind of person that could type fluently in multiple keyboard layouts, if nothing else then just for the heck of it, but I'm not sure I'll ever have the kind of time to make that happen. Cool project though! There are certainly words and bigrams that are needlessly hard to type in Dvorak.