So we are going to do a Q&A panel with Paula and Eric. So we will start with an icebreaker question for Paula. So I've seen that in celebration of Clojure, getting the Clojure Java math namespace, you've ported it over to ClojureScript, which is super awesome because we love to see you do one more ClojureScript stuff. You said that unfortunately run into the problem that the JavaScript math isn't as capable as the Java math though. So you've had to re-implement a lot. What was the toughest part of doing this? The IEEE remainder function. There's a function for dividing one double, 64 bit double by another one and then finding the remainder value from that as accurately as possible. And that was really tough to get right. The code was available in C on the JDK because it's released as GPL. Anyway, I ported it into JavaScript and then once I had it working right there, that helped me get it right in ClojureScript. There's a lot of bit operations and there's expectations of having access to different word sizes and you can change the pointer types. And this is what C was doing internally and the way I had to make that work in ClojureScript was really quite difficult, but yeah, I've got it working. And yeah. Okay, let me do like the icebreaker for Eric as well. And we want to ask, what is your favorite dish to cook and why it's not cookies? Because I would eat too many cookies. That's the answer to the second question. What do I like to cook? I like to cook gumbo. I really like to gumbo. It's fun. There you go. It's a nice process. And what are the ingredients for that? Well, first you start with a roux, which is flour and an oil and you toast the flour in that. Gumbo's have a pretty dark roux if you're used to making a roux from French cooking. It's much darker. And so it kind of has this exciting aspect of testing your cardiovascular health because you can burn it and you want to take it right up to the point before you burn it. So it's kind of a game of chicken with your flour. Then you can put whatever you want, but I tend to put in okra. Gumbo's one of those kind of like empty your fridge of all the little ends and bits that you got left over from other things and just throw it into a big soup. Well, hopefully next time in the New Orleans you will cook some for me. I'm holding you to that. So we have a hand raised egg Davis. Yeah, I asked this on the Discord but then I was reminded that you all are enjoying questions being in person. Erica, I was thinking recently about causal loop diagrams. I don't know if you've run across those. I just clicked on the link that you shared. I have not come across them. So I'm going to check them out. Yeah. Are these, these are kinds of like systems, analysis, feedback loop kind of things. Exactly, yeah. And I mean, mostly I've seen them as like ways of exploring physics stuff but just recently occurred to me that it could be really interesting as a way of modeling business domains. I'll check them out. Thank you so much. Okay, so let's get Paula back in here. Ray on the Discord asked, Paula, can you tell us something about your graph database, ASAMI? What was the motivation behind it and what sorts of problems it's a good fit for? I would like to add how long have you been working on it and tell us a little bit more about the name. It's a lot of aspects to that question. I had been working on a previous RDF database called Moldara for over 10 years that was written in Java and I lost interest over time because it was written in Java and I was into closure by that point. I had an idea of re-implementing in closure but hadn't really got to it until an element that I'd written for Moldara was a rules engine which does this bottom-up evaluation for Datalog and I had this idea that I could re-do that for any graph database if I just hit the database behind a protocol. So I tried this with Datomic and showed my boss at work who said, you should try this at work because we need to do some referencing and he didn't like the idea of working with a commercial system. He said, I could take the rules engine which was open source and do, I needed to talk to an open source graph database. We weren't aware of data script and so I started doing something in memory and that became a summary and then I kept adding features to it in my own time including the storage layer which I did last year during a pandemic and it sort of, it grew a lot from that. So it's like Moldara but it's entirely in closure and it's taken on a lot of the new indexing ideas that I've had in the last 20 years. As for the name, we had a number of projects at Cisco where my manager was really into Avatar, the Last Anteberna and the SQL Cora and so a number of projects were named after characters in those shows. Well, the character Asami was Asami Sato while some of the other characters had these like superpowers with the bending. She didn't have anything like that but she knew technology and she would build things for herself so that she joined in with her friends and I liked that idea because I didn't have a graph database and I built one myself. Yeah, that's great. That's one of my favorite fun facts about Asami. Let's go back over to Renzo to hear more from Eric. Yeah, so I have a question for Eric. Do you think that the traditional roles found in most agile software companies are equipped to handle the domain-driven model that you are advocating for? And could we need to add additional supportive roles between product managers and technical leaders? Wow. I have not thought much about how this fits in with the sort of black box ticket machine that we've created with the current agile system. I'm not a big fan of the way I see agile working so I'll just, I'll put it that way. What I see is that business people, project owners or whatever, product owners, whatever they're called, just add tickets and then the programmers just do the tickets and there's very little because the program, it's easier, the asymmetry of it. The programmer is working longer on the ticket than it took to write. So it's always easier to get a longer backlog than you can actually finish. And so the programmers never really have time to get a global view of the tickets coming in and like what model are we actually making? And so I don't know if it would fit into agile at all to say like, hey, let's take a break and do some design work and some sketches and like maybe your, all these tickets don't make sense anymore. So I will elaborate, Eric, because that was actually a question for me. Oh, okay. So I think that traditionally we have like the product people and they know all the product stuff and they don't care or know about the code then we have all the code people and they know all the code stuff and that's all they care about. But not a lot of companies have like the glue holding them together. And a lot of times, software engineers or customer success people will try to fill those roles but I guess I think your domain driven model kind of advocates for the requirement of an additional role in a company that's like between understands technical but isn't leading technical and understands product isn't a product manager but can help those two. So, I mean, this is something that I don't think I'm prepared to discuss fully but there is a great book called The Inmates Are Running the Asylum and it's about the problem of just having these two roles of like business and dev and it argues for a third design role because the business is they're really trying to maximize profits, right? So more income, less cost and the programmers are kind of trying to make their job easier, you know, do the job but do as little as possible and there's no one advocating for the user really and the user is the kind of the person that the model has to serve ultimately. It does help the programmers, right? By having it making, if you have a good model the model that actually serves the users it's easier to write code that serves the users. If your model is different from what the users actually need then you're gonna have to write all these complicated code to like adapt it all the time and that's what's gonna lead to all this complexity. So I think that that's a good direction like having this third role who's kind of advocating for the user and then that lets you have some sort of team of maybe a special team of three stakeholders who can come together and talk about the model outside of the code. I think that's another problem in Agile is that the programmers are asked to do both the low level like let's make these tickets happen and the high level sort of evaluate these tickets and like understand the context and switch between that really quickly. And so you never have a, like you're going from this like engineering, like just get it work at like whatever it takes, get it to work and then you have to switch to a wait maybe we don't wanna do this, what's the context? Like, and that is very hard for your brain to do that. And I've seen it happen in companies where it's like a programmer will be coding up to the wire. Now we have a meeting to like evaluate these tickets like your brain needs an hour at least. Maybe you even need like a week from if you've been doing coding a lot. So I find that that's another problem like there's a human aspect, the psychological aspect missing from Agile. Yeah, the cost of context switching is certainly a cost me underestimate. Okay, going back to Paula, we have a question from Jacob on Discord. He says, comparing the performance of retrieving a whole data entity, for example, a person from an RDF database versus an RDBMS is the former significantly slower because it has joined on each attribute or is it just as fast because all the attributes are stored next to each other in the EAV index? It's a little bit slower, but in general, your bottleneck is in your storage. And these days that's often as likely to be in the cloud as it is locally. And so the work to bring those things together into a local entity is trivial in comparison to waiting for this stuff even coming off this. If you have a lot of things cached, yeah, there's a small performance cost there, but generally when you retrieve this data, it'll usually be co-located. You can bring it in, you can restructure it and return it. If it's in memory, it'll be a little bit slower. And if you run it through a criterion, you'll see that difference. But in general, you're going to see records come in and be restructured as an entity. At a similar pace, it's the tertiary storage, which is the real cost. And their locality is normally all right when it comes to that tertiary storage. So we can perhaps take the next question for Philippe. Hi. This is a question for Eric. Hi, Eric, great talk. Thank you. So I want to ask a bit about the process because what you've described is obviously a process by which you come to certain results. But a big part of how this sort of, this thing ends up, you're having the need for this process is the fact also that there is a disconnect. Like the people that have the model, maybe they're not talking all the time with the people that don't have the model in their heads. So even in the example you gave, it's like a multi-step process by which at some point someone realized, maybe we should look at the model. So my question is like, how do you actually, in what ways have you had success? Like actually putting down this model, collaborating with other people on this model and actually iterating over this model in the times that it's actually important to change it and update it? So these are all really good questions. And it's a little bit outside the scope of what I had in mind. So, but it's really good question. So now I'm thinking maybe I need to talk about it, but I'm also thinking maybe I focus too much on process and not enough on the sort of underlying groundwork of what you can even do at a domain model level before, and like an abstract level before you get into code. So thank you, this is really good information. So I do, but I do wanna answer your question. So what you asked about what successes I've had. So there are successes like when I'm working on my own definitely I will realize, oh, this model needs to be different. And then I go back to a more abstract level and I can work there. Of course I'm working on my own project like I don't have to answer it to anybody. In terms of like on a team, I've seen it work in the small. So maybe you realize that this a small part of your domain could be different. So for instance, maybe you're doing some kind of user interaction in a GUI and you realize, oh, if we just kept a log of these instead of mutating stuff in place, that would make all these things that we have to do easier.  In the large, I think that one of the jobs that I need to do is to make it apparent is to make the argument for how valuable this can be that it can speed up your development certainly but it can also be because software is like basically running businesses now, like the business, how it works is like in the code. I think that it can give you a real business advantage apart from just like the speed of development. I think that it can give you a clearer view of like it can give the business, the whole company a clearer view of the system that they're working with. And I like to use this example of like double entry bookkeeping, it's like, can you imagine a bank with a different model who's just like flailing all the time because they're not keeping books that well. And then someone comes up with double, the bank that comes up with double entry bookkeeping is like beating them and it's simply a change in model. The whole business is based on a different model. It happens to be encoded in their information system but that's happening more and more. And I think I need to come up with like find some real world examples where someone with a better model actually succeeded in competition because the model was different. And it wasn't just, oh, we were swamped by technical debt it's more like the model made their business better. So thank you so much, Felipe. I hope that answers it. And we can talk offline, we can talk in the chat if you want to go deeper. Sure, let's do that. Thanks again. Thank you, Felipe. Absolutely, Jordan. Any more questions for Paula? Yes, so I'm sure there are many people that are looking for opportunities to contribute and I'd like to give you a chance to a space where you have next steps you'd like to suggest to people where they can learn more, perhaps previous talks you've done in the past, good starting points for people to learn more about Asami and what you're doing. I've written a lot on the Asami Wiki. I've tried to put a lot of effort into like describing each of the different elements, how to go about using them, what the structures look like. There's even a number of pages on what the architecture is and how things interact. It's not perfect, but there's only so many hours in the day. Another place to go is Datomic. They have extensive documentation. They have a very fast-moving project and a lot of people working on it. So I have seen the dots get out of sync with the project on occasion, but it's generally quite good. So these are two really good sources. Well, I like to think that the Asami source is a good one. I put pictures in there and things. But while Datomic doesn't present itself really as a graph database, and it's not particularly strong in that way compared to some which are out there, it is a graph database and you can use it as such. So in general, looking for graph database resources can help, but I think working through the Datomic documentation is probably your best bet. And then if you learned about graph databases, you could build on top of that. Is there a second part to that question? I think you answered it. Sorry. Thank you. So let's see. We are approaching the end of the slot, but we should have time for another couple of questions, I believe. So for Eric, we have, well, I can pronounce that Kingsnooks, Kingsnooks, something King. Eric, is there a standard timeline, for example, two weeks to a month during which modeling, mass, mature, once a project requirements are completely understood? This is the first part. And then there's a second part. Eric, would you describe or to what degree to the idea that a design be centered around areas of volatility? Thank you. So the first one, Eric, again, is during which modeling mass mature, so what is the period where modeling mass mature once a project requirements are completely understood? Right. Again, this is a process question. And now I'm very much regretting talking about process. It's not like I don't want to talk about process as much as it seems to questions are fine. I want to talk about stuff like the sizes, that's an alternative. You choose one of these three sizes and that is an abstract thing that we can do before we jump into code, right? And that I want to catalog all these choices, these possible ways of modeling different things and then also talk about how those can be implemented in code. So, oh, closure has these seven ways to implement alternatives and Java has these three ways. And I want to do stuff like that. And so it's much more about sort of the Lego bricks of domains, of domain models, how to analyze your domain to find what those things might be and then how do you translate that into a language. The idea of process like, oh, have a three week sprint and then write down all these things on sticky notes and like that, I don't think I'm that good at that. So I don't want to touch that. The thing about whether to design it around areas of volatility, I think that that's very important and a lot of architects, software architecture experts talk about that, how one of the, this is one of the key areas of, key insights of David Parnas in talking about modularity is you want your modules to encapsulate this volatility. And an example of this is, well, the wrong way to do it is you break up a house thinking about the areas of functionality. So you think of stuff like, well, there's the kitchen, that's where you make your food, there's the bathroom, there's the bedroom. And so you think of those as the modules and then you like connect them together with doors, right? But really, when you look at your house, the modular stuff is different. The module, if you look at the volatility, you say, oh, wait, we need to be able to plug in different appliances at different times, right? You don't want to build in, I mean, they used to do this and they've learned it's a bad idea. Like you build in your vacuum cleaner system into the house.  It's like a standard interface that allows any module to be plugged into the house. And then you have like your plumbing, right? And that's like a different module. Like you want to be able to put different fixtures in without like ripping down the whole house and changing all the walls, you know, the plumbing and the walls. So looking at stuff in terms of what changes, like, you know, your furniture, it's very modular. You can change out your furniture, you don't have to touch the house, you don't have to rebuild anything. So to look at the volatility, I think is like one of the first things you should do. And that's kind of just architectural advice. It doesn't speak so much about the domain model, you know, the model of the house. I brought up volatility mostly because when you're implementing it, you have to make this choice. There's different ways to implement alternatives. You can make an enum, you can subclass an interface or you can make it values that are like strings that you can put in a database and all of them have their uses. There's not like one that's the right way to do it. And what, but how do you decide between them? It's all about volatility. And I think that that's something that's just not discussed that much, you know, I think that there's a tendency to say, like, well, let's just subclass everything and enum is, oh, that's just for like simple things, like simple strings that instead of using constants, like I think that that's the wrong way to look at it. You should look at it much more like you have to change an enum if you wanna add or remove something or change anything. You actually have to go open that code and change it. Whereas a subclass is open, you can just add a subclass and then the runtime stuff, well, you just add a new row in the database. Like you don't even have to touch your code. So yeah, that's the answer to that. Okay, great. So we are getting close to our break before our next session here. So we have one last question for Paula from Ray on Discord. And Ray says, when I see Datalog, I think of prolog and logic programming. Is there some synergy between Datomic and Core.Logic? Can the two be used together to solve more interesting problems than just data retrieval? I haven't done a lot of work with Core.Logic. I do know that David Nolan put some effort into connecting it to the assertive statements for connected to a database, as opposed to simply being in memory. I'm not sure that that would be the best approach to handle a lot of scaling issues. The sorts of rules which I was describing that Datomic can use, I think will be much more performant, but it's harder to apply than Datalog, I think. And I mean, that connection to logic programming and prolog is quite real. It's specifically designed to be like prolog over a corpus of data, as opposed to a space which needs to be searched all the time. There have been numerous attempts in the last 40 years or so of trying to integrate the two. Certain things have been done that in this top-down logic programming where solutions are searched for, the way that prolog does, the way that systems like Minicamron or Core.Logic do, these can solve certain sorts of problems while Datalog can't really approach those. However, Datalog has these restrictions on it which let it work really, really well with databases, graph databases, especially, I think. And while there's similarity there, there's also things which one can do that the other doesn't really have a very good handle on. Personally, my experience has been that logic programming hasn't required the scalability that databases provide us. And well, I mean, when I say logic programming, the complex stuff that Core.Logic and that prolog are really strong at doing, I haven't seen them applied to really large purposes of data to great effect, while if you can restrict your logic language down to what can work in Datalog, that works against databases, exceptionally well. There hasn't been a lot, there are a few cases, but there haven't been a lot of instances where you want that processing power of, say, prolog or Core.Logic being applied to massively scalable data. And the fact that those two don't often need to intersect has been fortuitous, but yeah. So I know Datalog can be put over the front of a database and David Nolan has done that. Not that I'm sorry, Core.Logic can be done over a database. David Nolan has done it, but I haven't seen it being picked up in the news. Okay, great, thank you Paula. So we are at the end of the Q&A panel and we would love to thank Paula and Eric for speaking today. And if you have any more questions that Paula and Eric are both very active in the community, please reach out to them on Slack or email. And I'm sure they'd be happy to answer any questions you have.


