Podcasts about Netflix Prize

Arnaud Castillo got $1.5 million in prepayments from customers who think he found a way to make accurate predictions about financial markets…the weather…venture capital…and anything. Arnaud created CrunchDAO, which holds online tournaments in which data analysts compete to see who can create the best predictive models. Skeptical? He might remind you of the Netflix Prize, the $1 million tournament in which a team of outsiders improved Netflix’s recommendation algorithm by 10.05%, or his entrepreneurial track of proving skeptics wrong. Arnaud Castillo is the founder of CrunchDAO, which is building the future of asset management. Sponsored byOrigami – If you’ve heard about DAOs (Decentralized Autonomous Organizations) and you want to find out how to set one up for yourself, go to JoinOrigami.com. Even if you’re just interested in how these things work and want to learn more, the Origami blog is a great place to start. Lemon.io – Why squander time and money on developers who aren't perfect for your startup? Let Lemon match you with engineers that can transform your vision into reality — diabolically fast. Go to Lemon.io/mixergy for a 15% discount on your first 4 weeks with one of their devs. More interviews -> https://mixergy.com/moreint Rate this interview -> https://mixergy.com/rateint

In this episode we talked to Tom Davenport and Laks Srinivasan from Return on AI Institute (ROAI) about how AI is empowering and challenging organizational models worldwide, and how the platform business model is often based on AI capabilities in the background.  Tom is a world-renowned thought leader and author on AI. He is the President's Distinguished Professor of Information Technology and Management at Babson College, as well as a fellow at the MIT Initiative on the Digital Economy, a visiting professor at Oxford's Saïd Business School, and is the Chairman of ROAI. Laks is a data and analytics executive with more than 15 years of experience in management, entrepreneurship, and innovation roles to help clients create measurable value from AI. He is a co-founder and Managing Director at ROAI and former CEO of Opera Solutions (ElectrifAI now), an applied AI solutions company with 500+ employees globally as well as the winner of the Netflix Prize and several Kaggle AI competitions. Tom and Laks explore with us how different forms of artificial intelligence might transform product teams at companies around the globe. In the second part of this episode, Tom and Laks offer concrete examples of companies that have created new business models powered by AI, as well as suggestions on what traditional organizations should look at when preparing to adopt artificial intelligence. At Boundaryless we're partnering with ROAI to explore the convergence between AI and Platforms, check out our research and services here: https://blss.io/ROAI Key highlights

Listen to AEP: https://www.listennotes.com/podcasts/the-analytics/coalesce-you-dont-need-9OHhYXco26r/

