Hello and welcome to Computational Thinking for Designers, I am Tadi Akopia and welcome to DevCon 21 presentations. A little bit about me. I am a design technologist and developer with background architecture. Over the years, I've had experience in architecture, engineering, construction, building information modeling, virtual design and construction and connecting a lot of data workflows to one another. And also using my knowledge of coding and computational design for creating courses, being a speaker in events and just trying to get the community out there to learn more about the practice of using visual technology in building design and construction. A little bit about my team. We are HMC Architects Digital Practice. We're kind of like the advocates and support for the user groups in our company to encourage them to use better data analytic tools, process automation and integrate software workflows as well as training them. Which is a big topic of today's how you would get people more comfortable with these kinds of visual solutions. The premise here is at HMC we want to get a lot of our designers and architects comfortable with the idea of using code, low code and some basic tools in coding to work on projects and we want to get them used to it without them feeling intimidated since a lot of them have zero coding experience. And we thought that one way of doing that would be using computational thinking to create a baseline of making them understand how the logic of code can work in projects. So what is our audience that we have to train for? What are they comfortable with? What do they like to teach? And what exposure do we have to all of this? Well, as you can see in the pretty pictures on the right here, they're very visually oriented people. The starting point is that most of them are architects and most of them like to draw everything they see. They're very technically oriented in that regard but at the same time they need to be able to see what they're doing. And they produce tons and tons of drawings. Of course these days it's all computers and 3D models. But when it comes to actual coding with text and packages and a lot of deployment and good stuff, they're not very, very few of them, a very, very, very small percentage of architects who know any of this stuff. So how do we introduce technical coding in an intuitive way to them so they can use the new tools out there? We want to bridge the gap of coding for creative designers and make them feel comfortable. Otherwise they might think it's too technical or abstract or intimidating or make them feel anxious to even try because it's out of their comfort zone. So one way to think about that is patterns. There's a architect named Christopher Alexander. He wrote the book on design patterns, which was originally meant for building architecture but got adopted by software and computer architecture. And so these architecture patterns, design patterns, coding patterns, anti-patterns actually have a nice crossover between architects for buildings and architects for code. So we also want to talk about thinking patterns. And one thinking pattern I mentioned before is computational thinking, which is the thought process for expressing solutions as computational steps or algorithms that could be carried out by computer. So very discrete steps, make it so that it's rigorous and easy to lay out everything. And here are the key points in computational thinking, using abstractions and pattern recognition to represent the problem in different ways. Logically organizing and analyzing data, breaking the problem down to smaller parts, which is very critical when it comes to trying to assess a problem. Some people just kind of take it for granted. They already know what they need to do with the problem without addressing the might need steps. Approaching the problem using programmatic thinking techniques such as iteration, simple representation and logical operations. We're formulating the problem into order steps, another critical step. And identifying, analyzing and implementing solutions with the goal of making more efficient combination of these solutions based on recursion. And trying to take a specific problem and generalizing it to a variety of problems so it can be used. So this is the kind of approach that you can use for anything, whether it's designing, coding, cooking food. The thinking itself can be applied anywhere. So we want to give them a framework that can take the kind of vague, almost fuzzy process of creating buildings and make it so they can feel comfortable doing coding with computational design. And the process is the same. It can be used to any field in this case. You start with what you don't have, you modify it, you create, you find recursion and you update it. So they want to give me this cycle of thinking, this pattern of thinking. And then there's just sequences, problem solving methods, abstract concepts from computational thinking can lend itself very well to solving kind of problems we have in any field. So it's all about getting those ordered steps in a row. One gap we do have to address though is the people we're trying to train at HMC are maybe not familiar with the essentials like inputs and outputs, data types, data flow, recursion. So we have to prepare how to understand these problems down steps and the fundamentals of processing that data must be handled first. Of course, everybody wants to do cool stuff like in this example. This is what architects really want to do. They want to get straight to the point and start designing awesome buildings that can be quickly developed. This is like a proposal, like a hundred story glass tower that's modified designers kind of looking around seeing what they got here. Architects love this kind of stuff. They love trying to take a big idea they have and make it into a reality and then kind of refining it. So they want something visual something they can enjoy. But to get there they have to go through all these steps of understanding the tools and disposal. And on left is the your typical kind of Python code you would see just defining in this case in geometry on the right is visual scripting and that's also Python. It's called pyflow. Now there's a link at the bottom here if you're interested in trying it out. Basically it takes the Python coding languages and it just makes it interactive so they can use these nodes to have things like the integers, the rays, going to the branches. And people can feel like they can play around with it and move around. It's a good way to kind of make people who aren't familiar with code, text coding, editing code kind of understand the logical operations involved. By using just your typical IDE script it may not be so obvious what they're doing with until they're very much trained but we're just trying to get them to understand the thinking patterns. A visual scripting medium is actually very useful and that's what a lot of designers actually use and that's what we're trying to get them to use in agency. For architects in general, the two big ones are artist, Revit and rhinoceros, Revit, or sorry rhinoceros, it's a general purpose 3D modeling software. You can model just by anything you want, building, jewelry, cars, you name it. And Revit is a specific purpose building modeling software that has basically an SQL database hooked up to a 3D modeling interface which is parametrically fine and it has a lot of controls and less fluid. And both of these have visual scripting plugins. These are open source projects. And Dynamo is the one for Revit and Grasshopper is the one for rhinoceros. We're trying to get them used to this but in order to use these tools we need to show them how to use the computational thinking steps and how to bridge that gap of really structuring how you think through a design problem. But because we're using software that are already trained on like Revit and rhinoceros, they are already more confident that they can get started because at the end of the day these scripting languages directly relate to the modeling software. They communicate to the API and let you create workflows and tools and buttons that don't come with the software without having to code with X. So here's an example of a Dynamo one for Revit. On the left is the visual scripting and the blue highlighted area can be distilled into this Python text. So while it might seem much more convenient to do in Python, if somebody's not familiar with computer program concepts, CS concepts, Python language, then they might be able to knock it out pretty quick with the visual scripting because they can at least kind of see for themselves where to start with what inputs they need, how to organize the content. It's all in front of them. It gets kind of hairy the longer these things go, but it's easier to read if you're not able to read code that the stuff on the right is going to be gibberish to you. So we want to give them a starting point so that they actually can get to the Python scripting. And this one example here shows you how you can take inputs and make it into a design output. So the input here is showing you we want to make some coordinates for force in a building tower. So the top half shows you the XYZ coordinates we need to use. And the bottom half shows you the inputs for model like concrete floors, number of levels, wall type, curtain wall, glass. We then take those inputs, modify them, the same middle called polycurve by point is basically connecting the dots. And then we multiply the polycurve by the number of levels and we tell the levels we want the floors of a six inch foundation slab. And based on just those inputs in the processing, we can get floors and walls. And that's something concrete and architect can understand floors and walls, they get that. And when you're done, this is what you get. You get the geometry on the left being translated into a model on the right. So they can preview the geometry and get a full build. This is the kind of payoff that a lot of designers out there feel comfortable with. They're like, okay, I get it. I understand that I can create the coordinate system that I can lead to this whole building that can then start documenting without having to, you know, copy paste and modify a ton of stuff at one. You can change it on the fly. You can add more points to your coordinates, things like that. So this is the kind of lead in that makes them feel comfortable to software.  You can do things like check out shapes and click on the different nodes and see what they can do for you. So they can play around with it while still basically working with a type of coding. Same with grasshopper. You can use it to make some nuance adjustments to your model. So you don't have to constantly try to tweak it yourself manually or any designer can feel confident. They can save a ton of time doing things this way. The slider is having to model everything tediously. So this is the kind of thing that makes them feel comfortable with the coding environment. But to get started, we try to, you know, give them a training regiment. They've never seen this kind of stuff or they won't get better at it. With these visual scripting, we try to say, okay, pretend you're baking a cake, like on the pop image there. So what would it take to get a bake a cake? Well, you need the oven. Well, what do you put in the oven? You put in the dough. Well, how do you get the dough? You have to mix it. What do you need to mix it with any ingredients? So we tell them, okay, what is it you're trying to achieve? You're trying to make a building? What do you need to do then? We work backwards. You know what they want, but by using the most discrete steps possible, how can we get there? And so you work backwards to get the inputs and then we have another scenario. We use diagrams to draw it out again saying, okay, if we want a peanut butter and jelly sandwich, you don't need peanut butter and jelly, but else you also need bread. But the bread itself might be a loaf. We have to cut it in half. Each slice of that loaf has to be input into a node with one on peanut butter, one on jelly, and then those two nodes go together to a peanut butter and jelly sandwich. So you start seeing, okay, like if you had to physically do this, you would just start putting things together, but you had to tell a computer how to do this. You have to be very explicit and account for every step. So that's how we try to diagramically explain this to them. And then we just show them how to do the exact same thing with a computer where we're using the visual scripting language again here. And we just say, okay, this time pretend it's coffee that we're working on. We want to get coffee, so we need to have temperature, water, coffee in the cup. The water needs to get heated, so we process the temperature here. And this is all just diagrammatic. We're actually doing anything here. It's just to get them comfortable using the visual scripting medium. So we put the water and the coffee cup together saying pour liquid in the cup. Now we have a cup of coffee. And then we have to figure out how much we want to put in the coffee, 12 ounces. We can't take that for granted. We don't know how big the coffee cup is.  Then once we get used to this thinking process of inputs and discrete steps and analyze, then we can get them to do it with an actual model, which is the same thing. Inputs, division of the surfaces, connecting them again and creating a design output on the right here. So that's how we're training them to get really used to that computational thinking and create a logical workflow so they can move on and do something like this where it's an actual building. If you ever saw one of these really groovy buildings out in the world, it's usually created with software like Rhino and Grasshopper and Revit. And by giving them use to these inputs and outputs and computational thinking and the discrete steps involved, then people can see that they can do it themselves with a few more steps, a little more savvy in this small environment. But they can't really get very far if they don't know how to process things. Some people have an intuitive grasp on it, but the more defined approach you can provide, the easier it will be to get them to where they want to design so they don't have to do much trial and error and get lost in circles. The approach we're getting to teach them is a very fundamental concept of computational thinking in the first place. That can be applied to anything to the thinking of how you can use that workflow to put together any kind of concept into a workflow diagram and then getting into these visual scripting languages so they can get some useful work done that makes them happy to be designing. At HMC, we're trying to bridge into a standard different direction, parametric design, computational design, general design. At this point, it's mostly computational design, but we're going to start from there and really expand from what's possible. And we want to make sure we pay attention to people's learning styles. A lot of people can learn different ways, visual, audio, text, touch, but architects are very visual with a little bit of touchiness, so we're trying to make it feel as comfortable as possible to visually see things and provide the resources necessary to supplement them. And we have a whole training and learning platform. It's in-house with some external tools like Lenten Learning, but through our own portal so that people can get training, structure training, training that's consistent with these kinds of computational thinking paradigms so that they don't, you know, get different kinds of training and it starts feeling like you're learning it 10 different ways from 10 different people and it has to be consistent. And the idea is we would train different people, junior or senior people, people tech savvy, people not so savvy on tech, and just, you know, train them, get them to a database and create an example of what's possible with their skill set. So an example to write this person is very good on Dynamo, Revit, and CAD and maybe a little work on Grasshopper so we can provide the right training. So that's how we take somebody and develop them further. And the goal eventually is to train a lot of the designers who work on the models day-to-day to make some cool concepts in their projects. And this is a real example of an H&C project in the Bay Area that is using environmentally responsive design to create louvers for a facade. And you can see on the top left there we have some energy analysis models showing, you know, the heat map that light gain, the solar gain in the room of this building, this library. And on the bottom you can see all those nodes. Now it's a very sophisticated series of nodes created for this project. In a nutshell, it takes the geometry input, turns it through a bunch of different processes, and it uses a couple of specialty nodes to control for solar exposure.  And then you can use that to set the room. On the top right you can see what's, you know, all these controls and configurations that we've used to figure out what the spaces look like with the different panel types. On the bottom right you see the panel generation showing us giving some examples starting from a very straightforward, you know, filled up panel to different slots so it doesn't look repetitive, but it still does its job by protecting people from the sun. But at the same time being energy efficient. So we use these tools without having to, you know, train people on software like IES or something like that, which is especially software for energy analysis or train them how to code. We can use, you know, visual scripting to get a lot of this done. It does take a little bit of training and practice, but once they get comfortable with the logic of it, the computational thinking of it and the tools, they can do this kind of work to become better architects. They can get more work done the way they want to get it done. They don't feel like the software is trying to tell them what to do. They feel like they have more control and we have better results for our clients because they see what kind of quality work we do for our buildings and it's cool to show us kind of work off and encourage others. So the key concepts in review is coding competition design is more important for the average person these days, including architects. Everybody needs to learn a little bit of computational thinking, a little bit of coding to get ahead in this world and make a difference in what they're trying to do. But you have to make a compatible training style to get people comfortable with the concept. Not everybody is just going to sit down and learn Python or JavaScript or any other language. A lot of people are not comfortable with that. Computational thinking establishes the baseline thinking so that people get comfortable with how you would need to talk to a computer. And you can use resources compatible to trainees, reduce the anxiety and give them examples that are familiar projects to the non-coder like a building, something that they can feel easy enough working with. Create some structured coursework to move them along with hand knowledge. Let them try skills on a project and share the results. Review, upgrade, continue training indefinitely. If you take anything from here, it's make sure people are comfortable with how you train them. Otherwise, nothing you do will get to them. You speak from experience. Here are some resources on computational thinking and design patterns. You should see the visual scripting tools, our digital practice and the visual scripting of Python Dynamo. If you want to see the text and the visual come together, have a link down there for you. And that's it. Thank you so much. If you want to share my context, please reach out to me if you have any questions about anything I talked about today. If you want to chat a little bit or whatever. QR code, GitHub, LinkedIn, e-mail, Twitter, all that jazz. Thanks, guys. Thanks a lot, guys. It was a pleasure speaking at DevCon. It's CZ 2021.


