1,014 karma · joined January 10, 2009
You can read a bit more about it here: http://www.shopify.com/technology/7183290-introducing-the-su...
A graphical tool to create them, built of units instead of just strings, and the output could still be a regex string.
>We developers are notoriously bad at socializing and I believe it’s one of the things severely keeping our craft much farther behind than it ought to be. We’re wonderfully intelligent people, but we’re nearly incapable of having open discussions to improve our craft. The idea of actual, constructive criticism seems farfetched to most developers, and it’s so much easier to shit on somebody else’s work.
I agree with this fully. This is something that would need to be solved before building such a system.
A great example of a system which learns from history, but which also supports changes in behaviour is: http://worrydream.com/MagicInk/#engineering_inference_from_h...
The linked example is specific to one application, but he continues to detail what he thinks would make for a general solution.
The way I look at it is, yes the software should keep a history of user behaviour and base its actions off that, but there must be feedback involved, either explicit or implicit. This way, if I gave some input to the system once but then never did so again, the likelyhood that one event should affect the future would diminish over time.
There could be trickiness around "Bubbles" (like a Search bubble, where it only recommends to you things it thinks you'd like, and never shows you other things). I think those are problematic and should be dealt with. But I don't think that means it's impossible to fix. It's just something that needs to be thought through. I don't have an answer for it right now but that doesn't mean there isn't an answer.
That's part of the implementation, again, I think. It would be silly for the implementation to treat just once instance of a behaviour so seriously. If the user buys it once, but then never shows any interest in such products again, then they should slowly be ranked less and less relevant. If the user instead continued to purchase or look at baby items, then the system could have more certainty of desire in them. Again, it's not just the products themselves, but the behaviour surrounding them. Temporal context is important, too.
I agree fully that just heaping on more interface for "special cases" is a bad idea. We just need to be smarter about...how our software is smart.
Flaws like this might exist right now, but that's really a "bug". It's a failure on our part (the software designers and engineers) to build a system that actually works for the human. So sometimes when we try to make our software smart, it ends up being [maddeningly] stupid. But again, this is only because we don't do our jobs right, not that they can't be done right.
So with a little more smarts from us, we could make a system that's a lot more flexible and allow for these sorts of things. We have to acknowledge that a user shouldn't have to fit our system exactly and we should allow for "Buying a friend some baby clothes but not have it think we have a child" cases by being smarter about how the system learns. We need to provide it with better context.
If you like the ideas in the OP, you owe it to yourself to chew through Bret's paper. A lot of the same ideas, expanded and thought through.
I think the real meat of the argument is "iPhone synthesized all those individual pieces into something coherent and incredible.". It's kind of like how the Macintosh and Lisa took the ideas from PARC, perfected them, and turned them into a real product. I think the stink is being made that Android is copying that aspect of the iPhone, instead of just a piece or two.
Maybe that's not what's actually being argued, but that's what I think should be argued at least.
If you're a Mac developer, check the forums. Else, wait for the info to be non-NDA.
Yes but things change. Old fart or not, you're into technology, we all have to realize things change!
>(plus libraries)
So some of this would belong as a language feature and other stuff would be in the standard library (is what I'm imagining at least).
I'm a Cocoa guy, and when a lot of people rave about Objective-C, they usually are referring to niceties Cocoa provides. This is sort of what I was imagining as I read along.
Yes, you get a good product, but you also get ads. Your information isn't really entirely private. Some people are totally fine with that, and that's OK. But if you don't want a service to do that, usually that means you pay them money. Nothing is free.
> Why would the amount of cash you throw at something impact how you invest your time in it? I love Evernote, but me throwing a few bucks a year at it isn't going to change how I already use it.
I mean that in the sense in order to really use a product like this, I've got to spend time putting recipes into it. The very basic (and not perfect) theory is: if this site is making money from me directly, it's less likely to shut down or want to sell out. I take comfort in that but I know there are counter-examples.
iOS is like a restaurant: most of the choices are made for you, but the meal is effortless.