About AidanAidan is an AWS enthusiast, due in no small part to sharing initials with the cloud. He's been writing software for over 20 years and getting paid to do it for the last 10. He's still not sure what he wants to be when he grows up.Links: Stedi: https://www.stedi.com/ GitHub: https://github.com/aidansteele Blog posts: https://awsteele.com/ Ipv6-ghost-ship: https://github.com/aidansteele/ipv6-ghost-ship Twitter: https://twitter.com/__steele TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.Corey: Today's episode is brought to you in part by our friends at MinIO the high-performance Kubernetes native object store that's built for the multi-cloud, creating a consistent data storage layer for your public cloud instances, your private cloud instances, and even your edge instances, depending upon what the heck you're defining those as, which depends probably on where you work. It's getting that unified is one of the greatest challenges facing developers and architects today. It requires S3 compatibility, enterprise-grade security and resiliency, the speed to run any workload, and the footprint to run anywhere, and that's exactly what MinIO offers. With superb read speeds in excess of 360 gigs and 100 megabyte binary that doesn't eat all the data you've gotten on the system, it's exactly what you've been looking for. Check it out today at min.io/download, and see for yourself. That's min.io/download, and be sure to tell them that I sent you.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. I'm joined this week by someone who is honestly, feels like they're after my own heart. Aidan Steele by day is a serverless engineer at Stedi, but by night, he is an absolute treasure and a delight because not only does he write awesome third-party tooling and blog posts and whatnot around the AWS ecosystem, but he turns them into the most glorious, intricate, and technical shit posts that I think I've ever seen. Aidan, thank you for joining me.Aidan: Hi, Corey, thanks for having me. It's an honor to be here. Hopefully, we get to talk some AWS, and maybe also talk some nonsense as well.Corey: I would argue that in many ways, those things are one in the same. And one of the things I always appreciated about how you approach things is, you definitely seem to share that particular ethos with me. And there's been a lot of interesting content coming out from you in recent days. The thing that really wound up showing up on my radar in a big way was back at the start of January—2022, for those listening to this in the glorious future—about using IPv6 to use multi-factor auth, which it is so… I don't even have the adjectives to throw at this because, first it is ridiculous, two, it is effective, and three, it is just who thinks like that? What is this and what did you—what monstrosity have you built?Aidan: So, what did I end up calling it? I think it was ipv6-ghost-ship. And I think I called it that because I'd recently watched, oh, what was that series that was recently on Apple TV? Uh, the Isaac Asimov—Corey: If it's not Paw Patrol, I have no idea what it is because I have a four-year-old who is very insistent about these things. It is not so much a TV show as it is a way of life. My life is terrible. Please put me out of my misery.Aidan: Well, at least it's not Bluey. That's the one I usually hear about. That's Australia's greatest export. But it was one of the plot devices was a ship that would teleport around the place, and you could never predict where it was next. And so no one could access it. And I thought, “Oh, what about if I use the IPv6 address space?”Corey: Oh, Foundation?Aidan: That's the one. Foundation. That's how the name came about. The idea, honestly, it was because I saw—when was it?—sometime last year, AWS added support for those IP address prefixes. IPv4 prefixes were small; very useful and important, but IPv6 with more than 2 trillion IP addresses, per instance, I thought there's got to be fun to be had there.Corey: 281 trillion, I believe is the—Aidan: 281 trillion.Corey: Yeah. It is sarcastically large space. And that also has effectively, I would say in InfoSec sense, killed port scanning, the idea I'm going to scan the IP range and see what's there, just because that takes such a tremendous amount of time. Now here, in reality, you also wind up with people using compromised resources, and yeah, it turns out, I can absolutely scan trillions upon trillions of IP addresses as long as I'm using your AWS account and associated credit card in which to do it. But here in the real world, it is not an easily discoverable problem space.Aidan: Yeah. I made it as a novelty, really. I was looking for a reason to learn more about IPv6 and subnetting because it's the term I'd heard, a thing I didn't really understand, and the way I learn things is by trying to build them, realizing I have no idea what I'm doing, googling the error messages, reluctantly looking at the documentation, and then repeating until I've built something. And yeah, and then I built it, published it, and seemed to be pretty popular. It struck a chord. People retweeted it. It tickled your fancy. I think it spoke something in all of us who are trying not to take our jobs too seriously, you know, know we can have a little fun with this ludicrous tech that we get to play with.Corey: The idea being, you take the multi-factor auth code that your thing generates, and that is the last series of octets for the IP address you wind up going towards and that is such a large problem space that you're not going to find it in time, so whatever it is automatically connect to that particular IP address because that's the only one that's going to be listening for a 30 to 60-second span for the connection to be established. It is a great idea because SSH doesn't support this stuff natively. There's no good two-factor auth approach for this. And I love it. I'd be scared to death to run this in production for something that actually matters.And we also start caring a lot more about how accurate are the clocks on those instances, all of a sudden. But, oh, I just love the concept so much because it hits on the ethos of—I think—what so much of the cloud does were these really are fundamental building blocks that we can use to build incredible, awe-inspiring things that are globe-spanning, and also ridiculousness. And there's so much value of being able to do the same thing, sometimes at the same time.Aidan: Yeah, it's interesting, you mentioned, like, never using in prod, and I guess when I was building it, I thought, you know, that would be apparent. Like, “Yes, this is very neat, but surely no one's going to use it.” And I did see someone raised an issue on the GitHub project which was talking about clock skew. And I mentioned—Corey: Here at the bank where I'm running this in production, we're—Aidan: [laugh].Corey: —having some trouble with the clock. Yeah, it's—Aidan: You know, I mentioned that the underlying 2FA library did account for clock scheme 30 seconds either way, but it made me realize, I might need to put a disclaimer on the project. While the code is probably reasonably sound, I personally wouldn't run it in production, and it was more meant to be a piece of performance art or something to tickle one's fancy and to move on, not to roll it out. But I don't know, different strokes for different folks.Corey: I have gotten a lot better about calling out my ridiculous shitpost things when I do them. And the thing that really drove that home for me was talking about using DNS TXT records to store information about what server a virtual machine lives on—or container or whatnot—thus using Route 53 is a database. And that was a great gag, and then someone did a Reddit post of “This seems like a really good idea, so I'm going to start doing it, and I'm having these questions.”And at that point is like, “Okay, I've got a break character at that point.” And is, yeah, “Hi. That's my joke. Don't do it because X, Y, and Z are your failure modes, there are better tools for it. So yeah, there are ways you can do this with DNS, but it's not generally a great idea, and there are some risk factors to it. And okay, A, B, and C are the things you don't want to do, so let's instead do it in a halfway intelligent way because it's only funny if everyone's laughing. Otherwise, we fall into this trap of people take you seriously and they feel bad as a result when it doesn't work in production. So, calling it out as this is a joke tends to put a lot of that aside. It also keeps people from feeling left out.Aidan: Yeah. I realized that because the next novelty project I did a few days later—not sure if you caught it—it was a Rick Roll over ICMPv6 packets, where if you had run ping six to a certain IP range, it would return the lyrics to music's greatest treasure. So, I think that was hopefully a bit more self-evident that this should never be taken seriously. Who knows, I'm sure someone will find a use for it in prod.Corey: And I was looking through this, this is great. I love some of the stuff that you're doing because it's just fantastic. And I started digging a bit more to things you had done. And at that point, it was whoa, whoa, whoa, wait a minute. Back in 2020, you found an example of an issue with AWS's security model where CloudTrail would just start—if asked nicely—spewing other people's credential sets and CloudTrail events and whatnot into your account.And, A, that's kind of a problem. B, it was something that didn't make that big of a splash when it came out—I don't even think I linked to it at the time—and, C, it was examples of after the recent revelations around CloudFormation and Glue that the fine folks at Orca Security found out. That wasn't a one-off because you'd done this a year beforehand. We have now an established track record of cross-account data sharing and, potentially, exploits, and I'm looking at this and I got to level with you I felt incredibly naive because I had assumed that since we hadn't heard of this stuff in any real big sense that it simply didn't happen.So, when we heard about Azure; obviously, it's because Azure is complete clown shoes and the excellent people that AWS would never make these sorts of mistakes. Except we now have evidence that they absolutely did and didn't talk about it publicly. And I've got a level with you. I feel more than a little bit foolish, betrayed, naive for all this. What's your take on it?Aidan: Yeah, so just to clarify, it wasn't actually in your account. It was the new AWS custom resource execution model was you would upload a Lambda function that would run in an Amazon-managed account. And so that immediately set off my spidey sense because executing code in someone else's account seems fraught with peril. And so—Corey: Yeah, you can do all kinds of horrifying things there, like, use it to run containers.Aidan: Yeah. [laugh]. Thankfully, I didn't do anything that egregious. I stayed inside the Lambda function, but I look—I poked around at what credentials have had, and it would use CloudWatch to reinvoke itself and CloudWatch kept recording CloudTrail. And I won't go into all the details, but it ended up being that you could see credentials being recorded in CloudTrail in that account, and I could, sort of, funnel them out of there.When I found this, I was a little scared, and I don't think I'd reported an issue to AWS before, so I didn't want to go too far and do anything that could be considered malicious. So, I didn't actively seek out other people's credentials.Corey: Yeah, as a general rule, it's best once you discover things like that to do the right thing and report it, not proceed to, you know, inadvertently commit felonies.Aidan: Yeah. Especially because it was my first time. I felt better safe than sorry. So, I didn't see other credentials, but I had no reason to believe that, I wouldn't see it if I kept looking. I reported it to Amazon. Their security team was incredibly professional, made me feel very comfortable reporting it, and let me know when, you know, they'd remediated it, which was a matter of days later.But afterwards, it left me feeling a little surprised because I was able to publish about it, and a few people responded, you know, the sorts of people who pay close attention to the industry, but Amazon didn't publish anything as far as I was aware. And it changed the way I felt about AWS security, because like you, I sort of felt that AWS, more or less had a pretty perfect track record. They would have advisories about possible [Zen 00:12:04] exploits, and so on. But they'd never published anything about potential for compromise. And it makes me wonder how many of the things might have been reported in the past where either the third-party researcher either didn't end up publishing, or they published and it just disappeared into the blogosphere, and I hadn't seen it.Corey: They have a big earn trust principle over there, and I think that they always focus on the trust portion of it, but I think what got overlooked is the earn. When people are giving you trust that you haven't earned, on some level, the right thing to do is to call it out and be transparent around these things. Yes, I know, Wall Street's going to be annoyed and headlines, et cetera, et cetera, but I had always had the impression that had there been a cross-account vulnerability or a breach of some sort, they would communicate this and they would have their executives go on a speaking tour about it to explain how defense-in-depth mitigated some of it, and/or lessons learned, and/or what else we can learn. But it turns out that wasn't was happening at all. And I feel like they have been given trust that was unearned and now I am not happy with it.I suddenly have a lot more of a, I guess, skeptical position toward them as a result, and I have very little tolerance left for what has previously been a staple of the AWS security discussions, which is an executive getting on stage for a while and droning on about the shared responsibility model with the very strong implication that “Oh, yeah, we're fine. It's all on your side of the fence that things are going to break.” Yeah, turns out, that's not so true. Just you know, about the things on your side of the fence in a way that you don't about the things that are on theirs.Aidan: Yeah, it's an interesting one. Like, I think about it and I think, “Well, they never made an explicit promise that they would publish these things,” so, on one hand, I say to myself, “Oh, maybe that's on me for making that assumption.” But, I don't know, I feel like the way we felt was justified. Maybe naive in hindsight, but then, you know, I guess… I'm still not sure how to feel because of, like, I think about recent issues and how a couple of AWS Distinguished Engineers jumped on Twitter, and to their credit were extremely proactive in engaging with the community.But is that enough? It might be enough for say, to set my mind at ease or your mind at ease because we are, [laugh] to put it mildly, highly engaged, perhaps a little too engaged in the AWS space, but Twitter's very ephemeral. Very few of AWS's customers—Corey: Yeah, I can't link to tweets by distinguished engineers to present to an executive leadership team as an official statement from Amazon. I just can't.Aidan: Yeah. Yeah.Corey: And so the lesson we can take from this is okay, so “Well, we never actually said this.” “So, let me get this straight. You're content to basically let people assume whatever they want until they ask you an explicit question around these things. Really? Is that the lesson you want me to take from this? Because I have a whole bunch of very explicit questions that I will be asking you going forward, if that is in fact, your position. And you are not going to like the fact that I'm asking these questions.”Even if the answer is a hard no, people who did not have this context are going to wonder why are people asking those questions? It's a massive footgun here for them if that is the position that they intend to have. I want to be clear as well; this is also a messaging problem. It is not in any way, a condemnation of their excellent folks working on the security implementation themselves. This stuff is hard and those people are all-stars. I want to be very clear on this. It is purely around the messaging and positioning of the security posture.Aidan: Yeah, yeah. That's a good clarification because like you, my understanding that the service teams are doing a really stellar, above-average job, industry-wide, and the AWS Security Response Teams, I have absolute faith in them. It is a matter of messaging. And I guess what particularly brings it to front-of-mind is, it was earlier this month, or maybe it was last month, I received an email from a company called Sourcegraph. They do code search.I'm not even a customer of theirs yet, you know? I'm on a free trial, and I got an email that—I'm paraphrasing here—was something to the effect of, we discovered that it was possible for your code to appear in other customers' code search results. It was discovered by one of our own engineers. We found that the circumstances hadn't cropped up, but we wanted to tell you that it was possible. It didn't happen, and we're working on making sure it won't happen again.And I think about how radically different that is where they didn't have a third-party researcher forcing their hand; they could have very easily swept under the rug, but they were so proactive that, honestly, that's probably what's going to tipped me over to the edge into me becoming a customer. I mean, other than them having a great product. But yeah, it's a big contrast. It's how I like to see other companies work, especially Amazon.Corey: This episode is sponsored in part by our friends at Sysdig. Sysdig is the solution for securing DevOps. They have a blog post that went up recently about how an insecure AWS Lambda function could be used as a pivot point to get access into your environment. They've also gone deep in-depth with a bunch of other approaches to how DevOps and security are inextricably linked. To learn more, visit sysdig.com and tell them I sent you. That's S-Y-S-D-I-G dot com. My thanks to them for their continued support of this ridiculous nonsense.Corey: The two companies that I can think of that have had security problems have been CircleCI and Travis CI. Circle had an incredibly transparent early-on blog post, they engaged with customers on the forums, and they did super well. Travis basically denied, stonewalled for ages, and now the only people who use Travis are there because they haven't found a good way to get off of it yet. It is effectively DOA. And I don't think those two things are unrelated.Aidan: Yeah. No, that's a great point. Because you know, I've been in this industry long enough. You have to know that humans write code and humans make mistakes—I know I've made more than my fair share—and I'm not going to write off the company for making a mistake. It's entirely in their response. And yeah, you're right. That's why Circle is still a trustworthy business that should earn people's business and why Travis—why I recommend everyone move away from.Corey: Yeah, I like Orca Security as a company and as a product, but at the moment, I am not their customer. I am AWS's customer. So, why the hell am I hearing it from Orca and not AWS when this happens?Aidan: Yeah, yeah. It's… not great. On one hand, I'm glad I'm not in charge of finding a solution to this because I don't have the skills or the expertise to manage that communication. Because like I think you said in the past, there's a lot of different audiences that they have to communicate with. They have to communicate with the stock market, they have to communicate with execs, they have to communicate with developers, and each of those audiences demands a different level of detail, a different focus. And it's tricky. And how do you manage that? But, I don't know, I feel like you have an obligation to when people place that level of trust in you.Corey: It's just a matter of doing right by your customers, on some level.Aidan: Yeah.Corey: How long have you been working on an AWS-side environments? Clearly, this is not like, “Well, it's year two,” because if so I'm going to feel remarkably behind.Aidan: [laugh]. So, I've been writing code in some capacity or another for 20 years. It took about five years to get anyone to pay me to do so. But yeah, I guess the start of my professional career—and by ‘professional,' I want to use it in strictest term, means getting paid for money; not that I [laugh] am necessarily a professional—coincided with the launch of AWS. So, I don't hadn't experienced with the before times of data centers, never had to think about direct connect, but it means I have been using AWS since sometime in 2008.I was just looking at my bill earlier, I saw that my first bill was for $70. It was—I was using a C1xLarge, which was 80 cents an hour, and it had eight-core CPUs. And to put that in context at the time—Corey: Eight vCPUs, technically I believe.Aidan: An it basically is—Corey: —or were they using [eCPU 00:20:31] model back then?Aidan: Yeah, no, that was vCPUs. But to me, that was extraordinary. You know, I was somewhere just after high school. It was—the Netflix Prize was around. If you're not sure what that was, it was Netflix had this open competition where they said anyone who could improve upon their movie recommendation algorithm could win a million dollars.And obviously being a teenager, I had a massive ego and [laugh] no self-doubt, so I thought I could win this, but I just don't have enough CPUs or RAM on my laptop. And so when EC2 launched, and I could pay 80 cents an hour, rather than signing up for a 12-month contract with a colocation company, it was just a dream come true. I was able to run my terrible algorithms, but I could run them eight times faster. Unfortunately and obviously, I didn't win because it turns out, I'm not a world-class statistician. But—Corey: Common mistake. I make that mistake myself all the time.Aidan: [laugh]. Yeah. I mean, you know, I think I was probably 19 at the time, so I had—my ego did make me think I was one, but it turned out not to be so. But I think that was what really blew my mind was that me, a nobody, could create an account with Amazon and get access to these incredibly powerful machines for less than the dollar. And so I was hooked.Since then, I've worked at companies that are AWS customers since then. I've worked at places that have zero EC2 service, worked at places that have had thousands, and places in between. And it's got to a point, actually, where, I guess, my career is so entwined with AWS that one, my initials are actually AWS, but also—and this might sound ridiculous, and it's probably just a sign of my privilege—that I wouldn't consider working somewhere that used another cloud. Not—Corey: No, I think that's absolutely the right approach.Aidan: Yeah.Corey: I had a Twitter thread on this somewhat recently, and I'm going to turn it into a blog post because I got some pushback. If I were looking at doing something and I would come into the industry right now, my first choice would be Google Cloud because its developer experience is excellent. But I'm not coming to this without any experience. I have spent a decade or so learning not just how it was works, but also how it breaks, understanding the failure mode and what that's going to look like and what it's good at and what it's not. That's the valuable stuff for running things in a serious way.Aidan: Yeah. It's an interesting one. And I mean, for better or worse, AWS is big. I'm sure you will know much better than I do the exact numbers, but if a junior developer came to me and said, “Which cloud should I learn, or should I learn all of them?” I mean, you're right, Google Cloud does have a better developer experience, especially for new developers, but when I think about the sheer number of jobs that are available for developers, I feel like I would be doing them a disservice by not suggesting AWS, at least in Australia. It seems they've got such a huge footprint that you'll always be able to find a job working as an AWS-familiar engineer. It seems like that would be less the case with Google Cloud or Azure.Corey: Again, I am not sitting here, suggesting that anyone should, “Oh, clouds are insecure. We're going to run our own stuff in our own data centers.” That is ridiculous in this era. They are still going to do a better job of security than any of us will individually, let's be clear here. And it empowers and unlocks an awful lot of stuff.But with their privileged position as these hyperscale providers that are the default choice for building things, I think comes with a significant level of responsibility that I am displeased to discover that they've been abdicating. And I don't love that.Aidan: Yeah, it's an interesting one, right, because, like you're saying, they have access and the expertise that people doing it themselves will never match. So, you know, I'm never going to hesitate to recommend people use AWS on account security because your company's security posture will almost always be better for using AWS and following their guidelines, and so on. But yeah, like you say, with great power comes significant responsibility to earn trust and retain that trust by admitting and publicizing when mistakes are made.Corey: One last topic I want to get into with you is one that you and I have talked about very briefly elsewhere, that I feel like you and I are both relatively up-to-date on AWS intricacies. I think that we are both better than the average bear working with the platform. But I know that I feel this way, and I suspect you do too that VPCs have gotten confusing as hell. Is that just me? Am I a secret moron that no one bothered to ever tell me this, and I should update my own self-awareness?Aidan: [laugh]. Yeah, it's… I mean, that's been the story of my career with AWS. When I started, VPCs didn't exist. It was EC2 Classic—well, I guess at the time, it was just EC2—and it was simple. You launched an instance and you had an IP address.And then along came VPCs, and I think at the time, I thought something to the effect of “This seems like needless complexity. I'm not going to bother learning this. It will never be relevant.” In the end that wasn't true. I worked in much large deployments when VPCs made fantastic sense made a lot of things possible, but I still didn't go into the weeds.Since then, AWS has announced that EC2 Classic will be retired; an end of an era. I'm not personally still running anything in EC2 Classic, and I think they've done an incredible job of maintain support for this long, but VPC complexity has certainly been growing year-on-year since then. I recently was using the AWS console—like we all do and no one ever admits to—to edit a VPC subnet route table. And I clicked the drop-down box for a target, and I was overwhelmed by the number of options. There were NAT gateways, internet gateways, carrier gateways, I think there was a thing called a wavelength gateway, ENI, and… I [laugh] I think I was surprised because I just scroll through the list, and I thought, “Wow, that is a lot of different options. Why is that?”Especially because it's not so relevant to me. But I realized a big thing of what AWS has been doing lately is trying to make themselves available to people who haven't used the cloud yet. And they have these complicated networking needs, and it seems like they're trying to—reasonably successfully—make anything possible. But with that comes, you know, additional complexity.Corey: I appreciate that the capacity is there, but there has to be an abstraction model for getting rid of some of this complexity because otherwise, the failure mode is you wind up with this amazingly capable thing that can build marvels, but you also need to basically have a PhD in some of these things to wind up tying it all together. And if you bring someone else in to do it, then you have no idea how to run the thing. You're effectively a golden retriever trying to fly a space shuttle.Aidan: Yeah. It's interesting, like, clearly, they must be acutely aware of this because they have default VPCs, and for many use cases, that's all people should need. But as soon as you want, say a private subnet, then you need to either modify that default VPC or create a new one, and it's sort of going from 0 to 100 complexity extremely quickly because, you know, you need to create route tables to everyone's favorite net gateways, and it feels like the on-ramp needs to be not so steep. Not sure what the solution is, I hope they find one.Corey: As do I. I really want to thank you for taking the time to speak with me about so many of these things. If people want to learn more about what you're up to, where's the best place to find you?Aidan: Twitter's the best place. On Twitter, my username is @__Steele, which is S-T-E-E-L-E. From there, that's where I'll either—I'll at least speculate on the latest releases or link to some of the silly things I put on GitHub. Sometimes they're not so silly things. But yeah, that's where I can be found. And I'd love to chat to anyone about AWS. It's something I can geek out about all day, every day.Corey: And we will certainly include links to that in the [show notes 00:29:50]. Thank you so much for taking the time to speak with me today. I really appreciate it.Aidan: Well, thank you so much for having me. It's been an absolute delight.Corey: Aidan Steele, serverless engineer at Stedi, and shit poster extraordinaire. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an immediate request to correct the record about what I'm not fully understanding about AWS's piss-weak security communications.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