Thabstet presents the Great Gilded Sleeve. Hee hee hee hee. The makers of Thabstet present each week at this time Harold Perry as the Great Gilded Sleeve, written by John Wheaton. We'll hear from the Great Gilded Sleeve in just a moment. But first, are some of the foods you usually serve hard to get these days? Well don't think that means your meals have to be monotonous because there's a plentiful food that gives appetizing variety to menus in a hundred different ways and is mighty easy to use too. I'm talking about Thabstet, the delicious golden cheese food that comes in the familiar round package. It spreads easily to make tasty, nutritious sandwiches. Thabstet also slices neatly to serve with apple pie or fruit. And it's no trick at all to make smooth cheese sauces with Thabstet to pour over hot vegetables, hard-cooked eggs, fish or chicken dishes. Yes, and Thabstet makes smooth, tempting rare bits, light, fluffy souffle. And it's a sure hit, melted on toast in the broiler. By all and all, you could count at least 100 different ways to turn everyday foods into exciting treats with Thabstet. Another thing, Thabstet is easy to digest too and wholesome and nourishing, a favorite with the youngsters. So serve Thabstet often. Ask your grocer for Thabstet tomorrow. You'll recognize it by its distinctive round, flat package. Remember, it's Thabstet. The delicious golden cheese food of a hundred uses. And now, let's join our friend, the great Gildersley, who seems to have been overdoing a bit lately. His legal counsel, Judge Hooker, has persuaded him to drop in on Doc Pettibone for a checkup. And while the judge stands by, the good doctor goes over the great man with a stethoscope. You know, doctor, this is a lot of nonsense. I feel fine. Oh, quiet please, Mr. Gildersley. I want to listen to that heart of yours. We take you now to Gildersley's heart. Take it away, Doc. What is it? Why do you look like that? What is it, Doc? What have you found? Don't tell me you found a heart. You keep out of this, Hooker. This is serious. I like you to listen to this, Judge. Put this stethoscope on him. That's right. Now hold the other end up to his chest. Stand still. It tickles. Well, stand still. There. Now listen. What do you hear? Sort of a rustling noise. Sort of a what? Sounds like a troop of boy scouts coming through the underbrush. Oh, no, no. That's the hair on his chest. You're in the wrong place. Hold it lower. Hold it still. Hold Gildersley still. Oh, cut that out, Hooker. I can't stand the suspense. Doc, Doc, am I, am I going to die? Oh, no, no. Take it easy. Don't spare me, Doc.  I know it. Don't try to fool me. If my time is up, I want you to tell me.  No? No. Did you hear that, Hooker?  Oh, my goodness. I'll do it, Doctor. I'll do anything you say. You name it, and I'll do it. Well, I want you to get some rest. Rest, yeah. Well, I'll take it easy. Above all, don't get excited. Don't get excited. Maybe you ought to go away for a few days. That's what I keep telling him. Go away. Go away. Listen, you'll meddle some old goat. The judge is right. Yeah.  You know, I hadn't been fishing in 20 years. Best thing in the world for the nerves, isn't it, Doc? Nothing like it. Yes, sir. I used to be quite a fly caster in my day. A regular Isaac Walpole. Well, then the place for you is Lake Hecmatac. You can rent a little cabin up there and... Are there any fish? You know that big trout that hangs over the sideboard in my dining room? Yes. Lake Hecmatac. Yes. Say, one of those wouldn't look bad in my den. By George, I'll do it. I'll take Marjorie and Lee Roy and we'll start the first thing in the morning. Come on, Josh. Mr. Gildersleeve, just a minute. Yeah? There's one more thing. What's that, Doc? $5, please. Oh, yeah. $5.  There's a poppy bottle I got. Look at that float. Yeah, good evening, Bertie. Good evening, Mr. Gildersleeve. Something smells mighty good. It smells all right, but it ain't good. Lee Roy, what's going on here?  Just making a little root beer. A little root beer? He's made 14 gallons. Well, that's how much it makes. You can see for yourself, Uncle. It says here on the bottom. This extract is sufficient to make 14 gallons of genuine root beer. Don't you think you're getting into this thing a little deep, Lee Roy? 14 gallons. That's an awful lot of burps. Yeah, and he's used up... He's used up every bottle and cork I got and a wash tub still have food. A wash tub? Oh, you don't understand, Uncle. I'm not going to drink it. I'm going to sell it. Lee Roy, did you ever hear the Pure Food and Drug Act? No. Well, you will. And you're going to hear the riot act if you don't get that stuff out of Bertie's kitchen. Where's Marjorie Bertie? She's out back there. She's been laying in the hammock crying her eyes out. Crying? Say, we'll have to see about this. Nothing but trouble in this house. The doctor's right. I've got to get out of here. You truly, Roy. Come on. You ought to know better than to mess up these things by Marjorie. What's the matter, honey? Nothing. It's Doug. He was supposed to take him to the movies tonight and he's standing up. He is not. I'm standing him up. Huh? Wait a minute. Let me get this thing straight. He stood me up last night, so...  Well, darling, if you're standing him up, what are you crying about? It's Doug who should feel badly. I know. But he doesn't. He's going to take that Helen Gibson out. Well, you told him to take her out. I heard you. Yes, but he's going to do it. That's women's crime. Take my advice. I'll never have anything to do with it. Yes, all right, please. Take it from me. The more you do for him, the less they appreciate it. I know, I know. Read up rough and tell them nothing. That's my method. Take my advice. Leroy, why don't you start a column?  Now, Marjorie, I wouldn't waste any tears on a fellow like Doug. He's nothing but a... Don't you dare say anything against Doug. Stick around, Leroy. I may need you after this. Stick around, Leroy. I may need you after all. Remember, Marjorie, there's better fish than Doug. He's right in Lake Hackmotac. Say, how'd you like to go to Hackmotac for a couple of weeks, huh? We'll rent a little camp and we'll do nothing but lie around the sun all day and fish. What do you say? Fresh! If I wasn't asking you, Leroy, if Marjorie... Well, there's going to be any fishing. There's one thing I'd like to know first. Oh, what's that? Who cleans the fish? Yes, there is that. Leroy, you're getting to be a big boy now. What's the matter with you cleaning the fish, huh? Well, I'll tell you. Funny thing about me and fish, I'm not a squeamish man, but there's one thing I can't stand is cleaning fish. But we haven't caught any fish yet. Wait a minute, I've got it. Birdie! Oh, Birdie! Birdie, how'd you like to go away with us tomorrow for a nice vacation? It's 10.30 and we were going to start at 8 o'clock.  Where's coming, Uncle Mort? Well, then what's holding us up? We're just packing the lunch. For goodness' sake, we just finished breakfast. Now, you'd be the first to holler, Mr. Gilfleave, if it wasn't any lunch. We'll be done soon as we finish these double eggs. I don't know why it is every time we go any place. All the women in the house have to start deviling eggs. Have you got the thermos bottle? Yes. Have you got the steamer rod? Yes, yes. Oh, Uncle Morton, why don't you just leave the packing to us? We can do it much quicker if you'll just let us alone. Well, I'm just trying to help, for heaven's sake. Of course, if I'm not wanted here, far be at ease.   Come on, Lee Roy. Hey, Uncle, can I back the car out? No, you may not. No, I'm not, Uncle Morton. Piggy Banks backs his car out. I can do it earlier. You heard me. I said no. Why not? I've told you before, young man. You're too young. You're much too young to understand about cars. Oh. I'll get off the running board. I'm going to start it up. Have you been pooling with this car, young man? No, sir. But may I make a suggestion? No, you may not. What is it? Why don't you turn on the ignition? Turn on the... Yeah. It's a funny thing. I've been trying to start it that way for years. This never works yet. I'm going to start it up. I'm going to start it up. I've been trying to start it that way for years. This never works yet. Yang Wei. What are you trying to do, Throck Morton? Run over me. No, Judge. But it's a nice idea. That's gratitude. An old friend comes over to say goodbye to you and you try to run him down. Here's a much faster, Miss Gil, please. Oh, Leroy. While you're resting, go get that, will you? I'll open the trunk. One side, please, Judge. Leroy, what's all this in here? That's my root beer. Well, get it out of there. Oh, long. We've got to have room for the baggage. We can't take all this. Well, gee, can't I take some of this? You can take six bottles. That's all we'll have room for. That's all you'll have room for, too. Okay. The idea I've never seen before. Morning, Marjorie. Well, it looks like you had a fine day for a trip. Looks like a scorcher, if you ask me. I'm dying already. Yeah, it is a little hot. It's a lucky thing it's not far to hack with hack. I don't like the looks to that left rear tire there. Oh, I wouldn't worry about that. It's still got a lot of fabric left. It's still got a lot of fabric left. Leroy, come get these bags, will you? Yes, Leroy, while you're resting. It seems like I have to do all the work on you. By the way, it's Rockmorton. I'll be glad to sort of keep an eye on the house for you while you're away. Oh, the house is locked, Judge. I don't think there's anything to keep an eye on, really. You can't tell. A couple of houses have been broken into around here lately, you know. Is that all? I hadn't heard about that. Yes, so if you would like to leave your key with me, I'll be glad to drop around once in a while and see that everything's all right. Well, that's mighty nice of you to judge. Mighty nice of you. Here, there's the front door key. Thank you. Leroy, have you got those bags and back there? Yes, I would. Bertie, suppose you and Leroy are right in the back.  Yeah. Are we all set? Everything in? We've forgotten anything. Let's see. Doors locked, lights out, bags in. Leroy, did you? Yes, boss. Good. Well, we're off. Goodbye, Judge. Bye, Rocky.  If we don't, you'll hear from us. Bye, Marjorie. Leroy. Bye, Judge. Goodbye. Goodbye. Bye. Good old hooker.  He's a sweet old thing, really.  I'm going to miss the sweet old goke. Well, ought to be a nice trip. Hey, Oz, what was that? It sounded like a blowout. I knew it. It's that left rear tire. Brothers! Oh, there goes our trip. Can you beat it? You work hard all year.  You mind your business. You try to take a well-earned making. Oh, I've seen some bad breaks in my time. But I'll be... I'll be more? I mean, I'm a patient man, but good gracious to Betsy. Well, that's life, I guess. Birdie, did you ever change a tire? Don't tell me. Let me guess. The tires were OK. All of them. Leroy, this is no time for joking. I'm not joking. They're OK. Leroy, I distinctly heard something blow. No, they don't. I'll tell you what blew. It was Leroy's root beer. That word blew. I told him he put too much yeast in their stock. Oh, this is going to be one of my bad days. The Elder Sleevel will be with us again in a few seconds. Everybody knows that fresh vegetables are good for you. But do you know the trick that makes practically any vegetable dish a real taste treat? Well, the answer is serve hot vegetables with smooth cheese sauce poured over them. You'll make them even better tasting, even more nutritious, too. It's easy if you use tap set. Delicious golden cheese food that comes in a handy round flat package. All you do is melt tap set. In a double boiler, stir in a little milk and season. Presto, you have a grand smooth cheese sauce, not only for vegetables, but for fish and chicken dishes, macaroni, rare bits, and a number of foods. You'll be surprised how a luscious golden cheese sauce, the kind tap set makes so easily, adds sparkle to everyday dishes. It proves them appetizing variety that just calls for second helping. Yes, and tap set spreads so smoothly, slices so neatly, you'll find a hundred delightful ways to serve tap set, both by itself and to add cheese goodness to other foods. It pays to serve tap set often because it's so nourishing. A fine energy food, rich in milk protein, and it gives you vitamins A as well as the milk, minerals, calcium, and phosphorus. So ask your grocer for a tap set tomorrow. Remember, tap set, the delicious golden cheese food of a hundred uses. Let's get back to the great yield of sleep. It seems that left rear tire held out, whereas the morning mist rolled across Lake Hackmotack. We find the mighty angler seated in the stern of a little rowboat with his niece in the bow and his nephew at the oars. Steady Leroy, steady as she goes. Leroy, that would ride in my lap. I can't help it, it's these darn oars. This is about far enough, I think, Leroy. Yeah, let her coast. That's it. Now hand me that rod. Rod, Marge. Oh, here, Uncle, you want a worm? Forget the worms.  Oh, and how do you catch the fish? Yeah, you'll see. Young man, you're about to be initiated into the gentle art of fly casting. You see that little doohickey there that covers the hook? You mean that tassel? It's not a tassel, young man. That's the fly. You see, it's very delicate. The finest ones are so delicate, they're made of hummingbird feathers. Do the fairies make a Uncle Morse?  There's a lot of angles of this, young man, so watch carefully and don't be so smart. I'm watching. This is how your crew angler attempts the finny tribe. It's all done with a wrist, see? And the secret is in getting the ribbon.  You see? One, two, one, two, one, two, one, two, one. It's all done with a wrist, you see? One. You've been saying that for three days now, won't you? When did you catch the fish? The fish are secondary, young man. The sport is the thing. One, two, one, two, one, two, one, two, one, two, one. Really, Uncle Morse? Pass me the worms. Tell me something, Uncle Morse. What makes you think there are any fish in this lake? I've seen them. Where? In Judge Hooker's dining room. Now, what are we doing here? Judge Hooker has a stumped crowd over his sideboard that long. And by George, I'm not leaving here till I catch something. Can you beat it? Five days, not a single bite. Not even from a mosquito. Not one. Remember, Uncle Morse, the sport is the thing. The fish are secondary. Give me those worms. I've tried dry flies, wet flies. I've tried casting, trolling. If this doesn't work, sir, help me. I'll go and after them with a club. Hey, Uncle, look, look down there. What? Where? Down on the weeds there. See him?  Be quiet, everybody. Be very quiet now. Shh. If I can just lower the hook down there without scaring him. Easy. If you don't move. What's that, a mosquito? It's an airplane. Well, keep it quiet. Shh. Remember now, fish are jittery. Easy now. Nice fishy.  That plane's coming this way, Uncle. Go away, plane. He's diving. It's a power dive.   Look out, everybody. Duck! Young man, you come out of there. This is no time to guard you. That's right, Marjor. You grab hold of the boat. Oh. Yes. Leo, are you grab hold of me? Yeah. I'll grab. Hey, look what I grabbed. The fish. I got the little son of a gun. I got him bare-handed. Oh, he's slippery.  Yes. I had to get away from that lake where I had razz material. What is it? Well, with any luck, we ought to be home by dark. But be sure and take good care of that fish back there. Oh, don't you worry about that fish. He can take care of himself. That's the powerfulest fish I ever smelled. Well. Some fish are gameier than others. You sort of have to expect that of a trout. That ain't no trout, Mr. Gill, please. What do you mean? That trout's a clown. Don't you talk that way about my trout? Well, whatever it is, it's getting higher than a goat. Why, Marjorie, I don't smell anything. Oh, of course you don't, with those cigars. If you don't stop smoking those things, this fish is going to be kippered before you get them home. So are we. No fooling, Mr. Gill, please. Don't you think we ought to stop somewhere and give him a decent burial? Nothing doing. That fish is all I got to show for a misspent week.  Hey, that's an idea. Hang him on the fishing rod and stick him out back. Here, I'll do it. Now, don't let him get away. What are you expecting to do? If I'm his way back to Lake Hatt-McCat? Well, what's that guy talking about? All right, brother, come on. Are you going to pass? What do you want? Got a fish you think? No, don't. I think the man had never seen a fish before. Miss Gill, please. What is it, Bernie? I ain't sure, Mr. Gill, please, but it looks like there's some seagulls following us. Oh, fine. Yes, that's what this is. They're after your fish, please. Pull in your line, Leroy. Pull in your line. Play him, boy. Play him. I have more trouble with birds. Oh! Go away, birds. Go away. Let's get this stuff out of here before it gets any darker. Don't forget that fish. If we could. I got the lunch bag, and who's going to carry all these bags? Thanks. Leroy, while you're resting, old man. Yeah. Watch your step, Marjorie. It's pretty dark. You? Something's graphing. Leroy, what did I tell you about those croquet wickets?  Gosh, feel that grass. I bet it's grown eight inches since we've been away. Leroy, first thing tomorrow morning. I know. While I'm resting. Yes. Hey, somebody left a light on upstairs. Where? In my bathroom. Birdie, has that been burning all the time we've been away? Wasn't me, Miss Guilty. Well, who was it then? I don't know, Miss Guilty, but it's in your bathroom. Yes, well, that's right. Well, come on. Bring the bags, folks. Oh, it's stuffy in this house. Don't forget to put that fish in the icebox, Birdie. The icebox isn't built. They could hold that fish. Oh, Miss Guilty. Miss Guilty. Somebody's been in the kitchen. What do you mean? Tramps, the jifties, or somebody. How do you know, Birdie? There's dirt and dishes all over the place. Miss Guilty, you don't think maybe it's been burglars? Yes, burglars. Well, we'll have to see about this, Birdie. Miss Marjorie, you and me better go count that silver. What is it? It's a shower, Uncle Mark. Shower? You didn't go up and leave it running. Certainly not. I always turn that little... There's somebody in it. There's somebody up there right now. How do you like that for a nurse? It takes a shower before he robs the joint. It's no use, Leroy. The wires are cut. How do you know? They always are. It's the first thing robbers do. But you can't wait for the police, Uncle Mark. You've got to go up there and get him. You're right, Marjorie. Who, me? I'll guard the back stairs, Miss Guilty. And if you come down that way, I'll party scalp with this meat shopper. Yes. Yes. You do that, Birdie, but do it quietly.  Yes. Wait a minute. Maybe we'd better think this over a little first. A lot of angles to this. Leroy, you stand by. Okay, Uncle. I've got my baseball back. Marjorie, you sneak out and run for the cops. Well, here I go. If nobody stops me. Be careful, Uncle Mark. Yeah, yeah. How? It quickly starts pushing, Leroy. I wish it wasn't so dark. I don't dare turn on the light. I'm a little vulnerable on the light. Well, here I go. To those squeaky stairs. It's probably these $6 shoes. I mustn't get excited. Doctor said I mustn't get excited. I'll bet he'd get excited, though. Well, now that I'm here, I want... Uh-oh. I can see you moving around behind the shower curtain. What do I do now? Remember what the coach used to say, Guilty? Get him below the knees, boy. The wish I'd never broken training. Come on, Guilty. Give him what you gave, Harvard. 29, 33, 76.  Let go of it! Let go of it! Now, please! Please! Kill this, please! Hooker, what are you doing here? Well, what does it look like I'm doing? I'm taking your shower. Any objections? Yes. What are you doing in my house? Well, Peter's working on mine, so I thought I'd just move over here for a few days. I didn't think you'd mind. Matter of fact, I didn't expect you back so soon. I'll bet you didn't. Hooker, you knew you were going to move in here the minute you got me out of town. That's why you suggested that trip. Morton, I'm hurt that you'd say a thing like that. Come clean, Hooker. You just had a bath. You knew it all the time. I had to have the house painted. You know that. It was a disgrace. Yeah. I can't stand the smell of paint. It gives me colic. You wouldn't want me to go... No, I wouldn't want you to have colic. Anything I have is your judgment. You know that. Move in any time. Make yourself at home. Wreck the joint. There's one little thing, Judgeee. About Lake Hackma Tag. Lovely spot. Yes, lovely. But there's no cross there. You know it. Now, there you're wrong, Crockmorton. You just didn't try the right place. Don't tell me I combed that lake from one end to the other. Well, no wonder. You should have tried the place where I got mine. Where was that? At the Hackma Tag souvenir shop. Well, Judge, let's let bygones be bygones, huh? Let's be friends. You mean that, Crockmorton? You mean you forgive me? Certainly, I mean it. There's my hand on it. Gildy, my friend, I take back everything I've ever said about you. Uh, seems to me this calls for a little drink, huh, Judge? Birdie, bring the judge a bottle of that special root beer. You may think you've tasted root beer, Judge, but you're gonna get an old bang out of this. Good night. On this program of composes conducted by Billy Mills, this is Dan Alexander speaking for the Makers of Pat Steps and inviting you to tune in again next week at the same time for the further adventures of the great Gilders League.


