Hacker News: finiteloop

Building in the Era of Autonomous Software Development

finiteloop — Tue, 24 Dec 2024 01:59:48 +0000

Article URL: https://backchannel.org/blog/autonomous-software

Comments URL: https://news.ycombinator.com/item?id=42499101

Points: 1

# Comments: 0

New comment by finiteloop in "Ask HN: Can Salesforce be a long term career?"

finiteloop — Thu, 29 Apr 2021 15:06:21 +0000

Excited to work with you!

New comment by finiteloop in "Ask HN: Can Salesforce be a long term career?"

finiteloop — Thu, 29 Apr 2021 14:54:04 +0000

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 bret.taylor@salesforce.com.

New comment by finiteloop in "ECC matters"

finiteloop — Mon, 04 Jan 2021 06:13:43 +0000

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

New comment by finiteloop in "A Complete Guide to LLVM for Programming Language Creators"

finiteloop — Sat, 26 Dec 2020 02:18:16 +0000

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?

New comment by finiteloop in "A Complete Guide to LLVM for Programming Language Creators"

finiteloop — Sat, 26 Dec 2020 01:28:37 +0000

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.

Show HN: PurpleAir air quality iOS 14 home screen widget and app

finiteloop — Mon, 12 Oct 2020 01:56:43 +0000

Article URL: https://github.com/finiteloop/air-quality

Comments URL: https://news.ycombinator.com/item?id=24750761

Points: 1

# Comments: 0

New comment by finiteloop in "Stupid solutions: Live server push without JS"

finiteloop — Tue, 29 Sep 2020 17:12:43 +0000

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...

Invisible Asymptotes – Growth at large scale technology companies

finiteloop — Sun, 27 May 2018 19:59:42 +0000

Article URL: http://www.eugenewei.com/blog/2018/5/21/invisible-asymptotes

Comments URL: https://news.ycombinator.com/item?id=17168834

Points: 7

# Comments: 0

New comment by finiteloop in "Spotify files for its IPO"

finiteloop — Wed, 03 Jan 2018 17:37:05 +0000

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.

New comment by finiteloop in "Quip launches Live Apps, a collaboration development platform"

finiteloop — Mon, 06 Nov 2017 21:58:04 +0000

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

Quip launches Live Apps, a collaboration development platform

finiteloop — Mon, 06 Nov 2017 21:55:41 +0000

Article URL: https://quip.com/blog/new-quip-collaboration-platform

Comments URL: https://news.ycombinator.com/item?id=15639352

Points: 2

# Comments: 1

New comment by finiteloop in "Security concerns with minified JavaScript code"

finiteloop — Mon, 31 Aug 2015 16:21:07 +0000

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.

New comment by finiteloop in "React with C++: Building the Quip Mac and Windows Apps"

finiteloop — Wed, 08 Jul 2015 16:34:23 +0000

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.