In this first interview we talk to Kim Falk, Senior Data Scientist, multiple RecSys Industry Chair and author of the book "Practical Recommender Systems". We introduce into recommenders from a practical perspective discussing the fundamental difference between content-based and collaborative filtering as well as the cold-start problem - no mathematical deep-dive yet, but expect it to follow. In addition, we reason what constitutes good recommendations and briefly touch on a couple of ways of finding that out.Looking a bit into the history of the recommender systems community, we touch on the Netflix Prize that was running from 2006 to 2009 as well as on the RecSys - the leading conference in recommender systems, where we also met for the first time.In the end, we discuss a couple of challenges the field faces, in particular associated with approaches based on deep learning. Besides that, Spiderman will accompany our conversation at certain times. Plus many practical recommendations included on how to get started. Stay tuned!Links from this Episode: Kim Falk on LinkedIn and Twitter Book: Practical Recommender Systems (Manning) (get 37% discount with the code podrecsperts37 during checkout) GitHub Repository for PRS Book ACM Conference on Recommender Systems 2021 (Amsterdam) Recommender Systems Specialization at Coursera Amazon.com Recommendations: Item-to-Item Collaborative Filtering Netflix Prize Netflix Prize dataset on Kaggle New York Times: A $1 Million Research Bargain for Netflix, and Maybe a Model for Others Evaluation Measures for Information Retrieval Paper by Dacrema et al. (2019): Are We Really Making Much Progress? A Worrying Analysis of Recent Neural Recommendation Approaches (best paper award at RecSys 2019) Recommending music on Spotify with Deep Learning MovieLens Recommenders General Links: Follow me on Twitter: https://twitter.com/LivesInAnalogia Send me your comments, questions and suggestions to marcel@recsperts.com Podcast Website: https://www.recsperts.com/ Twitter and LinkedIn posts for sharing: LinkedIn Twitter

