finiteloop
Joined 18 years ago
Karma
1,123
Submissions
84
Member since
Mar 26
Recent submissions
Comment · 5 years ago
Excited to work with you!
Comment · 5 years ago
I am the COO of Salesforce. Two of the top ten jobs on Indeed are Salesforce Admin and Salesforce Developer, and the jobs are distributed around the world. We have a ton of stories of folks transitioning into the ecosystem and developing an extremely successful career.
Notably, our certifications are freely available at https://www.trailhead.com/. You can get started, learn, and get credentials for free. It is a great place to start, and we purposely made our learning and credentialing free so we could make it as easy as possible for folks pivoting mid-career into Salesforce.
I would be happy to point you in the right direction. My email is [email protected].
Comment · 5 years ago
One of the best quotes in the Google quotes file an early Googler maintained (I am sure I am screwing it up):
“I’ve heard of defensive programming, but never adversarial memory.” — Ben Gomes
Comment · 5 years ago
Everyone says that but I have not experienced it. In practice, I think this impacts backend extension developers more than people targeting LLVM IR. My experience covers version 7-11, but perhaps it used to be worse?
Comment · 5 years ago
As someone who writes a lot of toy languages, I made this scaffolding for a LLVM-based compiler: https://github.com/finiteloop/compiler
It uses Bison and Flex for parsing and lexing unlike this post, but may be a useful starting point for those building their own toy languages.
Comment · 6 years ago
At FriendFeed, when we first introduced real-time comments and likes (pretty sure we were the first social network to do this), we did it with long-polling via an iFrame because web sockets did not exist. It actually worked pretty well!
https://www.ft.com/content/87b8107e-9c6d-3d3f-a60d-3e4f6315d...
Comment · 8 years ago
People file lawsuits when companies have filed for IPO because generally that leads to companies being in a "quiet period" in which they cannot effectively respond publicly, which increases the likelihood of settlement, etc. It is also extremely common for competitors to seed the press with negative story lines, taking advantage of the legally mandated quiet period to remove the filing company's ability to counter these stories.
Comment · 9 years ago
Developer documentation is here: https://quip.com/dev/
The APIs to build Live Apps enable real-time coediting and online / offline syncing with no special code; you get a ton for "free," and we are super proud of the technology.
We open sourced all the apps we wrote, like Calendar, Kanban board, and more. Available at https://github.com/quip/quip-apps
Comment · 11 years ago
Minifying alone is "kind of" important, and the benefits are hard to measure precisely with the combination of gzip, http/2, and the plethora of other network optimizations. However, the more sophisticated JavaScript compilers, like Google's Closure Compiler (https://developers.google.com/closure/compiler/) also do a lot of other compiler optimizations, like inlining functions, eliminating dead code, etc.
When you are working on a large engineering team with lots of JavaScript volume written by a lot of different people, the dead code elimination alone is worth it; it means you can use one function from a library with millions of lines and your compiled JavaScript will only contain that individual function rather than many megabytes of unused code.
Comment · 11 years ago
Our documents are broken into lots of smaller components we call sections. So, in a billeted lost, each list item is its own section.
Sections have a GUID and can be modified without touching any of the other parts of the document. This is useful in that it minimizes most common merge conflicts - they only happen of people edit the same sentence or spreadsheet cell while offline, but simultaneous edits of the same doc generally don't result in the need for any merge algorithm.
For offline edits of the same section, we use a fairly standard three way merge algorithm. Then, we show the edits we chose in the left hand side of the doc with the conversation along with a "Revert" button so you (the end user) can revert if our algorithm was wrong.
Co-Founder of Sierra and Chairman of OpenAI.
Previously, Co-CEO of Salesforce, co-founder and CEO of Quip, CTO of Facebook, co-founder and CEO of FriendFeed, co-creator of Google Maps.
[email protected]