Arrgh

s/linkedin.co/linkedin.com/g :)

me: "this is great advice"

also me: "I have no interest in working on things that don't scale"

The specific mechanism of action here needs a drill-down. Did "The AI Scientist" (ugh) generate a patch to its code and prompt a user to apply it, as the screenshots would seem to indicate? If so I don't find this worrying at all: people write all kinds of stupid code all the time--often, impressively, without any help from "AI"! ;)

Did it apply the patch itself, then reset the session to whatever extent necessary to have the new code take effect? TBH I'm not really worried about this either, as long as the execution environment doesn't grant it the ability to bring unlimited additional hardware to bear. Even in that case, presumably some human would be paying attention to the AWS bills, or the moral equivalent.

Long, long ago, I used a library called Augeas (https://augeas.net/) in a drift-detection product*, so that if we detected a difference in config files, either on the same server through time, or on different servers that were supposed to be similar, we could de-noise the diffs, and more importantly, let users write fine-grained, but syntax-tolerant, allow-lists like "this particular setting is allowed to differ"... or even "this particular setting can have one of the following list of values". :)

* the company was acquired by Splunk years after we shelved that product

Counterpoint: the new project has to survive long enough to ship 1.0. :/

Building a trust relationship between commercial entities isn't automatable; it nearly always requires a contract to be carefully hand-written and argued over by high-priced lawyers before any meaningful exchange of value can take place.

Sure, this is an unfortunate level of friction, and overkill in many cases, but think about it from a cost/benefit perspective: I can spend $10k on legal fees and successfully avoid not just a lot of uncertainty, but very infrequently, the contract also protects me from losses that can be orders of magnitude larger than it cost me to negotiate the contract.

It's not an "alternative", it's still Android, just a fork of a fork.

Splunk has a bunch of openings onsite in downtown Vancouver BC: https://jobs.jobvite.com/splunk/search?r=&c=&l=Vancouver%2C+...

This one in particular is on my team. :) https://jobs.jobvite.com/splunk/job/ob3j6fwn

Hey folks,

I'm the Director of Architecture at Metafor Software (http://www.metaforsoftware.com/) in Vancouver, BC. We just raised some money, and we're looking to fill five open positions:

* Front-end Web Developer

* QA Test Engineer

* Graduate Student Internship Position (in Machine Learning)

* Development Team Lead

* Java/Scala Developer – Big Data

We strongly prefer onsite work, and have not previously paid relocation or sponsored any visas, but for the right candidates, we might reconsider.

> I like being a pedantic programmer.

Try Scala! (So do I ;)

Jonas Bonér has been a big fan of Mozart/Oz for a long time, so naturally he rolled some dataflow concurrency support into Akka: http://doc.akka.io/dataflow-scala

A minor nitpick-nitpick: it's not so much that a JVM requirement prevents Scala from using H-M type inference, it's that H-M doesn't work very well with subtyping, which Scala supports for its own O-O reasons. This comment from Martin provides some context: http://www.codecommit.com/blog/scala/is-scala-not-functional...

I wish there were a downloadable version of the video. The only way I ever watch work-related videos is on my phone, on the bus.

2002? Ha! Try 1994! http://www.reddit.com/r/pics/comments/6sok3/either_ive_final...