Internet Archive, no acabamos de hablar del nuevo "pattern matching", complejidad creciente de la sintaxis de Python https://podcast.jcea.es/python/20 Participantes: Eduardo Castro, email: info@ecdesign.es. Conectando desde A Guarda. Jesús Cea, email: jcea@jcea.es, twitter: @jcea, https://blog.jcea.es/, https://www.jcea.es/. Conectando desde Madrid. Víctor Ramírez, twitter: @virako, programador python y amante de vim, conectando desde Huelva. Javier, conectando desde Madrid. Audio editado por Pablo Gómez, twitter: @julebek. La música de la entrada y la salida es "Lightning Bugs", de Jason Shaw. Publicada en https://audionautix.com/ con licencia - Creative Commons Attribution 4.0 International License. [01:33] Cómo documentar en Python. Google docs: https://docs.google.com. Wikis en GitHub: https://docs.github.com/en/communities/documenting-your-project-with-wikis/about-wikis. Ventajas de tener la documentación en el control de versiones del proyecto. Ventajas de ir escribiendo la documentación mientras escribes el propio código: Realimentación. Sphinx: https://www.sphinx-doc.org/en/master/. sphinx.ext.autodoc: https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html. plantuml: https://github.com/sphinx-contrib/plantuml. Markdown: https://www.markdownguide.org/. [03:48] La vieja guardia es escéptica con las novedades de la semana. No hay balas de plata. La documentación guía el desarrollo. Paralelismo con los tests. [08:38] Open source y la vergüenza: tests y documentación. [09:28] CPython Internals Book https://realpython.com/products/cpython-internals-book/. [11:13] HPy https://hpyproject.org/. Nuevo API https://es.wikipedia.org/wiki/Api para programar extensiones C para Python, independizándote de la versión del intérprete y compatible con cosas como PyPy: https://www.pypy.org/. [13:18] Internet Archive como biblioteca de libros modernos: https://archive.org/details/inlibrary. Funciona como una biblioteca tradicional. Préstamo de libros. Están escaneando a toda velocidad: 2.5 millones de libros en el momento de escribir estas notas (mayo de 2021). Internet Archive: https://archive.org/. Wayback Machine: https://web.archive.org/. Preservación de videojuegos, páginas en flash, discos de música... [17:03] Web de Python en Internet Archive. 1997: https://web.archive.org/web/19970606181701/http://www.python.org/. 1998: https://web.archive.org/web/19981212032130/http://www.python.org/. Un ejemplo de "batteries included": https://commons.wikimedia.org/wiki/File:Python_batteries_included.jpg. [17:53] Jesús Cea echa de menos la internet distribuida. [18:23] Pattern Matching en Python 3.10. PEP 622 -- Structural Pattern Matching https://www.python.org/dev/peps/pep-0622/. ¿"match" y "case" serán palabras reservadas? PEP 617 -- New PEG parser for CPython https://www.python.org/dev/peps/pep-0617/. Se repasa la funcionalidad un poco por encima. [27:48] Logs fáciles de configurar y decorados con colorines: Daiquiri: https://daiquiri.readthedocs.io/en/latest/. Colorama: https://pypi.org/project/colorama/. Compatible con Windows. [29:28] Truco: Python -i: Ejecuta un script y pasa a modo interactivo. Comentado hace unas semanas. También se puede hacer desde el propio código con code.InteractiveConsole(locals=globals()).interact(). Jesús Cea se queja de que usando la invocación desde código no funciona la edición de líneas. Javier da la pista correcta: para que funcione, basta con hacer import readline antes de lanzar el modo interactivo. [30:48] Manhole: https://pypi.org/project/manhole/. [31:53] Breakpoints condicionales https://docs.python.org/3/library/pdb.html#pdbcommand-condition. breakpoint() como función nativa: PEP 553 -- Built-in breakpoint() https://www.python.org/dev/peps/pep-0553/. import pdb; pdb.set_trace(). [33:28] Scraping a mano: scrapy shell: https://docs.scrapy.org/en/latest/topics/shell.html. Jesús Cea no echa de menos Scrapy https://docs.scrapy.org/en/latest/. [36:03] Indexador y buscador de documentos: Whoosh https://whoosh.readthedocs.io/en/latest/intro.html. Jesús necesitaba ignorar tildes, lo que impacta en la extracción del lexema. El backend está documentado, para que te lo puedas currar tú si lo necesitas. [38:23] ¿Cómo hacer copia de seguridad de un fichero de 600 gigabytes con pocos cambios internos? [40:58] Eduardo Castro ha ganado un hackathon en Pontevedra. Software para Django: https://www.djangoproject.com/. [46:38] Experiencias agridulces con los hackathones https://en.wikipedia.org/wiki/Hackathon. Netflix Prize https://en.wikipedia.org/wiki/Netflix_Prize. [50:38] Una URL puede no estar no disponible ya cuando escuchas el podcast: Podcast: Programar es una mierda: https://www.programaresunamierda.com/. [52:28] Jamii https://jamii.es/. API https://es.wikipedia.org/wiki/Api [55:38] GraphQL https://es.wikipedia.org/wiki/GraphQL. REST: https://es.wikipedia.org/wiki/Transferencia_de_Estado_Representacional. Permisos de usuario. No hay cacheo. Vulcain: https://github.com/dunglas/vulcain. [01:02:53] HTTP/2 https://en.wikipedia.org/wiki/HTTP/2. HTTP/2 Server Push: https://en.wikipedia.org/wiki/HTTP/2_Server_Push. No se tiene que responder por orden. Multiplexación. [01:08:53] La explosión de la complejidad innecesaria ocultada por bibliotecas: OAuth2 https://en.wikipedia.org/wiki/OAuth#OAuth_2.0. OpenID: https://en.wikipedia.org/wiki/OpenID. [01:10:33] Complejidad creciente de la sintaxis de Python. Volvemos a Structural Pattern Matching https://www.python.org/dev/peps/pep-0622/. Complejidad de la sintaxis. Un lenguaje pequeño y capaz reemplaza a lenguajes dinosaurio. Python reemplazó a otros lenguajes dinosaurio. Ahora Python es un dinosaurio. ¿Cuándo saldrá un lenguaje que reemplace a Python? [01:12:13] Metaclases https://realpython.com/python-metaclasses/. Closures: https://es.wikipedia.org/wiki/Clausura_(inform%C3%A1tica). [01:15:08] Empiezan a aparecer sublenguajes, tribus, subculturas de Python. Ciertos cambios de sintaxis pueden unificar subculturas: "la forma oficial de hacerlo". El operador ternario de Python v = VALOR1 if CONDICIÓN else VALOR2: PEP 308 -- Conditional Expressions https://www.python.org/dev/peps/pep-0308/. List comprehension: [f(i) for i in ITER if CONDICIÓN(i)]: PEP 202 -- List Comprehensions https://www.python.org/dev/peps/pep-0202/. [01:20:18] En los viejos tiempos, podías hacer barbaridades como True = 0. Esto funciona en Pythonn 2.7. Es algo que se cambió en Python 3.0: https://docs.python.org/3.0/whatsnew/3.0.html#changed-syntax. [01:21:53] Jesús Cea echa de menos que se eliminen cosas. Está obsesionado con el tamaño del lenguaje. ¿Qué eliminaríamos? [01:25:23] El lenguaje C incluye solo lo mínimo imprescindible. [01:26:48] Curiosidades: What the f*ck Python! https://github.com/satwikkansal/wtfpython: >>> all([]) True >>> all([[]]) False >>> all([[[]]]) True [01:28:03] Algunos avances en la investigación del bug descrito por Virako en las últimas semanas: Ejemplo de código: https://pastebin.com/vGM1sh8r. Issue24676: Error in pickle using cProfile https://bugs.python.org/issue24676. Issue9914: trace/profile conflict with the use of sys.modules[__name__] https://bugs.python.org/issue9914. Issue9325: Add an option to pdb/trace/profile to run library module as a script https://bugs.python.org/issue9325. Requiere mejorar el módulo runpy https://docs.python.org/3/library/runpy.html. A nadie le ha dolido lo suficiente el bug como para solucionarlo. No es que sea realmente difícil. Tal vez sí. [01:35:53] Nuitka https://nuitka.net/. Ejecutables Python independientes de lo que tengas instalado en el sistema. Por ejemplo, para poder usar una versión de Python "moderna". También funciona en MS Windows. [01:39:43] Tertulia previa: Fuentes de caracteres con ligaduras. Combinación de caracteres unicode. Las banderas de los países, por ejemplo, son un código "bandera" seguido del código del país: https://en.wikipedia.org/wiki/Regional_indicator_symbol. La bandera de Taiwan se ve distinta en China que en el resto del mundo: https://emojipedia.org/flag-taiwan/. "Collation" https://en.wikipedia.org/wiki/Unicode_collation_algorithm, para ordenar y comparar correctamente caracteres unicode: PyICU: https://pypi.org/project/PyICU/. [01:50:23] Cuando el Steering Council https://www.python.org/dev/peps/pep-0013/ vota un tema polémico, la decisión es final. Ya no se busca el consenso a toda costa. [01:52:53] Despedida. [01:53:55] Final.