The jack Benny program presented by Lucky Strikes LSMFT-LSMFT Lucky strike means fine tobacco- fine tobacco that gives you a truly finer smokebut Yes, Lucky strike means fine tobacco year after year at auction after auction independent tobacco experts can see the makers of Lucky Strike Constantly select and buy that fine. That light. That naturally mild tobacco. Just listen to what mr. B.V. Bowen, 40 years an independent tobacco buyer of Timminsville, South Carolina recently said. I make my living buying tobacco, and year after year, I've seen American buy fine, light, full-bodied tobacco, ripe, mellow tobacco that makes a smooth, mild smoke. For 22 years now, I'll smoke luckies regularly. Take a tip from the experts. For your own real deep down smoking enjoyment, light up a lucky, light up a really finer cigarette and puff by puff, you will see. L.S. M.F.T., L.S. M.F.T. Lucky strike means fine tobacco, so smoke that smoke of fine tobacco, lucky strike. So round, so firm, so fully packed, so free and easy on the draw. Remember, there's no finer cigarette than luckie strike.  The Lucky Strike program, starring Jack Benny with Mary Livingston, Phil Harris, Rochester, Dennis Day, and yours truly, Don Wilson. Ladies and gentlemen, as you may know, this is National Pickle Week.  Thank you, thank you. Hello again, this is Jack Benny talking, and Don, you certainly went a long way for that introduction, didn't you? No, I didn't, Jack. This really is National Pickle Week. Well, dilly, dilly. Jack, a pickle's nothing to laugh at. Our first joke proved your point. But as long as it is National Pickle Week, I want to say congratulations to all the mama pickles, papa pickles, and all the little boys and gherkins. Now, Don, let's get on with the... Hello, Jack. Oh, hello, Mary. I'm glad you got over your cold. We missed you last week. Well, thanks. What are you and Don talking about? What are we talking about? You mean you haven't heard? Heard what? All over the country, flags are flying, parades are forming, and you don't know? Know what? Mary, this is National Pickle Week. Pickle? Yeah, that's a cucumber that had its option picked up by Heinz. You know, Don's right, I am a barrel of fun, isn't I? For this, I had to get well. Well, you can thank me, Mary, for sending my doctor over to take care of you. Oh, fine. Some doctor. What are you talking about? He's an excellent physician. Yeah, but boy, is he nearsighted. Huh? As he came into the house, I thought I'd save a little time. So when he walked over to me, I stuck out my tongue, and he hung his hat on it. Hung his hat on your tongue? Then he walked over the clothes rack and said, Don't stand there in the corner with three coats on if you're cold, get in bed. Gee, I didn't know he was that nearsighted. He can't hear either. The doctor can't hear? I said goodbye to him four days ago, and he's still there. Oh, well anyway, Mary, you're back on the program, and that's all that matters, because tonight we're going to do a very important sketch. Come in. Mr. Benny? Yes? I drove you down to the studio of my cab, didn't I? Yes, yes, you did. The fare was $1.95, and I paid you. Well, I've been thinking about the tip. The tip? What about it? Look, I know this is National Pickle Week, but I'd rather have money. You'll keep what I gave you. Goodbye. We've got a lot of nerve breaking in on my program with those silly jokes. Wait a minute, Jackson, don't get mad at the cab driver. He deserves a lot of credit. The guy comes in here without a script and gets a laugh. So what? Well, that's the way we'll all have to do on television. No scripts, no nothing. We'll have to add lib our way. Well, I won't have any trouble. I'm a barrel of fun.  Sit down and learn stuff. Oh, yes, you do. Not unless you're 100 proof. Now, look, I'll show you how television's going to be, Jackson. Hey, Liv, he asked me. He asked me what I did yesterday. Okay, Phil, what'd you do yesterday? I played golf. See, it's easy. Well, Phil, what's funny about that? Don't rush me. Now, come on, Liv, ask me what happened on the first tee. Okay, what happened on the first tee? I drove off and hit Walder pigeon.  Phil, look, Phil, what's funny about hitting Walder pigeon? Well, don't you get it? On my first shot, I got a birdie.   Well, that's the idea. Jackson, Milton, Burl and Steeler get thrown off of television and then there's a chance for us. Well, I hope he steals our first three pages. It'll give them a running start. I think Milton is very clever. Oh, he is, eh? Libby's right, Jackson. Milton is a burl of fun. Oh, Harris, you like a car without brakes? Ain't no stopping you. Uh, don't worry, folks. He'll be normal in a couple of days. Yolkham's moon will soon be over. Now, look, kids, I started to tell you that we have a very important sketch to do tonight. Well, hello, Mr. Benny. Well, hello, Dennis. What's that you're eating? A pickle. A pickle? Yeah, cab driver gave it to me and changed. Oh, well, how? How come you took a cab from home? Oh, I didn't come from home. I came from the airport. Oh, Dennis, have you been away? Oh, no. A friend of mine is learning to fly and when he got through with his lesson, I put on a parachute and he took me for a ride. Dennis, your friend is just learning to fly and you went for a ride with him? Uh-huh. Weren't you afraid? Afraid of what? We were riding in his car. Now, wait a minute. Look, kid, if you were riding in a car, why did you wear a parachute? In case he went up on a grease rack. Well, I asked a question, he gave me an answer and it wasn't bad for this late in the season. Imagine going up on a grease rack.   What?  Dennis. Kiss me, Liv. Well, of all the... That kid gets sillier every program by the time we go off the air. Mary! Mary! Mary! Mary, why'd you do that to Dennis? He asked for a kiss, so I gave it to him. And it wasn't bad for this late in the season. All right, now look, Dennis, we've got a very important sketch to do tonight. So sing your song now. I'm a nervous wreck, but I'll try. Okay. Life of Dennis Day called Mary, sung by Dennis Day. And very good, Dennis. And now, ladies and gentlemen, tonight for our feature attraction, our own original story based on those two great fight pictures, the champion and the setup. In this thrilling story of the squared circle, I'm going to play the part of... Uh-oh. What's the matter, Jack? The scripts. Mary, would you go to my dressing room and see if Rochester got the scripts for the play? Okay, I'll be right back. I want to know if the scripts are ready. Yes, here they are. I was just reading them. Thanks for Mr. Benny to be a prize fighter. After all, he does have a nice physique.  I undress him. It's like eating an artichoke. You keep taking things... Cooper did that. We have our own system. Would you like to see how it works? Yes. Okay. I'll take some numbers from this telephone book. I'll start with this one. Act Me Radio Survey is your favorite comedian. Now, kids, when we do this play, I want everybody to... I'll get it. Act Me Radio Survey? Yes, he is. Yes, I listen to him all the time. And now, kids, let me stop looking at him. Truman voted for himself, too. Now, kids, you've all got your scripts, so let's get started with the play. Jack, what about the sportsman quartet? Aren't they going to do a number? They did that while you were out. Oh, gee whiz. What's the matter? Well, you said it was very clever and you wanted me to hear it. Well, Mary, we've already done it, but I'll tell you what it was about. You see, next Sunday is our last broadcast of the season, and the quartet is going to spend the summer making personal appearances in Honolulu. So I asked Don what kind of songs are they going to do over there? And Don said... The boys are going to do songs like Aloha, Sweet Lelani, and Hawaiian Warchant. Then I said, Don, I don't know how Hawaiian Warchant goes. And then Don said... I'll have the boys do it for you now. So I said, would you Don? And Don said... Sure, Jack. Take it, fellas! And when Don said... Take it, fellas. The quartet sang... Awe! Ta! Ahu! Awe! Yeah, yeah. Ta! Wa! Ata! Wa! A lucky strike! A huwele, a pelicola, one-way line! Pu! A dupe, a blue one, firm and fully packed! Ta! A wana, easy on the draw! Ta! Wa! Ata! Ata! A la-sam! A huwele, a pelicola, and a tee! Pu!  Wee! Ya, ya, ya, ya! Smoke a lucky strike! Our first choice! A huwele, a huwele! O-S-M-F-T! Quality of product is essential To continuing success! Luckies are made of the fine Of that light tobacco we confess! L-S-L-S-L-S-L-S-L-S-L-S-L-S-L-S! That's the only cigarette That you can sell to me! L-S-L-S-L-S-L-S-L-S-L-S-L-S-L-S-L-S! Lucky strike! Oh, L-S-L-S-L-S-L-S-L-S! Lucky strike! They never failed! For this late in the season. You said it. And now for our play. Let's go down. Ladies and gentlemen, For our feature attraction tonight, We present a thrilling, dramatic story Of the prize ring, entitled The Champion Set Up! Curtain Music! We've been in Los Angeles in a few days. I hear it's a great place. Look out, here comes a car. You boys want to lift? Bit of the back seat, boy. Hey, that's a beautiful car. What kind is it? It's a Cadillac. I thought it was a Buick. Look at all those holes on the side. We got those in an argument With a sheriff in El Paso. Ah. How far you boys gone? All the way to Los Angeles. Los Angeles, eh? I got an aunt who lives in a suburb of Los Angeles. Glendale? No, Tahatchopee. By the way, Miss, Your boyfriend doesn't seem very talkative. He talks with his fists. He's slugger brown, The middleweight champ of the world. Yeah. We can only take you boys as far as Omaha. Slugger's fighting there tonight. Yeah. You really slugger brown? Yeah. And you're the middleweight champ? Yeah. You're fighting tonight in Omaha? Yeah. And this is the title fight? Yeah. 36 years later, we arrive in Los Angeles, And I want to see the foremost fight manager in town. With my chest, I'm said. That reminds me, I'm having spare ribs for dinner. Don't be funny, Mr. O'Brien.  Do you hear? A champion. Now, wait a minute, son. Fighting is a tough game. I used to be a fighter myself, And I'll never forget my last bout. It was with Killer Nelson. I tried to slug it out with him for the first three rounds, And then I decided I'd better stay away from him, So I got on my bicycle. But he finally got me. What happened? My trunks got caught in the chain. And you didn't swin the fight. Send three. Now look, Mr. O'Brien, I want to be a fighter. Will you handle me? All right, kid. I'll be your manager. Go over to the gym and let my trainer, Punchy McNeil, get you in condition. Bubbles and I went over to the... Excuse me, Mr. But I'm looking for Punchy McNeil. Yeah, that's me. Well, I'm Midge Benny. I'm pleased to know you. Look, Punchy, I'm trying to be a fighter. Mr. O'Brien wants you to handle me. Okay, but you ought to think it over. Fighting is a tough racket. Yeah, I should know Because I used to be a fighter myself. First fight back in 1932. Gosh. Yeah, I spent 12 years in the ring. 12 years? Yeah, but I finally came, too, Got up and went home. Well, look, Punchy, I want to... Hey, wait a minute. I didn't finish my story. Oh, there's more? Yeah. What? Oh, well, tell me, Punchy. Were you always a fighter? Oh, no. I used to be a musician With Guy Lombardo's band. Go on. You were never with Lombardo. Oh, yes. Yes. Yes, I was. A little flat on that last... Come on, Midge. Let's start training. Two weeks later, I won my first fight. A week later, my second and my third. Well, Midge, how you doing? Hello, baby. How's about a date tonight After I knock out the champ? I've got news for you, Midge. You're not knocking out anybody. You're throwing the fight. Are you kidding? You don't believe me. Here's your manager. Ask him.  Would I fight for two years And tank sounds for this? Would I spend two years Getting my brains knocked out Just so I could take a dive? Would I work my way up To the title bar Just to throw the fight? Would I? Would I? Why don't you turn the page And find out? The men are in the center Of the ring Receiving their instructions They go back to their corners Waiting for the bell And there it is, round one. Slugger comes out of his corner And starts mixing furiously. Midge meets him Like a wildcat with a right And a left And now for a few words From our sponsor. Look sharp, Feel sharp, Be sharp.  That was an exciting round. Midge's eye is tightly closed. Now we're waiting for the bell For the second round. There's the bell.  They're still circling each other. We circle each other three times. Hey, bud. Fool me? Yeah. Come here a minute. What is it? What round are you going to take a dive in? The fifth. Uh-uh. Make it the third. The third why? My feet are killing me. I'm in here to win, so start mixing it. Well, okay. It's your nose. Oh! Cross and Midge. Benny is down. Yes, I was down. The referee is counting over him. Yes, the referee was counting over him. The count is up to five. Yes. Midge is rolling over on his back. Yes.  Why don't I shut up? Look out. Here comes a car. Hey, you boys want to lift? Oh, no. We're not going through that again. In a cigarette, it's the tobacco that counts, and lucky strike means fine tobacco. Yes, it takes fine tobacco to make a fine smoke, and in each and every lucky strike, in every pack, in every carton, there's fine light, naturally mild tobacco. Tobacco that makes lucky strike a truly finer cigarette. No doubt about it. LSMFT. LSMFT. Lucky strike means fine tobacco.  No wonder a recent survey reveals that more independent tobacco experts, men who spend their lives buying, selling, and handling tobacco, smoke a lucky strike regularly than the next two leading brands combined. So, next time you're up at the cigarette counter, remember, there is no finer cigarette than lucky strike. Yes, for a finer smoke, smoke a finer cigarette. Lucky strike, buy a carton today. Ladies and gentlemen, we'll be with you again next Sunday night at the same time, one week. I'll get it. Hello? Mr. Benny. Speaking. I am the president of the Pasadena Pickle Factory, and I want to thank you for saving me 200 gallons of vinegar. I saved you 200 gallons of vinegar? Yeah. Thank you for your program, son. He had our cucumbers next to the radio, and they all turned sour. Well, good. Good. No, but it ain't bad for this late in the season. Goodbye. Goodbye. In the life of Dennis Day. Stay tuned for the Amos and Andy Shaw which follows immediately. This is CBS, the Columbia Broadcasting System.


