ttol

Had to give https://reasoner.com a try on ARC-AGI-2.

Reasoner passed on first try.

“Correct!”

(See screenshot that shows one rated “hard” -- https://www.linkedin.com/posts/waynechang_tried-reasoner-on-...)

Finally, the missing block to building geocities v2!

We actually integrate with PagerDuty and a bunch of other services already (users can submit integrations too) :-)

Existing integrations: http://try.crashlytics.com/integrations/

Submit integrations using: https://github.com/crashlytics/crashlytics-services

[CENSORED] [REDACTED] [CENSORED] :P

Agree. That's an area I personally want to address and am addressing. Oh the stories I have around that!

Yes - no brainer. :-)

Crashlytics is free :-)

Thanks ksar! Wait until you see what we've been working on ;-)

Wayne here. I hear your loud and clear. Working on it.. :-)

This is super interesting. Right now we are limited by communication due to latency from speed of light. With quantum entanglement, does that mean no latency over great distances? Or is there a latency involved, even in quantum entanglement?

Hey Joe, Wayne here with Crashlytics. Our mission is to provide the best-in-class mobile crash reporting tool. We actually do not charge :-) Let me know your thoughts once you've tried it. We power many top apps including Twitter, Vine, OpenTable, Yelp, Path, Square, and many others.

Also, thanks for the feedback on the invite flow -- I will look into that with the team today!

Hi pifflesnort,

Wayne here. We're extremely proud of the work that the team here at Crashlytics has put into our crash reporting solution. There are many flaws in PLCR that we've addressed -- our customers, like Twitter, Vine, Square, Yelp, OpenTable, Hipmunk, Delta, Kayak, and others, enjoy the increased visibility as well as the wider net to catch issues that other solutions cannot.

We look forward to improving our solution even further - stay tuned ;-)

Wayne from Crashlytics here. Don't worry, a shut down is not next :-)

Thanks Leonid! Have you used these in production?

Agree. OP should work on better account receivable practices instead of pretending to be a loan shark.

This won't work in practice. There are laws in place to prevent sky-high compounding interest rates, late fees, etc.

I would suggest that you simply take 50%, or some other large portion of the project, up front. Then, as you near a milestone, ask for another piece of it.

Billing at the end in one large chunk and then charging enormous rates just means you're not de-risking on the on set, and you're screwing a customer relationship.

Also, industry norms are NET 30, and some customers may even operate, and push, on NET 90 terms.

We redirected it to our main site while we resized our blog server. Resize completed and the blog server (and post) is now up! :-)

Whoops - yes, you're right. Our blog server is completely separate and apart from any of our other servers. It originally only had 1GB of ram, and we're in the middle of resizing it to 4GB. Thanks for the Google cached link! :)

Update: And the blog server is now back up and on a much faster machine.

I remember when this problem was solved. Saved a ton of time.

I think cutting all the legacy is a good move -- start over from scratch. They have the wherewithal to round developer support (and also leverage their Xbox relationships), so cutting baggage is a good idea.

This is nifty :-)

Congrats Ariel, Aaron, and Brian! Textbook industry needs disruption.