Mit Christian haben wir uns heute mal wieder ein bisschen mehr über Machine Learning etc. unterhalten. Was wäre, wenn man Jupyter-Notebooks als IDE verwenden wollte (nbdev)? Was braucht man eigentlich heutzutage so an Hardware, wenn man Modelle trainieren will? Ausserdem haben wir ein bisschen auf der Mikrofon/Headset-Seite aufgerüstet (keine Ahnung, ob man das hört).     Shownotes Unsere E-Mail für Fragen, Anregungen & Kommentare: hallo@python-podcast.de News aus der Szene Numpy 1.20 Release Pandas 1.2 Release Spacy v3 Release Ben Gorman: Python NumPy For Your Grandma, Python Pandas For Your Grandpa Mypy 0.800 Release Pip 21.0 Release appenv, batou NBDEV nbdev I don't like notebooks.- Joel Grus Literate Programming I Like Notebooks - Jeremy Howard google colab Binder Buch: Deep Learning for Coders with fastai and PyTorch Machine Learning Recap ocr: Tesseract Vektorrechner / Tensor Cores / TPUs Hardware: Which GPU(s) to Get for Deep Learning Criteo: Display Advertising Challenge Netflix Prize Öffentliches Tag auf konektom

Live from the 2020 ASCEND Space Conference, Acquired covers the full story behind the most "out there" technology story of the past few years: Virgin Galactic. How did this space tourism company grow out of the winning X Prize team, and catch the eyes and fancy of billionaires like Paul Allen, Sir Richard Branson, and, most recently, company chairman Chamath Palihapitiya who took it public via the first "modern" technology SPAC transaction in history? Tune in to find out!! If you want more more Acquired and the tools + resources to become the best founder, operator or investor you can be, join our LP Program for access to our LP Show, the LP community on Slack and Zoom, and our live Book Club discussions with top authors. Join here at: https://acquired.fm/lp/   Sponsors:  Thanks to Tiny for being our presenting sponsor for all of Acquired Season 7. Tiny is building the "Berkshire Hathaway of the internet" — if you own a wonderful internet business that you want to sell, or know someone who does, you should get in touch with them. Unlike traditional buyers, they commit to quick, simple diligence, a 30-day or less process, and will leave your business to do its thing for the long term. You can learn more about Tiny here: http://tinycapital.com Thank you as well to Bamboo Growth and to Perkins Coie. You can learn more about them at: https://growwithbamboo.com https://www.perkinscoie.com/   Playbook Themes from this Episode: (also available on our website at https://www.acquired.fm/episodes/virgin-galactic ) 1. Prizes can be a great way to generate leverage on innovation. If done right, the X Prize and other industry prizes like it (e.g., Netflix Prize, DARPA Challenge, etc) can bring an order of magnitude more talent to bear on a challenge than what the same dollars alone could hire. The challenge is to create a prize that inspires and draws in a large enough pool of contributors. The aerospace industry’s “cool” factor may be what allowed the X Prize to succeed and explain why prizes aren't employed as often in other sectors. 2. When trying new things, most people want to go second — but those willing to go first get the best returns.Being first into new markets carries high risk (including/especially reputational), but often also offers asymmetric upside. Investing in a new frontier when others think it’s crazy is a recipe for success — if you’re both contrarian and right. Chamath took a huge turn from the traditional VC playbook when he created his first SPAC in 2017, years before they went mainstream. He and his investors have generated over $1B in profits from that vehicle (which is now merged with Virgin Galactic), and have since used those proceeds to launch five more. 3. The best time to invest was yesterday, the next best time is today. Great investors don’t miss the chance to invest in big markets because they’ve passed on it before. Sir Richard Branson passed on investing in the X Prize twice before partnering with Burt Rutan's winning team to build Virgin Galactic. 4. Whenever a market's prices aren't being set by supply and demand, there's probably an opportunity to disrupt that market. The traditional IPO pricing process is managed by third parties (investment banks) that represent both sides of the transaction, and also have their own economic interests at play. It's the equivalent of a real estate agent representing both the buyer and seller. As a result, many technology IPOs have left hundreds of millions or billions of dollars on the table. SPACs and direct listings are now solving that problem. Any other market with this dynamic should represent fertile ground for entrepreneurs.   Links: Virgin Galactic's "One Small Step" reservation program: https://www.virgingalactic.com/smallstep/ The November 2020 launch delay: https://www.virgingalactic.com/articles/virgin-galactic-adjusts-test-flight-schedule-in-response-to-new-state-government-covid-19-restrictions/   Sources: Black Sky Documentary: https://www.youtube.com/watch?v=cikmdTVFPig How to Make a Spaceship: https://www.amazon.com/How-Make-Spaceship-Renegades-Spaceflight/dp/1101980494/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=&sr= http://d18rn0p25nwr6d.cloudfront.net/CIK-0001706946/362d3eae-199a-4995-ab78-232a09ced07d.pdf http://www.agent4stars.com/virgin-galactic-passenger-list/ https://abcnews.go.com/Business/story?id=8191703 https://abcnews.go.com/Business/virgin-galactic-resume-selling-tickets-space-reports-skyrocketing/story?id=69229936 https://en.m.wikipedia.org/wiki/Virgin_Galactic https://en.wikipedia.org/wiki/Burt_Rutan https://en.wikipedia.org/wiki/Richard_Branson https://en.wikipedia.org/wiki/Scaled_Composites https://en.wikipedia.org/wiki/The_Spaceship_Company https://en.wikipedia.org/wiki/Virgin_Galactic https://investors.virgingalactic.com/news/news-details/2020/Virgin-Galactic-Adjusts-Test-Flight-Schedule-in-Response-to-New-State-Government-COVID-19-Restrictions/default.aspx https://investors.virgingalactic.com/news/news-details/2020/Virgin-Galactic-Announces-Third-Quarter-2020-Financial-Results/default.aspx https://open.spotify.com/episode/63gIP0UcvBUyhuf0qz1Rza https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5mZWVkYnVybmVyLmNvbS9wcm8tcmF0YQ/episode/OTc4MDliM2MtYTI1NS0xMWU5LWJhZjMtMmYxYWQyZTM2ZmM0 https://sifted.eu/articles/fund-fintech-secret-ian-osborne/ https://techcrunch.com/2020/09/16/cant-stop-wont-stop-social-capital-hedosophia-just-filed-for-its-fourth-spac-says-new-report/ https://www.ainonline.com/aviation-news/aerospace/2007-08-28/northrop-grumman-seals-scaled-composites-deal https://www.bloomberg.com/news/articles/2020-11-05/virgin-galactic-sees-new-ticket-sales-after-branson-s-space-trip https://www.businesswire.com/news/home/20121005005907/en/Virgin-Galactic-Acquires-Full-Ownership-Spaceship-Company#.VFvXsPnF98E https://www.forbes.com/sites/daviddawkins/2020/09/06/inside-virgin-orbit-richard-bransons-small-satellite-bid-to-match-musk-and-bezos-in-the-billionaire-space-race/?sh=1d880f577ab9 https://www.listennotes.com/podcasts/industry-focus/cg-virgin-galactic-prepares-wOHokI4mM06/ https://www.marketwatch.com/story/abu-dhabis-aabar-boosts-virgin-galactic-stake-2011-10-19 https://www.renaissancecapital.com/IPO-Center/News/65718/The-Space-SPAC-Everything-You-Need-to-Know-about-Virgin-Galactic https://www.renaissancecapital.com/IPO-Center/News/72123/Palihapitiya-and-Osbornes-fifth-SPAC-Social-Capital-Hedosophia-Holdings-V-p https://www.sec.gov/Archives/edgar/data/1706946/000114420417044783/v473766_s1.htm https://www.sec.gov/Archives/edgar/data/1706946/000119312519215509/d785777ds4.htm https://www.space.com/31993-stephen-hawking-virgin-galactic-spaceshiptwo-unity.html https://www.spacedaily.com/upi/2004/0831-091100-us-spacerace2-cashprize.html https://www.theguardian.com/business/2014/oct/09/virgin-galactic-space-tourism-richard-branson-george-whitesides https://www.theverge.com/2018/10/13/17967954/virgin-galactic-richard-branson-saudi-arabia-jamal-khashoggi https://www.usatoday.com/story/tech/talkingtech/2018/05/29/amazons-jeff-bezos-says-we-need-leave-earth-survive/651715002/?fbclid=IwAR0E2z5cBtry3Zy0sNRs9jRFKjE_b-T7N-kN0TQO7MDbWJO-baZKw4ZMZGU https://www.wsj.com/articles/richard-bransons-virgin-orbit-seeks-1-billion-valuation-in-fundraising-11602403201?cx_testId=3&cx_testVariant=cx_2&cx_artPos=1#cxrecs_s https://www.wsj.com/articles/richard-bransons-virgin-raises-480-million-with-spac-11601642288