Good afternoon. So as Rosalie said, I am the managing director of Impact Hub in San Francisco and Berkeley. And this is my third year of introducing Impact Hub at SoCAP. Every year this crowd seems to get bigger, which is a very exciting thing. And I guess I would start with, you know, as I look out at this sea of people that are in here, I know they are people that know that things can be better. They are people that know that business can do more and that their actions can make it happen. You guys come year after year because there's a sense of community here. There's a sense of connection here. And most importantly, it's an opportunity to celebrate the work that you're all doing. And if you're not celebrating, I don't think you're so capping, right? I'm sorry. For the last two years, I've mentioned your opportunity to stay connected to this community and keep celebrating all year long at the Impact Hub.  The Impact Hub is now you guys. The global network of entrepreneurs, activists, corporates, artists, freelancers, designers, and investors has grown to 10,000 members, over 50 spaces, cities around the world on all six continents. And just to kind of bring it into perspective, we'll start here in the Bay. Next week, Berkeley is going to celebrate its five-year anniversary of being the first hub in the United States. Over the last year, San Francisco, which is nearly full 20,000 square feet, has recently become the home of the Google Impact Challenge winners. And if you haven't seen them, I'll explain that a bit later. And Impact Hub Oakland came online in February, revitalizing, essentially overnight, the activist spirit of our network. New York, Philly, and D.C. have all opened in the last couple of months and drawn in those local communities. And we've gone, since I started doing this, from four to 14 Impact Hubs in North America. That's over three years. But it's not just here, it's globally. As you can imagine, there's some difficult conversations in some of these cities. In Odessa and Moscow, they're bridging some very complex conversations. On the ground in Athens, they're engaging youth and supporting the entrepreneurs and fighting mass unemployment in that city. In Caracas, they're supporting the massive social unrest that's happening down there. And in Tel Aviv, they're working towards one of the original concepts of the Impact Hub, a peace hub where you can actually bring people together, the Israelis and the Palestinians, to discuss the issues. Thanks. You're everywhere these days. You're working your nights. You're working on the weekends. And you continue to build this movement. You continue to build these enterprises. And you continue to build the campaigns. And you consistently seem to want more, which is why I think these Impact Hubs keep growing. And I'm here to kind of introduce you to what you can do while you're at Socap for the next couple of days. Right across the water there, you can come to the Impact Hub at Socap. We have 20 founders in from around the world to talk to you about what it means to have an Impact Hub in your local reality. You can also bring your discussions to that space and actually take them offline and hold them in the space that we've created for you. And it wasn't just us that created it. We partnered a couple of years ago with Herman Miller, with their Century of Design Expertise and Collaborative Space Knowledge, has helped us not only outfit the spaces across the United States, but they're also helped us design the space that's over there. As I mentioned previously, Google has partnered with us recently with their Impact Challenge and their Lounge Space showcases the great projects and Impact Hub members that have won this year in the Bay Area. The Make Impact Station, which is also to be found in the Impact Hub, provides a prototype space where you can witness some of the exciting innovations being built for the developing world in makerspaces locally like Tech Shop and Gearbox. And this is actually brought to you by the Lemelson Foundation. The Vodafone Mobile Innovation Station, which you can also find inside, is for mobile entrepreneurs changing the world. And of course, in the back of the Impact Hub space is Socent Central, where you can quickly learn more about and meet, if you want to, the entrepreneurs that are sponsored this year at Socap. And there's one of the requests that I would have from all of you. If you haven't yet, use StartGrid. You have a connection or you have an insight to these businesses that are out there, to these entrepreneurs that are there, that can really help them progress in their work. And so take a moment and please share your knowledge. You are the global community of Impact Hub makers. We've built the Impact Hub at Socap to connect you at a local level. And if you come over and find us, we would be more than happy to talk to you more about that. So I will see you at the Impact Hub. Thank you.