Alrighty, good morning everybody, have a clicker, thank you. So I'm Dries, I'm from Belgium, and I'm here to talk a little bit about Drupal today. So what I wanted to talk about today is winning the hearts and minds. As many of you know, or as many of you are about to find out, Drupal is really built on passion. Passion from users, passion from developers, and I would like to see us build even more passion by winning the hearts and minds of people, and I think we can do so through innovation. So before we start, I wanted to give you a few quick examples of really cool innovations. So here is one, which is the fish carrier, some more, soundproof underwear, obviously a really great innovation. We have the Beard scarf, the good news is they also have a kids version, so you can go as a family. There's the cat duster, not everybody likes cats, some people have babies, so there's the baby duster, there's the noodle cooler, and then my favorite is the noodle-eater hair guard. But the real question, of course, is what kind of products win the hearts and minds of people? And so let's look at a few companies or products which were once perceived as being innovative and today no longer are, and you see some of the examples up on the screen, like Kodak or Palm or Nokia and some other technologies. And then on the flip side, there is products like this which we all relate to probably as being very innovative companies like Apple and Google, Facebook, Twitter, and so forth. So the real question is what's the difference between these two categories of companies or products? And the answer is not a propeller powered lazy boy, but continuous innovation. That's what separates the first or the last companies from the first companies. So let's talk a little bit more about that. So if you look at the typical lifecycle of a product, it typically has four phases, the development phase, it has the growth phase, the maturity phase, and then sort of the decline phase and adoption increases, install base increases over time until you reach the decline phase. So what that means for Drupal, for example, I would say Drupal 7 right now is kind of, has just reached the maturity phase. Drupal 7 grew very fast. It grew about 2.5 times as fast as Drupal 6 in terms of adoption, so the way we measured that, by the way, is we looked at how fast we got to 100,000 installations measured by data though. And it took, I don't remember the exact length, but it took Drupal 7 2.5 times less time to get to 100,000 installations. Also, Drupal 7, the number of Drupal 7 installations has now surpassed the number of Drupal 6 installations. So there's more Drupal 7 sites out there. So we could probably put Drupal 6 there. It's actually sort of declining as people migrate or upgrade from 6 to 7. That's what happening. And then obviously Drupal 5 is on its way out. It's obviously still maintained, but fewer and fewer people are using it. And then of course, as most of you know, I think we're working on Drupal 8 right now and it's very much in the development phase. And we'll talk a little bit about that as well. So let's go back to innovation though. So how do these companies innovate? So they innovate because they sort of extend those product life cycles. In the case of Apple, they do so by launching new products like the iPhone, the iPad, and also the iPods. And so where these other companies failed is that they stopped innovating. You know, and a great example is Kodak. They actually owned the analog photography market and they invented, I don't know how many people notice, but they invented digital photography, right? Back in 1975, I think. But they've never been able to really capitalize on that. They weren't bold enough to change and to disrupt their own analog photography business. So reinvent themselves and to innovate. And so they died. So there's a big lesson there and a good reminder for us to continue to embrace big changes. And I'll talk about of these big changes in this presentation. All right, so in terms of Drupal, obviously we don't have multiple product lines like the company like Apple does. We only have one product which is Drupal. So the way we innovate is by making each version of Drupal better than the previous version and adding more cool features to it. So that looks roughly like this. So if that's the way we innovate, what does that mean for Drupal? So let's have a look at the past and the current, I guess, to figure out what we need to do going forward. So I wanted to start here with a little bit of Drupal self-reflection. I wanna talk about Drupal's strengths. I wanna talk a little bit about our weaknesses, which is maybe unusual for people that go to traditional technology conferences. But I do like to talk about our weaknesses so we can learn from them. I would like to talk a little bit about the opportunities that we have and finally some of the threats. But before I do so, I wanted to give the floor to a number of people. So I went out and interviewed a number of people, people that use Drupal in a big way and that are pushing the limitations of the platform really. And I've asked them to comment on these four things and came back with a little video which I'll show you now. We had tried a lot of the enterprise content management systems out there. A lot of them were sort of legacy systems that were modified to work with the web. We narrowed our search down first open source and then secondly we looked at communities around the various open source platforms. And it didn't take us a long time until we came to Drupal and saw that it was a very vibrant, large community that was very active in developing Drupal and pushing it into the future. Obviously it's the community. I went to my first Drupal Con in May of 2010 and was just blown away by the ecosystem and the energy. So having a very flexible, robust platform comes from having a vibrant community. The opportunity in the marketplace is huge. I don't think that there has ever been a time where the commercial products in the open source products were either so evenly matched or if anything the open source products probably have a richer feature set. We made the pitch that we're gonna choose this new platform. We're gonna deliver something on the web within one month which for a big company that's typically a very difficult thing to do. We had our first website was our exchanges platform which is our blog site out in end production within 30 days. Being able to handle video well. Being able to handle like text blog content well. Being able to handle community features well. And being able to combine those into a single cohesive site. Certainly some of the challenges with Drupal is talent starvation. How do we get more people involved into Drupal and how do we get them up to speed? I would like to see Drupal evolve to a place where mobile isn't something that's an afterthought. Works on any browser, any screen size, any phone. There's a tremendous opportunity there to simplify workflow to make things easier for editors to perform everyday tasks. The opportunity for Drupal is enormous. From where I'm sitting I see a world where multi-million dollar CMSs are going out of fashion. It really is an application platform and a platform to build web applications on top of. And I think Drupal's perception needs to break beyond that it's just this content management system. We'll start to do a lot more with mobile. So I'm very excited about the opportunities to expand on our desktop experiences and bring those to the mobile web. And we're gonna be leveraging Drupal to do that as well. I think that the vision is solid. I think that they wanna take Drupal to a level where it continues to get easier and easier to deploy web content. As these companies are making this transition for the first time into this new ecosystem that they're getting very excited about, Drupal is going to be at the forefront of that decision-making process. I think the Drupal community represents what open source is all about. It's been great. I feel a tremendous amount of promise. I love being part of the community and I'm incredibly appreciative for everything that everybody does every single day. So, there's a lot of things here in what they said. I wanna talk a little bit about these things in this keynote, but it's very consistent. These things are very consistent with things I hear everywhere. Like wherever I travel, these are the kinds of things people are saying. So let's break it out a little bit here. Let's talk about the strengths first.  So that's a huge testament to all the work that you've done. So, obviously what does that really mean? So, if you think a little bit about it, the fact that Drupal is open source, the fact that we can share a code that the license allows us to share code leads to collaboration, right? And that kind of collaboration leads to community and I think the important step is that community leads to innovation and that's, I think, why so many people really like Drupal. So, they like Drupal for the community because that translates into a lot of flexibility. Tens of thousands of us are taking Drupal and extending it in different ways, adding tens of, you know, thousands of modules really and that allows people to build pretty much any kind of website, right? It really changes the way people build websites. It frankly changes our industry. Like, where we're going from a world where people used to develop websites by writing code or by using frameworks to a world where people can actually assemble for the most part of a website. So, this vision of the assembled web and the kind of flexibility that that gives you is, I think, a direct effect of having a very vibrant and active community. And it's a big change because it is replacing a lot of legacy proprietary CMSs. So, a big opportunity there. So, obviously we can talk about our strengths all day. There's many, but I would actually like to talk a little bit about our weaknesses and, you know, the things that keep me up at night. Let's see. So, I really thought long about it and I came back with three things. You know, obviously there's a few more but I think it really boils down to three big things. The first one is the fact that we have, you know, a rudimentary authoring experience. And I think there's two big things happening right now in the world. First of all, and this is relatively new and it's kind of worrisome in a way for us, is that the content authors, the actual staff that needs to use Drupal from 9 a.m. in the morning till 5 p.m. at night or whatever, they're very involved nowadays in the CMS selection process, if you will. Whereas it feels like even a year ago or two years ago, it was mostly a decision made, say, by IT or by technical people versus the actual people using the CMS. So that's kind of an interesting trend, which means we need to put a lot more emphasis on the authoring experience. And the second biggest trend, and this is one that I've talked about in the past, frankly, which is the consumerization of IT. Like things like iPhones and tablets and all of these things have fundamentally changed the way people expect applications to work and the kind of usability people expect from these applications. So I think these two things combined really puts a lot more, puts a bigger spotlight on Drupal's authoring experience. So I do want to talk a little bit about that in this keynote. The second thing that keeps me up is our framework. Although Drupal still has, is still, in my opinion, one of the best CMSs, technically, we're also at an interesting point. Like if you look back at the early days of Drupal, Drupal was successful because it was very accessible to hobbyists. People could get it in the code, make some quick changes, you know, add to Drupal. I think for all the right reasons, Drupal has evolved to be more complex and some of that accessibility is lost in the process. At the same time, for more seasoned developers, Drupal is also a little peculiar. Like it isn't necessarily what they expect to be. So we've arrived at this point where it's a little hard for newbies or hobbyists and it's also a little hard for seasoned developers. So something for us to work on. And I'll talk about that as well. The third thing that keeps me up is, you like this image? It's a pool with small people. So it's a small Drupal talent pool. But this is actually a good problem in a way because Drupal is growing so fast. The demand for Drupal people, Drupal experts, continues to be bigger than the supply. And it's one of those things which is holding us back a lot actually. And it's an area where we're doing a lot of work on. The Drupal Association made it one of its priorities to help grow the ecosystem. There's things like Google Summer of Code which we should all participate in or help with. So there's a lot of initiatives to try and overcome this. But it is important that we continue to work on this. So these are some of the weaknesses. I'll come back to these in a second. So let's move on to opportunities. So according to Mary Meeker, who is a partner at Kleiner Perkins, I don't know how many people know Kleiner Perkins. It's probably the number one or among the top venture capitalist firms in the world. And so she said that we are now in the fifth major technology cycle. What that means is, I'll let it come up on the screen, it really means mobile. And so a lot of people are making very big bets on mobile. And so let's put that in perspective a little bit. So if you look at Drupal today, we estimate there's about 1.5 million sites. So big applause for everyone. That's a giant number by the way. But if you put it in perspective, it's only 6.7% of all the websites that have a content management system. So it's a pretty large number, but it is our first opportunity. The opportunity is to go after the other 90 plus percent. And I think we're well on our way. I think that number keeps going up. It's also where I think the platform vision comes in, like the one Drupal to rule the model vision, if you will, where we make Drupal better and more suitable for more different kinds of websites. So I think that number will go up over time. Interestingly though, only about 30% of all the websites in the world actually do use a CMS. So how many people knew that? Not many. So 70% of all the websites don't actually have a CMS. And that's also a huge opportunity for us because eventually either these websites will stop to exist or they'll probably move to a CMS. So making Drupal easier and better will also help us go after that piece. But the real opportunity, the biggest opportunity of all is really in mobile. If we believe the predictions, mobile is just about to explode and we'll grow by 25X over the next five years. And so in that picture, we're tiny, right? And we basically have kind of one shot at this with Drupal 8 to really go after mobile. So we're ready in five years. So that I think is a big opportunity and I'll come back to that as well in a second. So the threat really in my opinion is that we are unable to innovate and that we are basically being bypassed by other systems. So I think we've talked about that in the beginning, the need for innovation and the way we innovate. So all right, so that's kind of this section where we talked about the strengths, the community, the innovation, the weaknesses, the opportunity and the threats. So what does that mean, right? What do we do with this?  And so in the beginning of the presentation, I said that I would like us to win the hearts and minds of more people. And so when I think about that, I would like us to focus for Drupal 8 on three different audiences. Developers, site visitors and authors. And I'll talk about each of those in this presentation. So let's start with developers. So I've already explained some of the weaknesses which is this aging framework. So what we wanna do there is really update Drupal a little bit. I think, as I said, Drupal is still one of the best TMSes in the world, but I think also some of us realize that if we don't innovate on the framework piece, we risk being left behind. And so we spent months and months discussing about what that means, technically and architecturally. And after months, we've decided to leverage pieces of symphony, but we weren't all in agreement still. And so we basically got like 15 people in the room together, locked ourselves up in the room for about three days. And what we came out of is that actually we do wanna use symphony and we probably wanna use more of it than we expected. So we've decided with Drupal 8 that we are gonna embrace portions of symphony. Could be quite a bit. And obviously that's a very big deal. It's a very big decision for us because it will propagate to our contribute modules, the way we work, the things we need to learn and so forth. So instead of me talking about what that means, I've made another video and I'll let two experts basically explain you what that means. Here we go. Drupal at this point is the most advanced and powerful traditional CMS on the market, but the market is changing and what is going to be a market leader in the next five to 10 years is different than what was a market leader in the last five to 10 years. Drupal right now has a huge opportunity to really reinvent and reposition itself to be the leading system of tomorrow as well. Symphony is two different things. First and foremost, this is a set of reusable and cohesive components that you can use for your PHP project. Symphony is also a full stack framework and a full stack framework means that you have a tight integration between all the components and you don't need to make the glue yourself. We are one of the first big framework to have embraced PHP 5.3 and all the namespaces and stuff like that. That's the first point. And the second one is that we have tried to make it really flexible. I think the second version is really great if you want to create products on top of the framework itself. When we were working on the WISC initiative, we had a number of goals. Easier support for web services and being able to build more robust page layouts that could do partial page caching, could do edge side includes, could do a-ha callbacks in a much more efficient manner. And I think that's a going to be cultural shift for Drupal but a positive one and one that we are ready for and will benefit from immensely, which means that enterprise developers coming to Drupal will have an easier time adopting it. Developers coming out of computer science programs will have an easier time adopting it. It means that we can produce smaller pieces in modules that we can assemble LEGO style in Drupal in a site and build a more tailored site with less work. People who want to use Drupal as both a content management system and a framework get a stronger underlying foundation for both. Are we excited about this or not? It's kind of a big deal. I mean, it's a very big deal. So expect to see many of us talk about this at Drupal.com. Fabien, the symphony project needs will is actually at Drupal.com and there will be a session this week on symphony and possibly other sessions as well. So if you're interested, make sure to attend these sessions. And I couldn't explain it better than Larry and Fabien, but obviously symphony brings as many benefits. It's for people that really don't really know symphony. It's a well-tested open source project. It's very compatible. It has a very welcoming community behind it. We've had amazing help from these people in trying to do prototypes and stuff. And it's very solid technology. There's a lot of people using it. So I think by leveraging symphony and by working with the symphony project, we'll be able to go to more places faster, especially on the technical side of things. There's a lot of interesting things in symphony which will allow us to build more pluggable websites. It's gonna be easier to remove components from Drupal. But it also allows us to get to the next level of scalability because out of the box, for example, symphony has embraced edge site include. So it changes the way we can cache pages. It changes the way we can render pages. And in doing so, we can go after bigger websites. For me, one of the biggest advantages of symphony is that it actually will help solve that, you know, small Drupal talent pool issue, I hope, I think, I believe. Because by adopting a modern framework, I think we'll be able to get more developers, more seasoned developers, but also more junior developers and hobbyists because ultimately people wanna work with the tools of the future, right? They wanna use, you know, for their own careers, they wanna use the tools that will get them the furthest along. So that's kind of the first big thing, symphony. The second thing I wanted to talk about is what we need to do for site visitors. And I've already talked a little bit about this today, but I've definitely talked about it in previous keynotes, is we need to build a great mobile experience. And it also came out of the video. But if you think back, if you look back, in 2000, all the traffic came from desktop browsers. 10 years later, only in 2010, 3% of all the traffic came from mobile. If we are to believe these predictions, then by 2015, mobile traffic will be huge and will be bigger than desktop-based traffic, if you will. And so about a year ago in my keynote in Chicago, I said if I were to rebuild Drupal from scratch today, I would build it for mobile first and desktop browser second. And so I really believe if we need to change Drupal, turn it around so we can embrace mobile. If you think about mobile, there's different kinds of mobile if you build. There is native applications that run on your mobile devices, like iOS or Android. And then there is mobile web experiences, meaning people that visit your websites through a mobile browser on a mobile device. And we need to do the right thing for both. Because we need to do the right thing for native apps because I truly believe the web is changing from just web to web plus apps. I think that change is pretty visible to most of us. As Drupal, we need to embrace that. What that means and what we're doing here is on the native app side, we are adding restful web services to Drupal Core. We want to make it very easy for people to retrieve content in Drupal in different formats. And we want to be able to expose some of the CRUT functions, the basic operations on Drupal objects through APIs. Also think, and this is something we haven't talked much about, also think that maybe we should start thinking about adding SDKs, software developer kits to Drupal and possibly maintain these as projects on DDo as well. So people have starting points to build mobile apps. So hopefully something we can talk about this week. And then on the mobile browser side of things, we are working on making HTML5, the default output of Drupal 8. And we're also working on adding things like responsive design and all of the things that you would come to expect there. So a lot of things going on there, a lot of progress being made. I think an area where we could do better is embracing a mobile culture. Like when we work together in issue views, I almost never see anyone share a screenshot taken on their Android or taken on their iPhone. So we still need to get it in our DNA to really truly embrace mobile. And it's important that we do this now because we need to do it before the rest of the world does it. Because we need to build Drupal so that it's ready by the time the rest of the world wants it. So I think we need to work on this a little bit more. So maybe everybody should get an iPad or something. If you reach under your chair, it's provided by the Drupal Association. I'm joking. But maybe you can ask your boss. But I think it would be really helpful for all of us to do this. All right. And we'll talk about this at this conference as well. So the third audience is the site visitors. Sorry, it's the authors. So we talked about site visitors. Let's talk a little bit about authors. This is a big one. It's probably the newer one for most people. But as I said, Drupal today really wins based on technical merits. And so we did a whole bunch of research, and I created this kind of like spider graph. But it basically what it shows you is different content management systems. And we've rated each of those based on technical strengths. And so I'm not sure it's very readable, but there's scores from zero to eight. If you have an eight, like Drupal, it means you're the best. And so you're all the way out there. And if you have a low score, technically, you're more towards the middle. So Drupal is winning on technical strengths. But if you look at the authoring experience, I think it looks a lot more like this, where frankly most of the other systems are better. And so that's an area that we really, really need to work on. So if you look at the authoring experience in more detail, and you break it up in several components, you know, what does it actually mean, authoring experience, right? So it's like inline editing, workflows, mobile authoring, localization, layouts, all of these things. And if you look at all of these competitors that I just showed you, and you take the best from each of them in these areas, you can sort of create an ideal product, roughly, right? And that's what's shown in orange. And then we looked at Drupal and overlaid that with the ideal product. And so what it shows you is that we're doing pretty well on the workflow site. And that's, you know, thanks to contributed modules like the workbench module and other things. But we're doing pretty weak, for example, on the inline editing side of things. And some other areas. So ideally, over time, you would be able to sort of, you know, spend the entire graph and get a lot closer to what I think would be the ideal product. All right, so what does that actually mean? I think it means a couple of different things. First of all, I think we should put more stuff in Drupal 8 core. Because a lot of these things are expected. A lot of these things are what I would call infrastructure that every person needs. It's like, people want more inline editing. People want more drag and drop. People want more improved content administration tools. People really want better media support. Like, that's why people get a content management system, to be able to manage the content, right? And people do want better page layout building tools. And I think a lot of these things we should try and put in core, which would, you know, obviously make core bigger. At the same time, we need to keep core very pluggable. Because we also need to recognize that distributions are the best way to build, you know, specialized user experiences. Like these things core can do, core can provide the infrastructure. But to really create the best user experience, you need to know the audience. Often distributions, they know the audience that they're built for. So, we're also doing a lot on distributions. One big thing which we just did is we changed the way we can build distributions on D.do. We can now include external libraries and all of these things. Which is a big change. We're also working on better promoting distributions on D.do. There's a lot of events happening to help grow a community around distributions. And ultimately, I think the big one is we really have to figure out the revenue model for distributions. Because I think if people can make money with building distributions or more money, you can actually make money with distributions today. But if more money could be made, I think it would cause more people to build really great distributions. I think distributions are the way to... If you go back to the planets, it's the way to capture more of the other things which we aren't doing yet. So, here's a quick screenshot of some of the things which we're trying to do on the Drupal main page. As you can see on the screenshot, we're trying to make distributions. First-class citizens by adding it to different pieces of the website. These are just mock-ups that gives you an idea of what is hopefully to come. And this is something the Drupal association wants to really start helping with. So, we're starting to build a bigger team of people working on D.do. So, obviously, it's kind of a big topic. It's not necessarily easy to pull this off because it's really hard, especially as we get bigger, to build consensus on what is one considered good usability and secondly, what should belong in Drupal Core and what shouldn't belong in Drupal Core. I mean, this is the kind of stuff which we have talked about for many, many years. So, here's a proposal on how to fix this. First of all, let's look at the Drupal 8 timeline. This was announced recently, but I'll announce it again. The goal is to get to feature freeze by December 1st. That's roughly eight months from today. Once we're feature frozen, there will be some time to complete the features which we started adding. And then ultimately, we want to freeze the code by February 1st, 2013 with the goal to release Drupal 8 at the next Drupal code in Europe. So, not the one which is coming, but the one after that, right? So, that's, I think, roughly 18 months from today. So, that gives you a sense of when you can start planning upgrades and things like that. So, anyway, if we want to nail the authoring experience in Drupal 8 and if we want to make progress there, we only have a little bit of time left. So, what I would like to do here is, you know, go through three phases. First of all, I think we should do some analysis. You know, we should do more talking brainstorming about what we want to add to core. I don't have all the answers. I think it very much should be a collaborative effort to figure out what we want to do. Then I think we should come up with designs, mock-ups, maybe even prototypes. And then by the end of July, I should really start to make some decisions based on these mock-ups, like we're going to add this to core, and this is what it's going to look like. So, we can actually start implementing it and basically implement the mock-ups that we kind of signed off on. Once implemented, hopefully these things will be able to get committed before feature freezes. What exactly will go in? I don't know yet. We have a lot of work to do here, but I think it's important that we have some sort of timeline and that we have decision-making points in order to get there. So, that's what I would like to do, and I'm sure we'll talk more about that this week as well. Other than that, we're also working on a lot of other things. I don't necessarily want to rehash all of them, but we've launched a number of initiatives for Drupal 8, and this graph actually tries to summarize some of our status. So, what it really means is that most of the initiatives, they're pretty much done with their analysis, meaning we have figured out what we want to build. It's kind of the what. Most of them are doing really well on the design phase, meaning we know how to build it. All of them are in the development phase. We know what to build, how to build it. Now we just have to build it. It's a lot of work. That's why it's important that more people actually get involved. We need a lot more help. If we want to get this done, we're going to have more people that need to contribute to making this possible. So, make sure to go to the sessions. Each of these initiatives will have sessions, either in the core conversations or elsewhere, where you can learn how to get involved and where you can learn about the details. So, I think if we do these three things, if we focus on these three things, I think we can win the hearts and minds of authors, developers and site visitors. I think that would fuel into a lot more passion. I think it would make Drupal better. I actually think it would help us overcome our weaknesses. We would do more of our strengths. It would overcome the weaknesses because we would go after, we would fix the framework thing with Symphony, we would fix the authoring experience with some of the work we're doing and actually think in doing these two things, we actually also help fix the talent pool issue, as we talked about. At the same time, by doing mobile, we actually go after the opportunity, which is also very important. And again, in doing so, we reduce the threat of being replaced by something else. And if we do so, I think we can make Drupal 8 very successful and I think it can translate in the next big bump in terms of adoptions. And with that, I'd like to say thank you. Thank you. And open the floor for some Q&A. I think we have about 10 minutes or so. Yeah. It didn't take very long before DrupalCon keynote was a trending hashtag in the US. I think three to five minutes and it was announced that it was pretty much out of control. So I think we got some good questions ready to go and I guess we'll start with some difficult ones and then move to the easy ones. So first one we have is from a gentleman named Art USA Mac. What is the limit of symphony integration and does it mean rewriting Drupal on symphony? Right, it's a good question. I don't have the answer. So we basically agreed to use certain components of symphony. At the same time as you saw on the graph with the progress bar, Larry and the rest of the team, they're still trying to figure out how far we want to go. So we have some things which we agreed upon and then there's basically still some great area where we want to figure it out still. So it's the best I can say right now. Sure. But go to Larry's session. You may have all the wisdom. Or at least some good answers for us. So we have another question from a design's drive. Will jubilee be mobile friendly out of the box? Yes. So the goal, that would definitely be the goal. So one of the things which we're doing is as I explained, we want to output HTML5 out of the box and then also we want to update all of our teams that ship with core to support responsive design. Excellent. We want to improve the admin back end. So it actually works great on mobile devices. So we're doing all of these different things through a number of these initiatives with the goal to provide a great out of the box experience on mobile devices. Awesome. That's great news. This is from... These are difficult questions by the way. We've thrown an easy one there. No. This one's from Mr. Randy Fay. Are there changes we need to make in our community or development process now that we have grown so large? That's a tough one. Thanks, Randy. I think the answer may be yes. I think we have a culture of making changes. If you compare the way we work on Drupal 8 versus Drupal 7, I think that's already a huge change. We put a lot more process in place in terms of number of critical box, which we want to have open but also the initiatives and putting people, the initiative leads in more of a spotlight, I think is a way to delegate leadership and authority and I think as we get bigger and as core gets bigger, I think we need to do so. I have a few other ideas in that area as well, which I'll talk about in my core conversation. I don't know when it is, but this week. But the answer is yes, and I think we've always been open to discussing these and I think we have a track record of implementing changes as well.