This is the first episode of a podcast series on Machine Learning and Data privacy. Machine Learning is the key to the new revolution in many industries. Nevertheless, ML does not exist without data and a lot of it, which in many cases results in the use of sensitive information. With new privacy regulations, access to data is today harder and much more difficult but, does that mean that ML and Data Science has its days counted? Will the Machines beat privacy? Don’t forget to subscribe to the mlops.community slack (https://go.mlops.community/slack) and to give a star to the Synthetic data open-source repo (https://github.com/ydataai/ydata-synt...) Useful links: Medium post with the podcast transcription - https://medium.com/@fabiana_clemente/... In case you’re curious about GDPR fines - enforcementtracker.com The Netflix Prize - https://www.nytimes.com/2010/03/13/technology/13netflix.html Tensorflow privacy - https://github.com/tensorflow/privacy

스탠다드아웃 66번째 로그에서는 이수겸(@keniallee) 님을 모시고 로블록스, 기계는 어떻게 생각하는가, 실리콘밸리 개발자 등에 대해 이야기를 나눴습니다. 이지스퍼블리싱의 후원으로 도서 나눔 이벤트를 진행합니다. 아래 트윗을 리트윗해주시거나, 아래 페이스북 게시글을 공유하고 댓글을 남겨주신 분 중에 5분을 선정해 ‘기계는 어떻게 생각하는가?’를 보내드립니다. 트위터: https://twitter.com/stdoutfm/status/1216619861943603200 페이스북: https://www.facebook.com/stdout.fm/posts/1799748413500991 도서 링크: 기계는 어떻게 생각하는가? 참가자: @nacyo_t, @raccoonyy, @seapy, 이수겸 개발자 팟캐스트 stdout.fm 정기 후원 - stdout.fm are creating 프로그래머들의 팟캐스트 | Patreon 주제별 바로 듣기 00:00:00 66번째 에피소드 시작 00:03:25 게임 개발 플랫폼 로블록스(Roblox) 00:11:55 닷넷 개발과 프로그래밍이야기 00:19:28 아이폰 초기의 메신저 앱 개발과 미국 진출 00:29:37 기계는 어떻게 생각하는가?(숀 게리시) 01:06:30: 실리콘밸리의 개발자 게임 개발 플랫폼 로블록스(Roblox) Roblox RPG 만들기 - 위키백과, 우리 모두의 백과사전 Unity Real-Time Development Platform | 3D, 2D VR & AR Visualizations 공식 사이트 | Minecraft

แขกรับเชิญตอนนี้ อ.ม็อค ผนวกเดช สุวรรณทัต (บน) และอ.ท็อป วัชรพัฐ เมตตานันท (ล่าง) เว็บไซต์สาขาคอมพิวเตอร์ สสวท. http://oho.ipst.ac.th Facebook: สาขาคอมพิวเตอร์ สสวท. www.facebook.com/oho.ipst/ เว็บอย่างไม่เป็นทางการเกี่ยวกับหนังสือเรียนประถมศึกษา (โป้งก้อยอิ่ม) website: www.pongkoiim.com FB page: "บันทึกของโป้งก้อยอิ่ม" http://fb.com/pongkoiim วิธีการซื้อหนังสือแบบเรียนฉบับการ์ตูน​ (โป้งก้อยอิ่ม) - short URL (เพื่อซื้อจากศึกษาภัณฑ์ออนไลน์): http://pongkoiim.com/buy - วิธีการซื้อแบบอื่น (เช่น ซื้อจากร้าน หรือสั่งซื้อแบบขายส่ง): https://www.pongkoiim.com/go/?page_id=2 เว็บไซต์ที่ใช้ฝึกเขียนโปรแกรมสำหรับเด็กและคนทั่วไป: www.code.org -------------------------- ประเด็นความเป็นส่วนตัวของข้อมูล เรื่องข้อมูลการแพทย์ที่ไม่เผยชื่อ แต่สุดท้ายไปเทียบกับข้อมูลชุดอื่นแล้วบอกได้อยู่ดี -1,2,3 ข่าว Netflix Prize -1,2 ประเด็น Ai Bias การเหยียดเพศ เหยียดผิว ที่เกิดโดยไม่ตั้งใจ ข่าว Ai ของ Amazon อ่าน Resume คนสมัครงาน แล้วกีดกันผู้หญิง -1,2,3,4 ข่าว Google Photos แท็กคนผิวดำว่าเป็นกอริลล่า -1, 2,3,4 https://twitter.com/jackyalcine/status/615329515909156865 ข่าวรถขับเคลื่อนอัตโนมัติของ Uber ชนคนตาย -1,2,3 ข่าวอุบัติเหตุอื่นๆ ที่เกิดจากโหมดขับอัตโนมัติของ Tesla - 1,2,3 ตัวอย่างการให้คนทำงานควบคู่ไปกับ Ai แล้วดี การแนะนำคอร์สของ Udacity อ้างอิงนาทีที่ 33:50 ของ podcast นี้ https://www.wbur.org/onpoint/2017/06/26/machine-over-mind-in-a-new-economy และบทความ https://hbr.org/ideacast/2017/07/how-ai-is-already-changing-business.html งานวิจัยความเบร้อของ Ai ในการจำแนกภาพ -1 รูปหมูสามตัวนี้ ตัวแรกคือรูปหมูจริงๆ ai ก็เห็นเป็นหมู ตัวกลางคือรูปที่โดน add noise แล้ว ai เห็นเป็นตัววอมแบท รูปสุดท้ายคือปรับ noise ใหม่ให้ ai เห็นเป็นเครื่องบิน (ทั้งสามรูปมนุษย์ไม่เห็นความแตกต่าง) วอมแบทตัวจริงหน้าตาแบบนี้

So you’re trying to win the Netflix Prize. You need to create a recommender system. A recommender system gives recommendations to users - for Netflix: movies they’ll love. Spotify: songs they’ll love. Amazon: anything they’ll buy. And this is big business. A full 35% of Amazon’s revenue comes from its recommender system. In this episode, we’ll learn about how to build the two key types of recommender systems.

Researchers: Christopher Brinton, Zoomi, Inc. and Princeton University, and Mung Chiang, Purdue University Moment: http://www.ams.org/samplings/mathmoments/mm139-netflix.pdf Description: Christopher Brinton and Mung Chiang talk about the Netflix Prize competition.

If our potential matches on Bumble feel hotter than other apps, who's making that decision? What does this mean for us normals? Reynald Adolphe caught our eye with his blog post: "Is Bumble's Algorithm Filtering Ugly People?" He is a software engineer and teaches other people how to be engineers, too. He tweets: @reynaldadolphe Chris Volinsky was part of the winning team for the Netflix Prize to develop a better recommender system. He's assistant vice president of big data research at AT&T, and he tweets: @statpumpkin To discuss this week's episode, head to facebook.com/whyohwhyradio or tweet with #whyohwhy. You can find Andrea on Twitter as @andreasilenzi. Learn more about your ad choices. Visit megaphone.fm/adchoices

We start off with a discussion of a couple of USB-C hubs to add ports back onto the MacBook Pros. Aaron gives us a review of his new 2106 MacBook Pro 13 inch with TouchBar. We look at 1Password with Touch ID devices. We also discuss a few reviews on using the new MBPs. We discuss Touché a TouchBar emulator for macOS, the new Apple coffee table book, Designed By Apple in California, and cuts to Apple video subscription fees. We wrap the main topics on the rumored Apple glasses project and augmented reality (AR). Picks: API Reference, Learning From Data, (Dash iOS, Arrival.) Sponsored by: Buddy Build Episode 119 Show Notes: Review: CalDigit USB-C Dock – an okay solution for MacBook Pro owners, if you’re willing to make compromises Arc Hub 1Password New Touchbar Equipped MacBook Pros and the State of the Mac Wide gamut on iphone 7 One Professional’s Look At The New MacBook Pro Move Your Content to a New Mac Touché Apple to Halve App Store Fees for Subscription Video Apps “Designed by Apple in California” chronicles 20 years of Apple design Apple's £249 book contains 450 photos of Apple products Keep It Simple: The Early Design Years of Apple Iconic: A Photographic Tribute to Apple Innovation (Amazon - $50) http://iconicbook.com REVIEWED: Here are the most interesting parts of Apple's new $300 book Apple Considers Wearables Expansion With Digital Glasses Playstation VR HTC Vive Google Cardboard Nintendo Wii Lawnmower Man (Movie) Lawnmower Man (Book) Ready Player One Starship Troopers Vuforia String Rogue One Netflix Prize And the Pulitzer goes to… a computer Dash iOS OpenSource Initiative: Licenses and Standards use NSSet for common platform use case Twitter adds QR codes for some reason Tim's Instagram "vine" Red Laser ReLive Use Accessibility features in iOS Episode 119 Picks: API Reference Learning From Data Arrival (after show)

My guest this time is Xavier Amatriain. Xavier is a former researcher who went on to lead the machine learning recommendations team at Netflix, and is now the vice president of engineering at Quora, the Q&A site. We spend quite a bit of time digging into each of these experiences in the interview. Here are just a few of the things we cover in our discussion: Why Netflix invested $1 million in the Netflix Prize, but didn’t use the winning solution; What goes into engineering practical machine learning systems; The problem Xavier has with the deep learning hype; And, what the heck is a multi-arm bandit and how can it help us. The notes for this show can be found at https://twimlai.com/talk/3.

This week, Dr. Thomas Whitley and Rev. Sam Harrelson discuss the cloud, smaller phones, homoeroticism in the Bible, the Jerusalem Church and Paul, and why social media is not making us pick or choose our beliefs. Mentioned: Evernote was down today iPhone SE Gboard Netflix Prize Bernadette Brooten : Love Between Women  Council of Jerusalem Jesus’ brother lays a smackdown on Paul – TIL #7: “Fly from Heaven” Fly From Heaven (If He’s All You Say) | On Pop Theology Is Social Media Making Us Pick-and-Choose Our Beliefs? | RNS The post Thinking Religion 78: Homoeroticism, Paul, and James appeared first on Thinking.FM.

On episode eight we talk with Charles Sutton, a professor in the School of Informatics University of Edinburgh about computer programming and using machine learning how to better understand how it’s done well. Ryan introduces us to collaborative filtering, a process that helps to make predictions about taste. Netflix and Amazon use it to recommend movies and items. It's the process that the Netflix Prize competition further helped to hone. Plus, we take a listener question on creativity in algorithms.

Man Fights Back - Podcast #25 - Download MP3Alternate Download Link for Episode #25 - Download MP3Opening Clips: Butt Plug?Bee Gees vs Pink Floyd - "Shut Up Let's Hook Up" (ft Jason Downs)MFB Opening ThemeOpening Comments:Tribute to Officer Leslie Hulse - Her fight ends on 9/28/2009-Leslie's Story-Police department helps fellow officer fight cancerMusic Tribute:Mindy Smith - "One Moment More"Opening Comments (Continued):Andrew E's Starbucks Investigation on Drive ThruEddie V's Comcast experience with "upgrades"Music Break:Norova - "Transfection"Fortune Cookie Message of the Week:Motivational - "Make two grins grow where there was only a grouch before." - A Wise ManTechnology News:Cloud Computing - What it is and why....Secret Service Tackles Facebook PollThe Netflix Prize was brilliant. Google and Microsoft should steal the ideaHow Vizio Went From Nowhere to No. 1Music Break:John Clarkson - "4 KG"National News:Montana Town Occupied By Private Paramilitary Security ForceNew Government Policy Imposes Strict Standards on Garage Sales NationwideNurses Plan Rally To Protest Mandatory Swine Flu ShotMSM: Another Microbiology Researcher DiesMusic Break:Marti Walker - "To Late for Love"Music Mashup Trivia #16News Clip Break: From No Agenda # 133Indiana News:Little Nashville Opry Fire Was Intentionally Set2 Arrested In Wedding Crasher TheftLocal car wash recognized nationallyMusic Break:Tantra - "Trees"Strange News:BUSTED: Burglar Arrested After Checking Facebook During RobberyDust blizzards turn the sky red down underPrison sentence for woman who kept mom's bodyReturn of the Burger (and Hot Dog) KingStudent accused of rubbing sleeping women's legs Ending Music:Mark Barnwell - "Exotica"

Tikk Domonkos (Team Gravity): Skálázható kollaboratív filtering módszerek a Netflix Prize versenyen

Intro: You may think Google and Yahoo have a lock on search but it may be time to starting thinking a little differently. In this podcast we take a look at some niche search sites. Mike: Gordon, we love Google products and services - is there a the problem? It may be Google does too good of a job! Have you ever tried Google searching on a persons name? A simple Google search on my first and last name gives over 1.9 million results! Today, three companies control almost 90% of online search: - over 50% of all searches are done using Google - over 25% on Yahoo - and over 13% using Microsoft There are some problems though – these search engines primarily give results based on the number of sites linking to a page and the prominence of search terms on a page. Because they work this way there is room for niche. Mike: With this kind of lock on search it would be almost impossible for a startup to launch a successful general search product - right? Yes - it would be almost impossible but we are seeing some acrivirt in the niche areas. Areas like travel and finance are niches that have already been filled but today there seems to be some room in the people search area. Mike: Are there companies in this market we should be looking at? One of the startups to watch is Spock at www.spock.com. Spock is scheduled for their public launch the first week of August. Among other places on the web, Spock scans social networking websites like Facebook and LinkedIn. Search results give summary information (age, address, etc) about the person along with a list of website links that refer to the person. According to Spock 30% of the 7 billion searches done on the web every month are related to individuals. Spock says about half of those searches concern celebrities with the other half including business and personal lookups. According to Spock, a common problem that we face is that there are many people with the same name. Given that, how do we distinguish a document about Michael Jackson the singer from Michael Jackson the football player? With billions of documents and people on the web, we need to identify and cluster web documents accurately to the people they are related to. Mapping these named entities from documents to the correct person is what Spock is all about and they’re coming at the problem in an interesting way. Mike: I've looked at Spock - what is the Spock Challenge? They’ve launched what they call the Spock Challenge – more formally referred to as the SPOCK Entity Resolution Problem linked here: http://challenge.spock.com/pages/learn_more If you go to the site you can download a couple of data sets – one called a training set (approx 25,000 documents) and the other called a test set (approx 75,000 documents). Along with the document sets they include a set of target names. You assume that each document contains only one of the target names (even though most documents contain many names). The challenge is to partition all the documents relevant to a target name by their referent. Mike: When does the contest begin and end? It has already begun on 4/16/07. It will end on 11/16/07. On 11/16/07, Spock will run the final round of the competition and announce the winner.Here are the dates off the website: 4/16 Registration started 5/1- 8/15 Proposal submissions accepted 7/1 Leader board live 11/1 Finalists announced 11/16 Final round at Spock, winner announced Mike: What languages and tools be used?You can use any language and any non-commercial libraries, tools and data to develop the solution. There is one catch - the winner grants Spock non-exclusive right to use the software and data. As an FYI, much of Google is actualy written in Python with the Search Engine Core written in C++. Python provied scripting support for the search engine. and some apps like google code are done in pythonMike: Can you give us and example of how this works?From their website: Consider the following two documents with the target name "Michael Jackson": Michael Jackson - The King of Pop or Wacko Jacko? Michael Jackson statistics - pro-football-reference.com The referents of these articles are the pop star and football player, respectively. They’ve also included the ground truth for the training set so you have something to compare against. Once you're done training, you can run your algorithm on the test set and submit your results on this site. Spock will provide instant feedback in the form of a percentage rank score. This way you can see how you stack up against the other teams. So they provide you with a lot of well constructed data, and the ground truth about that data. “Ground truth? data is real results and you use this information to validate your search algorithm results. This data is documents about people, and the challenge is to determine all the unique people described in the data set. This data can be your training set. Once you have got your basic algorithm working against the training set, they let you further tune your code by running it against a second test data set and give you instant accuracy feedback in the form of a score. The score depends on how many correct unique people you can identify in the data. This way you can continue to refine your work, and see how you are doing, and how well others are doing. This looks like a great academic challenge. At the end of the contest time, you submit your code, a 3 page description of your approach, pre-built binary executables that can run in isolation on Spock servers, and your results (the “Software Entry?). Spock will select the finalists based upon submissions, and fly the finalists to visit the judges. The winner will win $50,000, 2nd place wins $5000 and 3rd place wins $2000. Mike: How doe people enter?You may enter the Contest by registering online at www.spock.com/contestregistration . You may register as an individual or as a team. During the registration process, you must provide your name, your age, your email address, and the country you are from. If you are entering on behalf of an organization, a school or a company, you must identify its name. If you are registering as a team, you must provide the same information for each member of your team as well as the identity of a team leader. You will also provide a name for your team or for yourself by which you or your team will be known to other participants in the Contest. Spock may change the name if it feels the name you select is not appropriate for any reason. Mike: What are the differences between the Spock Challenge and the Netflix Challenge? From Netflix website: The Netflix Prize (http://www.netflixprize.com ) seeks to substantially improve the accuracy of predictions about how much someone is going to love a movie based on their movie preferences. Improve it enough and you win one (or more) Prizes. Winning the Netflix Prize improves Netflix ability to connect people to the movies they love. Netflix provides you with a lot of anonymous rating data, and a prediction accuracy bar that is 10% better than what Cinematch can do on the same training data set. (Accuracy is a measurement of how closely predicted ratings of movies match subsequent actual ratings.) If you develop a system that Netflix judges  beats that bar on the qualifying test set they provide, you get serious money and the bragging rights. But (and you knew there would be a catch, right?) only if you share your method with Netflix and describe to the world how you did it and why it works. In addition to the Grand Prize, we’re also offering a $50,000 Progress Prize each year the contest runs. It goes to the team whose system we judge shows the most improvement over the previous year’s best accuracy bar on the same qualifying test set. No improvement, no prize. And like the Grand Prize, to win you’ll need to share your method with us and describe it for the world. The Netflix contest started October 2, 2006 and continues through at least October 2, 2011.So..... back to your question - The Netflix Challenge will run another 4 years; Spock Challenge has every intention to give out the grand prize to a team with a reasonable solution at the end of the 6 months. Netflix Chellenge sets an absolute standard for winning the grand prize; Spock Challenge intends to award to the best reasonable solution. Mike: How about some other companies? Wink – www.wink.com Similar to Spock – launched a few months ago. Claim that Wink People Search now searches over two hundred million people profiles. Searches people across numerous social networks including MySpace, LinkedIn, Friendster, Bebo, Live Spaces, Yahoo!360, Xanga, Twitter and more. Also included in the results are Web sources such as Wikipedia and IMDB with more coming all the time. Zoominfo – www.zoominfo.com Specializes in executive searches. Claim 37,131,140 People and 3,518,329 Companies indexed. You can currently search on three categories – people, jobs and companies. Searchwikia - http://search.wikia.com Jimmy Wales and his open-source search protocol and human collaboration project. From Press release: "Last week Wikia acquired Grub, the original visionary distributed search project, from LookSmart and released it under an open source license for the first time in four years. Grub operates under a model of users donating their personal computing resources towards a common goal, and is available today for download and testing at: http://www.grub.org/ . Grub, now open source, is designed with modularity so that developers can quickly and easily extend and add functionality, improving the quality and performance of the entire system. By combining Grub, which is building a massive, distributed user-contributed processing network, with the power of a wiki to form social consensus, the open source Search Wikia project has taken the next major step towards a future where search is open and transparent".