Thank you, Kevin, for this warm welcome. It's always a pleasure to have the chance to see you again. Thank you, Suzanne, for your welcome here at McGill. It's always a pleasure to be back at my old university. Before we start, I would like to take a moment to send our thoughts and prayers to London, where an attack took place earlier today. As always, Canadians stand with our British friends during these difficult times. Hello everyone. As you may have noticed, we are having a great visit today. I want to thank Mike Schroepfer and Jan Le Koon and the whole Facebook team for making this trip. It's always a pleasure to welcome folks to Canada, to my hometown. You will also be able to greet my colleague, Kirsty Duncan, the Minister of Science, as well as the Minister of English, and of course, Mayor Coderre. Thank you all for being here. Dear guests, it's a great pleasure to be here this morning to highlight the launch of the Artificial Intelligence Laboratory of Facebook. It's a very good news for the city of Montreal, for Quebec, and for all Canadians. Now, I'm sure many people have told you that in the last couple of years, Montreal has become a real hub for innovation. A city that is quickly becoming not only one of the most attractive places in the world to raise a family, but also a place where entrepreneurs can turn dreams into successful businesses. Now, the people who've told you that in the recent years aren't entirely wrong, but I do want to set the record straight. This trend isn't exactly new. Generations of innovators and thinkers have built Montreal into the city it is today. A city where new ideas are welcomed, where talent thrives, and creativity flourishes. From the gaming industry to the medical field, from aerospace to entertainment, there are countless examples of leaders and thinkers who drew inspiration from this vibrant community. In many respects, creativity is the engine of our prosperity, not only in Montreal, but across Canada. So it should come as no surprise that more tech giants like Facebook are choosing our cities as their home away from home. With a strong research community and well-educated first workforce, Canada is the right place to shape the future. A future where things like artificial intelligence and deep learning help create jobs, improve our quality of life, and generate new opportunities for the middle class and those working hard to join it. And as much as AI is about the future, it's already shaping the world we live in today. From funny filters on social media to systems that can identify the most deadly forms of skin cancer, AI is already part of our lives, even if we don't realize it. That's just how broad its applications can be. For Facebook, AI is an invaluable tool to deliver on its mission to build stronger communities. Take the translation feature, for example, with the click of a button, students from Toronto to Tokyo can now connect and exchange ideas in ways that my classmates and I couldn't even have imagined 25 years ago. Similar technology can also be used to address some of the concerns we all share when it comes to the online community. I'm talking about things like a more effective detection of the PURIEL codes and filters that help make social media more secure for our children. As a father of three children who will probably become users of Facebook in the coming years, it's very important for me. Of course, the field of AI is just the beginning and this avant-garde technology is even more promising. Canada is already in charge of this field. Our scientists, our university centers and our students have been among the first to recognize the immense potential of this revolutionary science. In this room, we only count several pioneers of deep artificial intelligence or deep learning. And when giants of the industry like Facebook decide to settle in our cities, their presence shows not only the world-class talent of the people at home, but of our enormous potential for growth. In other words, it's a vote of confidence for Canada and, above all, for Canadians. And I won't hide from you that our government doesn't play back. After all, artificial intelligence brings together innovation and science, creating good jobs for the middle class and making the economy grow. But we also have a role to play as a government to see whether our workers are willing to take care of their jobs to ensure that our students are ready to seize the opportunities that will come out of these technological advances. That's why we have put the focus on the training of skills and innovation in our last budget. That's why we have decided to invest in our greatest resource, Canadians themselves. Through the country, our government makes targeted and judicial investments, investments that help Canadians of the middle class to build a better future for them and their families. We support the creation of new learning stages to allow young people to acquire experience in the middle of work. We have set up the Canadian Programme des Prés et Bourses pour étudiants to make secondary post-secondary studies more affordable, a program that is now accessible to parents who want to return to studies. These measures are all part of our ambitious but pragmatic plan to help prepare all Canadians, recent graduates, and experienced workers for the good jobs of the new economy. An economy where innovation is experienced by all of our citizens as a plus, not just talked about by some of us. An economy that works for everyone, not just the wealthiest 1%. That's why I know that Facebook will be such a valuable addition to the Canadian ecosystem. Because like Canada, Facebook is all about community and diversity. It's about bringing people together whether they're an ocean apart or just sitting at opposite ends of the couch. I'm not speaking from experience here, that's what I'm told some people do. It's about recognizing that we can achieve more together than we ever could on our own. And it's about finding strength in our differences. That's a vision of the world we can all believe in and get behind. So thank you for choosing Canada. We're so very proud to be a part of this exciting new chapter in Facebook's future in all of our futures. Thank you very much.