We did a non-lethal O.C. training and took the panic attack and the bottle right to the face and it was, it was good, it hurt. So as Marines with the Special Purpose MAGTAP, we have the potential to deploy anywhere in the St. Com area and essentially in response to a crisis situation. And in the event that there is a crisis and our Marines do get deployed to that area, we need to provide them with a capability that isn't just a lethal capability. So when engaging with a hostile individual, whether it be a rioting situation or an embassy reinforcement.  You can't see much, your face is on fire. So try to fight through that knowing that you can afterwards. It's pretty accomplishment at the same time. The during and even the after is still pretty, still pretty painful. It definitely mixes up the day-to-day lifestyle that you're getting used to. And to be able to do a training, I think it also builds camaraderie. Everyone coming out here and just enjoying a little bit of pain is not bad at all.


The Muse instrument on ESO's very large telescope has given astronomers the best three-dimensional view of the deep universe ever. By staring for 27 hours into the Hubble Deep Field South region, these new observations reveal the distances, motions and other properties of more galaxies than ever before in this tiny piece of sky. They even go beyond Hubble and reveal previously invisible objects. This is the ESOcast, cutting-edge science and life behind the scenes at ESO, the European Southern Observatory. Long exposures of the sky have created many deep field images, revealing much about the early universe. The most famous of these, taken in 1995, was the Hubble Deep Field, which rapidly transformed our understanding of the early universe. It was followed two years later by a similar view of the southern sky, the Hubble Deep Field South. But these images did not hold all the answers. To learn more, astronomers had to then look at each galaxy with other instruments, to split up the light into its component colors and measure distances and other properties. This was a slow and arduous task. But now the new Muse instrument can do the same job for all the objects in the field in one go and far more quickly. One of Muse's first jobs was a long hard look at the Hubble Deep Field South, and the results exceeded all expectations. Even with a much shorter exposure time than Hubble, Muse revealed more than 20 very faint objects that Hubble didn't see at all. The Muse data contain a spectrum for every pixel in the image, about 90,000 in total, telling astronomers about the distance, composition and internal motions of hundreds of distant galaxies. Instead of producing a single image, Muse produces a stack of thousands of images, each showing the view in a different color. The new observations allowed scientists to measure the distances to 189 galaxies in this area of sky. These are marked with colored symbols on this image. The colors show how far away the galaxies are. Blue and green ones are relatively close, and pink and purple ones are very distant. They are seen when the universe was still very young. Triangles are objects that are so faint that they couldn't be seen in the Hubble images at all, but are detected by Muse. For closer galaxies, Muse can even look at how they're rotating, and the way in which their properties vary from place to place. When passing through the Muse 3D data, one side of a rotating galaxy appears before the other, as one side is approaching and one receding. The Doppler effect shifts the light either towards the blue or red end of the spectrum. The power of Muse to probe the distant universe has been demonstrated. Astronomers will now be able to study thousands of galaxies and discover new, extremely faint and distant galaxies. These infants, seen as they were more than 10 billion years in the past, gradually grew to become galaxies like the Milky Way that we see today. Studying them at such a young age provides an invaluable window on galactic evolution.


Item No. SCP-1933 Object Class Safe Special Containment Procedures SCP-1933 is to be kept in a standard low-security cell, equipped with basic furnishings. It is to be provided with two liters of Irish whiskey, 500 ml of double cream, no less than 48% fat content, 25 grams of powdered sugar, and 20 ml of refined vegetable oil on a daily basis. As SCP-1933 is unwilling to engage in basic hygiene, it is to be forcibly stripped and showered by level 3 personnel on a weekly basis, and its beard shaved and nails clipped on a monthly basis. Its soiled clothing is to be considered highly flammable and is to be incinerated as a fire hazard. Description SCP-1933 is an obese, middle-aged Caucasian male in a constant state of moderate to severe alcohol intoxication. SCP-1933's bodily fluids, including both intracellular and extracellular fluids, consist entirely of a substance identical in composition to the alcoholic beverage known as Irish cream. This substance adequately fulfills the functions of the fluids it replaces in SCP-1933's tissues, despite the fact that it renders normal biochemical processes essential to life impossible. Foundation scientists have been unable to determine how it manages this. SCP-1933 subsists on a diet of cream, Irish whiskey, sugar, and refined vegetable oil, the basic ingredients of most commercially produced varieties of Irish cream. It prefers to supplement its diet with small amounts of various herbs and flavorings, usually coffee, but these are not essential to its survival. It is incapable of digesting anything that is not a standard ingredient of Irish cream, including Irish cream which has been prepared beforehand. SCP-1933 will display effects consistent with acute malnutrition if its blood alcohol content significantly falls below or exceeds the range of 15-20%. The Typical ABV of Irish Cream SCP-1933's bodily fluids are safe for human consumption if intake is limited to 25ml or less within 24 hours. If a subject exceeds its limit, there is a significant risk that all their bodily fluids will be transformed into Irish cream. This substance does not fulfill the function of the fluids it replaces, as it does in SCP-1933. As such, it is instantly fatal. The probability that a subject's bodily fluids will be transformed into Irish cream increases by approximately 5% for each additional ml of SCP-1933's bodily fluids consumed. It is not known that the bodily fluids of SCP-1933's victims would have the same anomalous effects as SCP-1933's bodily fluids if they were to be consumed. Prior to containment, SCP-1933 was chronically homeless, sleeping either on the street or in derelict buildings, wearing a Santa Claus suit at all times, stealing money with which to purchase the Pacific items of food and drink necessary for its survival, and collecting its bodily fluids and bottles. It would attempt to break into people's homes between 2300-24th Christmas Eve and 0500-25th Christmas Day, and place crudely wrapped bottles of its bodily fluids alongside other wrapped presents, with the intention that they would later be unwrapped and subsequently consumed. SCP-1933 claims that this activity was motivated by a benevolent desire to give people presents, and refuses to acknowledge that its bodily fluids are fatal if consumed in large quantities. It has not been determined whether it is genuinely unaware and unwilling to accept that this is the case, or whether it is trying to conceal malicious intentions. However, the general consensus among Foundation staff who have studied SCP-1933 is that the former is more likely.