Fairfield's MFA has six concentrations, poetry, fiction, creative nonfiction, script writing, as well as two new concentrations, publishing and editing and spiritual writing. Having all of our classes, having the dorms and facilities on Anders Island off Mystic Connecticut allows us to feel that we're part of a single, united community. The setting where this program occurs is pretty extraordinary. I mean, just as a place to go twice a year and look at it, Long Island sound in the winter and the summer, it's pretty special. In the summer we often meet outside. It's a lot different from sitting in a cinder block classroom somewhere. Most of my best teaching has been in this setting. And a lot of the reason why is the closeness of the community fosters a different kind of teacher-student relationship than I've ever had. There's a real close friendship as well that develops between student and teacher. I was looking to develop myself as an artist. I wanted to make sure that I had the proper growth in an area that had always been a hobbyist. What you learn in the residencies then gives you a great deal of insight into the kind of instructor you want to work with. And you have access to an amazing array of professional writers who can really meet your needs on an individual basis. People who teach here are pros. They have been writing typically for a while and even our younger faculty have done a couple books. Everybody who teaches here has a sense, I think, of teaching and writing both as important vocations.  One of the things that has really advanced my own art is the conversations that I have with my colleagues. The other faculty members and reading their work has been a tremendous joy. One of the things that we do in the program is to emphasize not only the theory of publishing and writing, but also the ability for students to get published. In the past year alone, ten of our students have gotten their books published as well as hundreds of essays, articles, and poetry. In my thesis semester, I worked tirelessly with my mentor. Putting the book together was quite an effort and that was something that I did as part of the program. We provided the opportunity for those students who wanted to go into college teaching to give them a chance to actually teach college composition classes. I taught in theater. I had taught at the high school level. I've worked with special needs populations. I'd never really had the opportunity to take my passion for writing and teach that at the college level. This program offering the postgraduate pedagogy option has really been a huge boost for me. I started the program because I felt as a writer, the best way to train writers is to do one-on-one mentor-driven training, which is what our MFA program does. Students spend five months working with a particular mentor working on poetry or fiction or memoir writing. That one-on-one training is very similar to the kind of training that a writer would get with a publisher or an editor or an agent.  And it teaches you how to be a writer and how to make a writing life for yourself.