Hi there, my name is Reuben and today we're going to have a look at the abdominal aorta. I'm going to quiz you as we move through so that you can learn it yourself. Here we have it. Let's divide it up into sections according to which vertebra each portion overlies. Right at the top what do we have branching off? The first arteries are paired and they supply the muscle that the aorta has just popped through. That would be the diaphragm. So this is the inferior phrenic artery. Next at T12, the artery that supplies all the organs at the top of the abdomen. It comes from the ancient Greek word for belly. It is the ciliac trunk. What three main arteries does this end off? One that follows a coiled path over the pancreas, the splenic artery. One which goes straight to the stomach, the left gastric artery, and one which runs to the liver, the common hepatic artery. Off the splenic artery we have two main arteries that supply the stomach. The short gastric and left gastroepiploic arteries. Off the left gastric artery we have branches to a structure that runs parallel to the aorta then runs into the stomach. These are esophageal branches. From the common hepatic we have three branches. One, the proper hepatic, two, the gastro-duodenal, and three, the right gastric. From the gastro-duodenal we have the right gastroepiploic and superior pancreatico-duodenal. The main branches of the abdominal aorta run down in the order CSI. C for ciliac, S for superior mesenteric artery at the level of L1. First of all it gives off arteries for the second section of the small intestine. These have few arcades and long vasorecta. They are the gyginal arteries. Next with many arcades and short vasorecta we have the ileal arteries. We then have one branch that goes up and finishes the work of the common hepatic. This is the inferior pancreatico-duodenal. Next the first two parts of the large intestine are supplied. We have the middle colic and right colic arteries. The superior mesenteric artery is a loop and the loop is completed by the arteries supplying the stuff in the lower right corner of the abdomen. This is the ileocolic artery. Next up L2. From L2 we have two major arteries branching straight from the aorta. First up the renal arteries which has the inferior super renal coming off it. The superior infra renal comes off the inferior phrenic just so you know. Next we have the arteries to supply our testes and ovaries the gonadal arteries. Okay L3. This must be where our last criminal hops off remember CSI. This is the inferior mesenteric. It supplies everything in the lower abdomen that the superior mesenteric didn't. We've covered the right and middle colon so here we have first the left colic artery. So what comes after the descending colon which is the left side of the large intestine. The sigmoid colon thus the sigmoid branches we've got here. Last but certainly not least we have the end of the abdominal GIT covered. This is the superior rectal artery. At L4 I've included an artery that we see in four different pairs along the abdominal aorta. They run back on the bodies of the vertebrae behind that vessel. These are the lumbar arteries they are paired arteries. The last thing we see here is at L4 the bifurcation of the aorta splitting into to become the common iliac arteries. So how did you go? Have another crack and before you know it it will be as easy as ABC or CSI. Alright thanks very much hope you enjoyed that. See you next time.