I think we're good, so I'm going to hand over to Catty, who's got a great talk about tips and tricks of design for developers. Lower the bar please. Okay, so hi, my name is Catty Namoraro, you can find me on Twitter at Tevalica. I don't know if you've been to Amit's talk, he talked about patterns in architecture, but similar to architecture we also have patterns for interface design, and I provided a link there if the slides are available on Twitter, so you can go if you're interested in more, because some of you asked about patterns, but in this talk we're going to go even lower, even at the core principle. So there will be like the basics, so patterns are more advanced, maybe we can talk about that in the future, but now we'll go even lower. So principles are fundamental rules, and if you were to apply just one principle in your day-to-day interfaces, that would be consistency. So what consistency means? If the user learns your interface once, he will know how to use it in subsequent uses, and that is very important because it's much faster for him to react. But if we're saying that we're designing a consistent interface, this doesn't mean that all the buttons needs to be the same. There are several types of buttons, and it's very important to have a primary action on your screen, so the user needs to know what is the main thing you want him to do. And primary actions are usually designed with more contrast and color, so he gets the point on what you want him to do, and they should be like only one per screen. And these primary buttons needs to be very clear, so we should avoid things like yes or no or read more or stuff like that. Users think in actions they want to delete something or they want to add or to edit, so we should use verbs. We should not have long buttons. We could give context, but verbs are more efficient in terms of directing the action. And also, when we ask the questions, we should avoid double negatives or very abstract things. We should use a common language and make it very clear what we want them to do. There has been a very big debate on where the buttons should be placed, should be placed on the left side or on the right side, and if we are developing a native application it's much more easy because the operating systems have guidelines and style guides and they have a preference, but if you're designing for the web, on the web the rules are not that strict, so I just want to show you some points on why you should pick one or another. For example, on the left line it's very easy for the user to vertical scan. He can read the title or he can read the labels, and if he finds the button at the end he can just jump from the title to the action. But if you want the user to actually read the description text, he will make like a z-shape, so he will read the description, and then he will need to press the button, so in this case the position matters, because for example, if you're using left-align he will read the text, he will go to the primary, he will see the secondary, and he will need to go back. So it's a bit longer to react, like a millisecond or something, but can add up or at least compare to the other right-aligned.  If you're doing a mobile application, it doesn't really matter if it's on the left side or on the right side, because the width is very tight. There are some interfaces that even put the buttons in the middle, or the buttons are full width, but when we are designing for web now as developers we like to have 8K monitors if we can afford them. If you don't have columns, if you are applying a right-align layout, the buttons can get separated from the context, so the user might feel lost or not see the connection between the actions. So here, again, he will do like a nail shape. Now, I've talked about primary and secondary action. The thing is that regarding patterns, there are some patterns like wizards where you have multiple steps and you need to go like next and previous. If you're designing for someone from Western culture, when we read books we kind of go from right to left and we're switching pages, so that's why next button, feel more natural to be placed on the right side. But even when you're placing them, just make sure that the primary action is on the edge. Edges are much more accessible because they're coming, so don't place the primary action in the middle of the screen. So again, you need to decide, do I have wizards in the interface, you need to place them on the right, but if you place them on the right, place them everywhere. Don't switch the position depending on what interface pattern you're applying. Okay, buttons and colors in general. It's very nice that we can attribute some color meaning to the actions and, again, be very sensitive of your target. In Western culture, red means danger and errors, but in Asia, red means abundance and luck, etc. So they have reversed the green and red. But even if we can give all the cultures, try to limit the palette in order to be more pleasing and we can convey, in other ways, things like warnings and infos. And why it's important, at least to have one color for dangerous action is that if you are sure consistency across the interface and all your buttons are, let's say, gray and blue, when the user will see a red button, he will understand that that is a very important, or it's something with that action. And for destructive states, it's really important to ask for confirmation. So if you're doing something that will affect the user, ask him to see if he didn't accidentally press that. And I know it's harder to implement the undoes and measure controls, but they could be very helpful for the user to feel in control and safe and know that he can come back to that. Okay. And I know we talked a lot about buttons. We still have. But there's another principle which is called affordance. And affordance, the metaphor is like when you see a door and if the door has a circular handle, you might know that you might need to switch the handle. Again, if the door has like a pull, you know that maybe you can pull it or you can push it. And that's why sometimes when the door does the reverse thing of what you're expecting, you might be a bit confused. You don't know what's the direction. The same for this principle can be applied to links. So for the people that have been for a long time on the web, when they see something that is blue and that is underlined, they might think that, okay, that's a link. Or at least I know that's a link. So be very careful when applying blue to headers or things that are not linked. In the past year, the designers wanted to leave the old habits and maybe try to express themselves with colors. So it's okay to have links of other colors according to your color theme. But the most affordance based on your prior experience are blue and underlined. Same for buttons. When you see a button, buttons usually have the click state and you know that you need to be pressed. They have multiple states. So in order to increase usability, they should be represented at 3D objects that have some shadows or that have some borders or that have some gradients. So the flat trend for the past years have lowered the bid usability of the things because you don't know if that's just a container or it's actually a button. So ideally, they should have these affordances that can help the user know what type of entity it's in the page. One of the questions is, okay, when we have an action, what do we use? Do we use buttons or do we use links? And if maybe it's more clear that you should not have buttons inside the text because maybe you'll have some alignment things that the line height will get increased because the button doesn't have the same 12 pixels or 16 pixels. This is not actually the way we should rational about them. Buttons and links have been created for very specific purposes. So you should use buttons when you would like to have an action. It's something that changes inside the interface. You're adding an element or you're producing changes on the database or something like that, so actions. While if you're just navigating to other places, you should use links. Okay. Another principle is the proximity principle. So objects that are closer together are perceived to be related and this is a very strong visual principle that we could use inside the interfaces. So for example, if you would have a menu, if you just put some entries more closely together, people will perceive them as related. But it's very important to actually be related. Not just place them because they visually look nicer and this is an example of how it was used to be done in Gmail for an older version. Okay. Another related principle is the similarity. So similarity states that object sharing attributes are perceived to be related and we can force that using colors or shape or orientation. So if you would want to try to read this, let's say per lines, your brains will be harder for your brain because he will naturally try to put them in groups. And having this similarity and proximity principle in mind, there is an even stronger principle that is called the law of unity, which can override cues from this principle. And actually the thing is that if we are linking consecutive objects by lines or by borders or by background color, we can suggest somehow that they are related. And here is an example. So for example, if you are in an activity stream, if you just separate with lines, people will perceive this as an entry or that could be a logging form. Just a note here is that we might be very tempted to use these borders and lines, but the more borders we use, the interface would look more crowded. So in the past years we've seen a fallback instead of law of unity on the proximity. So the designs are more airy and they're using more white space and they're more relaxed and just rely on the proximity, not just on these cues. Okay, choice paralysis. It's a principle that states that if you give the user lots of choices, you might not know which one is best for them. And there's another law which is called Hicks law that states that the time to make a decision increases with the number and complexity of choices. And what we can do about this is to try to limit the choices we are offering to the user. To clearly mark what are the differences, we can apply this for example, in North software there are multiple download versions, so we should not represent them all the same. Be very clear. Actually if we can limit just the two and maybe if there are some advanced things just put them aside. I know we want to show all the options we have, but it's better for them to get a recommendation and know exactly what we should expect them to pick from that. And a similar rule to this is the seven plus minus two rule. So a century ago Miller did some experiments. I thought you were making pictures, so that's why I ignored you for a long time. So Miller's rule, he was having a lot of people and did research. He was giving them like lots of words and tried to see for the short term and long term memory how many of those words users remembered. And the average at that time was like seven plus minus two words. In theory designers use this rule to always say that we should not never have more items in the menus and all the websites should have this limit. But researchers have redone the research more recently and the value changed from four plus minus one. There's no clear conclusion on how many items there should be. The point is to have as few in order to be as easy to be used. Okay, and there's a principle that is called zero-position effect. If you think, let's say, at the alphabet, you know that it starts with A and then ends with the Z, but you don't actually, I mean maybe you do, but some of us have trouble remembering exactly what's inside the sequence. And this principle can be correlated with chunking. So for example, if you would need to have like nine items in a navigation bar, you could split them in groups of three. And this way you will have a first and a last for each of the groups and they will be easier to scan and easier to remember. And also they should be correlated, related not just placed there. And chunking is actually very useful also for form elements. I don't know if you have a card number, you should chunk them. People when they are trying to remember their phone number, they are usually splitting in sequences of two or three. So it's much easier for the user to know exactly what information they should enter. And regarding the easiness, for example, here it's an example with the zip code, but the most classical example, when you enter the card details, when you do a payment, and if a user sees an input of three digits, he might know that that's the CVS that he needs to take from the back of the card. So it will be much easier for them to fill the form. Here, if you place the labels on top, again it will help with visual vertical scanning. Highlight and explain the error in the context. Some applications have a generic zone where they place the error message, and it's much easier to implement like that or with alerts or with toasts. But for the user, it's much more clear exactly where he did the mistakes and also provide a hint of what he should fix. And if we are using some white inputs on something that has a light background, like it's here, the user will have to trigger he will want to fill in the blank. So if he sees something white, he will like to fill it, and that's how you can increase maybe some forms that have some optional fields. Okay. I've seen a lot of times when we have numbers that they are left aligned or centered, and the rule is to have them right aligned because if you have decimals and hundreds, it's much easier to compare from one to another. And this exclusively, not exclusively, but it's even more important on tables when you have quantitative data. So you can then apply them to currency or even to date and make sure the dates have the same format so it's easy to scan months and the days. And here I've also used easy to digest the date format because we don't want to see those long formats that we usually see in our interfaces. Icons are very important because I can't remember that Icons are not universal. People might look at this icon and think that it's a search, but it could also be a zoom because maps used it too or they could think it's a ping-pong paddle and they have tested the survey research on this. So it depends on your privacy, previous knowledge with Icons. You might understand them differently. But Icons help the names. The first time you will see them you will not know what exactly that icon means, but on subsequent users you will understand that that means I don't know recent tabs or downloads and you will just jump at it recognizing the Icons and not needing to read the text. Okay. I know I've went very fast and there are two books I can recommend learn more principles of design and the refactoring it's more of tips and tricks from a designer point of view. Okay. The slides are on Twitter. So if you have any questions, we have 30 seconds. We have time for a couple of questions because there's lots of people outside and we need to do the full turnover. Okay. That's a very unusual question. So I use Sphinx documentation for my open source project. So I'm using the default template. I'm pretty sure a lot of people put some effort in doing it the most generic nice template but I feel something is definitely wrong with it. As a developer I cannot say what's wrong with it but I would like to get it fixed somehow because a big team is using the same template for documentation. So in general open source projects tend to do generic things and things that are scalable and the base for theming so this is not necessarily wrong but you can do customizations on top, right? And my suggestion is identify what's the problem. You can do that by asking a designer or actually asking other people what they think it's wrong with it because I don't know what is wrong. You can try to fix it or just do a theming for it and theming can be diverse because we all have different purposes so it might work I don't know for not dark mode but theming should be supported mostly because there are people that are colorblind and ideally I don't know. Yes? Somewhere down there if you can project a set of patterns in medical industry application or a specific type of pattern in games is there a difference between those categories or is just that using it because it can create a habit and everyone will use it but that doesn't raise the risk with the threat of malicious participants exploiting these human habits. So the question is that there are different patterns for different industries and this is kind of hard to respond. The thing is that there are common things that all humans will understand and will perceive in psychological principles. It's very important to know your target. I mean if your target are children or people under 10 years old you will apply some patterns compared to someone in pharmaceutical industry I don't know. Industry come with some patterns but you will not find a website that will list them on domains. On the web we will have patterns like wizards and how the search results should look like but I don't know any of them but I would be very interesting to know if they are So like we have the good patterns there is this other category that are called dark patterns there are a lot of research and people that are trying to combat this they are usually taking advantage of in advertising and making people sell or buy things that they don't want or book things but that's not that good designer would not want to apply those patterns but you cannot force somebody to apply them or not but they shouldn't it's not recommended yet. Hicks law being abused so badly Hicks law being abused like to sell me service providers hosting companies but designers take an ethical standpoint like oh I've got four options I'm going to highlight this Ideally you should highlight it because you will have the user but depends on your purposes if you know how to manipulate these rules you can propose something that is not beneficial to the user but this depends on the moral values of the designer so I don't know how to answer that thank you so much for coming


Ah, summer! It sounds good right now after what we just experienced, doesn't it? Walk Resort. And today I want to show you guys the little hidden gem that is actually a brewery on Disney World property. A lot of people don't even know it exists, but it is here at the Boardwalk Resort. So, let's go do this. And here it is. Big River Grill and Brewing Works. I'm so excited. I hear they have fantastic food along with some amazing beers and we're gonna try both. Interesting fact though, this restaurant is not on the My Disney Experience app. So, you can just come in and see if they have any open spots or you can take a little seat at the bar. As you can see, as soon as you walk in, you can actually look at all the different brewing machinery they have. And it's right behind these glass windows on display for you. And they notice they keep it very clean. It's very nice, but this is the brew house. There's the fermentation. I don't know if I said that right, but those are the fermentation tanks. And then of course, all the different brews that are on tap right behind the bar. So, this is the beer menu. They have nine different types of beers that they brew in-house. And you can actually get a flight. And the flight comes with the signature four. So, the Southern Flyer, the Rocket Red, the Carousel of Hops, and the Midland. And then you get to pick two other ones. The beer of the week is actually a peach beer. And I'm excited to try that. And also this Strawberry Rhubarb Sour. I think that's going to be my sixth. And Bada Boom. There they are. I don't know which one I should go with first. I mean, the Strawberry Rhubarb Sour is definitely calling my name. Oh, yeah, we're going with the Strawberry Rhubarb first. Ooh, I like it. Very good. Since we went with something a little sweeter, I might as well hop over to something a little hoppy. The Carousel of Hops. It's very hot. At the rate that I'm going, I'm going to drink all my beer before my food gets here. So, we're going to stop for a second. And we're going to look at the menu. And I'll tell you what I ordered. So, here is the menu. We got starters, satellites, soups, sandwiches, the main dishes, the burgers, and the desserts. I went for the meatloaf. Because meatloaf and beer go together very well. But I was also thinking about the Habanero Chicken or the Kobe beef burger. But like I said, meatloaf and beer, you can't beat that combination. So, it's very interesting to point out that the whole flight only cost $8.99. And a regular beer can cost anywhere from $6.99 to $7.99 for a $16 ounce. So, I feel like the flight is the way to go because you get a little taste of everything. Another fun fact about the brew house here is that they do not sell anything that is fried. They have no fried food. Which is kind of cruel. Because they only mean like they're like skipping out no fryer but we got breweries. And now let's get back to the beers. I think I'm gonna go with the Midland. An English brown ale. Hmm. Don't mind if I do. Oh, that one is very good. I like that one. So far my favorite. Oh yeah. Oh, good aftertaste. Oh, look at that. They're in the back changing out the kegs. That's pretty cool. Or they're filling the kegs. Yeah, I guess they're filling the kegs. Wow. I'm not sure which one's gonna be my next victim. The southern flyer, the rocket red, or the treatment of the week, which is the pear or peach. So I guess I'm gonna go any mini, mini, mo, ketchup, tiger, buy it. So if it hollers, let them go any mini, mini, mo. This is the peach beer. It's the beer of the week or the treatment of the week. So let's give it a go, huh? Wow. That is delicious. Wow. I don't know which one's better now, the Midland or that one. Well, we got two more to go. So I don't want to make to see which one's the best one yet. I gotta try them all first. Tent a table. That's how I like it. And strictly driven by a love of beer and a passion for people. So the treatment of the week, the peach beer was actually a peach tea drink, a peach tea beer. And like I said, that one was really good. And now I think I'm going for the southern flyer. Haha, gotcha there. You thought I was going for the rocket red, didn't ya? So this, the southern flyer, is one of the four brands and it's available all year along. So let's give it a go, huh? Much too good for children. And I guess that leaves you, rocket red all by yourself. I'm so lost without you, rocket red. I hope you're delicious. Very good. Just as I finished up, look at this. Oh yes, the meat loaf and the potato chips. I like it. So here it is, the meat loaf. It looks really, really good. It usually comes with the cheddar mashed potatoes, but I'm sure you guys already know I don't like cheese, so I opted for the potato chips instead. And it comes with a little mixed vegetables, but I have to say that is a big portion. Looks very good. Alright, here we go. Look at this. It looks so good. And I'll let you guys know because I am a meat loaf enthusiast. I've had lots of meat loaf for my day, so I'll give you an honest opinion on this. Amazing. This gravy is what sails the deal. It's like a sweet gravy and I love it. I really do. It is really, really good. Really good meat loaf. The veggies are pretty good too. A mixture of white beans, green beans and carrots and potato chips. I like them a lot, but they do kind of taste retail-ish.  I'm gonna try a little meat loaf potato chip. I don't know how I'm gonna do this. Maybe I'm gonna do this. Oh, that did not work. Maybe like this. Ah, there we go. Yeah. Now I'm gonna make a little meat loaf potato chip sandwich. Put its hat on. There we go. Oh yeah, look at that. I gotta say that meat loaf definitely ranks up there. Might be the best meat loaf on Disney property. I mean, there's not many meat loaf selections anyway, but wow, that is pretty good. It tops up there with Walt's meat loaf in Disneyland, which they don't have here at Disney World. Not too bad on the pricing. So it came to $26.16 with my annual Fastest Count, and I gotta say that was very, very delicious. What's the flight of beer? It was only $8.99. You can't beat that. That was delightfully delicious. I'm sorry, I had to take my glasses off because they're fogging up, but honestly, I really liked it, and they actually have locations off Disney World property too. So you might be able to have one of those close to you, and I really did like it. Very good, and it's actually not that expensive. It's not pricey at all. So that's gonna do it for me. I hope you enjoyed. I hope you had a lot of fun, and I love the life you live. We'll see you next time. Bye.


service to london waterloo calling at box hall and service to london bridge calling at stratum common stratum tolls hill gulf valley


Don't let the thrill substitute your parachute.  If you follow God's commandments, you will miss on the fun. If you live your life according to God's rules, you will miss on the excitement. Therefore, jump out without the parachute and hope to have the most fun you can, and when you're getting to the bottom, call God to be there to pick you up, because you don't want to of course have a funeral. And that's what the enemy lies to us, and that's exactly what this Amnon believed. He falls in love and he becomes sick with feelings. The Bible says he starts losing weight. He becomes physically sick actually because he's so in love, and instead of going to God's word, he begins to see his feelings as an indication that this is right, and does that which his feelings tell him, even though it's contrary against the word of God, and eventually he ends up making a mistake that he regrets. As Christians, we must understand our standard is not our feelings. Our standard is the word of God. As Christians, we must understand is the measuring line for us is not our infatuation. Just because it feels right, it doesn't make it right. Just because it feels so good, it doesn't make it so good. Were you in love at the age of 14? Man, it felt right. You knew you're going to get married to the person whose name you don't remember now. But how many sleeps you missed? You lost your appetite. You were losing weight, or some of you were gaining weight at that time, because you were so excited, and there was not one thought in your mind. This could ever go wrong. This person is perfect. Two weeks later, you found someone else. So by now being 2024, you can come to one conclusion. Your feelings are not consistent. They are so irreliable. When a married man begins to throw an eye to another woman that is his friend, because his marriage is struggling, and those feelings become so real, and they are so strong, my friend. Just because it's real, it doesn't make it right. And just because it feels good today, it does not mean it's good for you. And that's a simple truth you have to embrace today, because the devil replaces your emotions with God's word. God's word holds the heaven and the earth. Your emotions cannot even hold one hour without switching. You have a bad day? Go drink coffee. Emotions changed. You have a bad day? Somebody gives you $50. Your emotions go through the roof. Your emotions cannot hold anything. They're like this up and down. And when you begin to put your life on them, instead of the word of God, push the parachute out and say, no, I'm going to go through the thrill. I don't need the parachute. I don't need God's word to tell me who I should be with.  I can do it on my own. My feelings, my heart will lead me. Well, it led you last time, and it wasn't really good.


I can finally say that the 10th season of American Horror Story has begun filming after nine months of halted production. That's right, cameras have begun rolling on the mysterious installment that was supposed to begin filming back in March. And with filming happening, we are starting to get some new details about the season. But before I get into that, I would just like to say that this video was made possible thanks to the support of my channel members. And you too can become a channel member for as low as 99 cents a month and receive early access to videos and exclusive videos every month. Last month's exclusive video was an interesting one where I opened the Sims 4 and made some AHS characters and made them compete against each other. So if you're a member and you haven't seen that one, make sure you check it out because it has some important information about the Discord server. But anyway, let's talk about the leaked working title of season 10 of American Horror Story. And I say leaked in quotations because this tends to happen almost every year. Because AHS likes to keep their real titles a secret, they shoot and have all the production material under a false title. These pretty much leak every year once filming starts to begin and sometimes they have very little to do with what the season's actually about, but other times they're kind of spot on to what the theme of the season is. Okay, so production weekly is this weekly newsletter that lists a bunch of registered movies or TV shows that are filming currently. And just this last week, AHS appeared once again because it has begun filming. This time it was under the working title of AHS Pilgrim. So there's obviously a lot to theorize about what that could potentially mean, and believe me I'm about to do that, but first let me give you some context. This is pretty similar to how the working title of season 8 was leaked back in 2018 with production weekly posting a newsletter with the working title of American Horror Story Radioactive. Only that time that subtitle of Radioactive had actually leaked prior to that because 20th Century Fox had registered the trademark of American Horror Story Radioactive for some reason, and that got leaked. But the season just prior to that, which ended up being called Cult, was filmed under the working title of Koldesack. So this has a little bit less to do with that season's theme than season 8's working title did, aside from the suburban neighborhood setting and the first three letters of Koldesack. But I hope you're seeing that the working title that we did get could potentially be a pretty huge hint towards the season, or it could be a more vague backhanded clue. But now let's theorize about it. So given that the season was originally supposed to be filmed in Provincetown, Massachusetts, and now with the word pilgrim in mind, the obvious connection that must be made is the pilgrims of Plymouth County, Massachusetts, who were English settlers that traveled to North America on the Mayflower and established Plymouth County in 1620. Now contrary to popular belief, Plymouth County was not actually the original landing place of the pilgrims. It was actually none other than Provincetown, Massachusetts. The very town where AHS-10 is potentially meaning to be taking place in. The Mayflower actually found the Cape Cod region, which consists of Provincetown, before settling at Plymouth. So the season's connection to Massachusetts and this working title of pilgrim obviously have something to do with each other. Another interesting aspect of Provincetown's history that I came across was that a certain area of the town once had the nickname of Hell Town. The area may have gotten the name from being a major hub of the fishing industry with hellish working conditions, or during the 1600s, the fishermen began to take up drinking, gambling, and smuggling, which could have also been the origin of that nickname. Now if you're thinking of the AHS timeline, this happens just about 30 years after the real Roanoke colony in North Carolina was found abandoned. So we've not quite been focused in this exact time period in a season of American Horror Story, so I wonder if this working title of season 10 could be a hint that it will be a period piece set in Massachusetts in the 17th century. Or perhaps like Roanoke, it will combine period scenes with modern day scenes as well. Another interpretation of this working title is that it is not a reference to any specific group of settlers, but instead a more figurative meaning of the word pilgrim. The word pilgrim is defined as a traveler or someone who has come from afar who is on a journey to a holy place. So my mind naturally goes back to the witchcraft elements of the American Horror Story lore, and I specifically think of the journey that Michael Langdon went on in the second half of Apocalypse. It was basically his spiritual journey into fulfilling the prophecy of becoming the Antichrist. I am a sucker for the witches, so I would love if season 10 built on the lore of the witches, and I'm very interested of what they were up to in the 17th century. So potentially this season could be about 17th century witches, perhaps journeying across the continent, either in escape from persecution or in pursuit of other witches, or maybe starting an organized coven. I think the early history of witches in American Horror Story has been obviously referenced and very briefly explored, but I would personally love a season that strongly focuses on this. Obviously these elements that I'm theorizing about wouldn't be the only elements of season 10 if any of these turn out to be true. So the heavily speculated ocean, siren, urban legend, body modification theories that I have talked about on this channel could very well still be at play in a season that has these elements in it as well. Obviously there are a ton of possible interpretation of this working title, so please be sure to let me know what it has you thinking of in the comments below. I'd love to know all your theories and give this video a like if you enjoyed it. Make sure you're subscribed for more AHS 10 news and horror related coverage. Thank you so much for watching and I'll see you next time.


Is this thing on? Cool. All right. So I'm Ashish Dixit. I'm here to talk about how you can make a difference and be a productive member of a team. Not necessarily immediately, but pretty quickly by following certain strategies. And this is irrespective of your background. But before we get started on that, let's take a little detour and find out more about me. So I was born and raised in this little country called Nepal. And I was a part of a small middle class family. So we have computers growing up. The first time I actually played with a computer was when I was in school. And I think it was the eighth grade when we started basically having access to computers during computer classes. And I was absolutely fascinated. Like the first time I played with it, I was just giddy with excitement. So I wanted to learn more about how they worked. And then around 2002, I came to the United States as an international student freshman year. I was like, well, you know, I always wanted to learn about those computers. So let's take a CS class and see what's up. So I took a CS class. And doing one of my projects, I actually ended up fixing a bug in my dream and remembered it the next day. So I was like, this thing's pretty cool. I think I want to keep doing it. So that's how I started with programming. But as I took more classes in CS, I was always very concerned that I was learning a lot of new things, a lot of interesting things. But I couldn't see clearly how knowing those things would help me provide value when I went and got a job in the real world, right? So that was always in the back of my head. And the real world happened. Graduated 2006. And two days after graduation, the H-1B work visa at Coda expired for that year. So if you know the immigration laws of this country, there are a lot of fun. So which basically meant companies weren't really looking to hire anyone who needed sponsorship. So I ended up doing like a year gig. I ended up doing just eight months. But I took a gig for a year at Berkman Center for Internet and Society up in Boston. And it was actually cool because it was my first introduction to open source, Ruby, Rails.  Let me install Ubuntu on this. And I never looked back. Well, no, I did have to look back because, again, the immigration laws. So to stay in the United States, I either had the choice of going to grad school and becoming a student again. Or I had to get a job that's sponsored. So that's what led me to a .NET job. The cool thing about this job was that I actually got to code. In my previous job, even though I was hired as a developer, there was way too many administrative tasks that needed to be done during the day and training interns, that kind of stuff. So I was very excited. And I thought I did well. I was fixing bugs, getting to know the code base. They liked me enough that they said, hey, sheesh, I think you should be our ETL developer. And I said, hey, that's awesome. But I know nothing about SQL. They're like, hey, it's OK. You'll learn. So I did. I did a little bit of ETL development with Perl. And then it was not Ruby, but it was close enough to Ruby. The only problem was that the company was known for this methodology that you may not have heard of. It's called crisis-driven development.  And this happens because the company didn't think it was a software company. They had a software product that they were selling to a client, multiple clients, for a lot of money. But they didn't think they were a software company, so they were not invested in the idea. They were not sold on the idea of how software should be built. And it was OK for a little bit. But I was watching the Ruby world from the sidelines. I just started getting very tired, because I would read articles. I would see people talk about how software should be built, write tests, have clear iteration goals, all that stuff. And we were just winging it the whole time. So I needed to figure out an escape plan. So I started looking. And then I came across this job description for Optiva Software Apprentices. And the one thing that caught my eye in the job description was they said that, for this position, we value potential over credential. And I was like, that's great, because I do have potential. I just don't know enough about Ruby and Rails. But I think I could learn this after all. I mean, I learned SQL and Perl and became an ETL developer without no background. So I was like, oh, I'll try this. See what happens. But good old friend Immigration Law came back knocking again. So according to the United States Immigration Law, if you are on H1B visa, you need to be employed for a full-time position. So an apprenticeship, because of the nature of it, you can't expect companies to make it a full-time position. Therefore, even the opportunity was there. It was not something that I could do. Luckily, though, there were other people who believed that I could deliver value as a developer. So I got a job at a company in Baltimore called MDLogix. And I found myself in this situation that I had dreamed of for so many months, like when I was planning this escape plan from the crisis world and the Excel hell. So I got in, and I found myself in this situation of understanding, OK, what are iterations? What agile actually is versus what the neveless agile world? And then how to write tests, all this stuff. And it was great. I learned a lot. And then four or five months after that, I was hired at Groupon. And I've been there for a year now. And it's been an awesome ride. I basically got to do the same thing again. A new team, new environment, new way of doing things, new code base. And then you just get in there, try to figure it out, and then see how quickly you start delivering value to your team. So why am I talking about this? Well, I strongly believe that people want to go to work. And they want to know that they're making a difference. There are different factors that people take into consideration when they're looking for a job. And there are different things that make them happy. But I think at the core, everybody wants to feel like the work that they're doing is helping someone. So that's what it is. And I think the drive to deliver quality work and the desire to improve constantly is a good place to start. I used to think that I needed to know the fundamentals of Ruby. I needed to be well versed in different things that Rails does that make things easier. But what I realized through my experience is that at the end of the day, what really mattered was not what I knew, but how eager I was to learn and how willing I was to be OK with the uncertainty. And if nothing, the one thing that'll get you comfortable with uncertainty is, again, the old friend, the immigration law. So the other reason I also wanted to talk here is because I actually want to start a conversation around this. Yes, I'm speaking to you in this 20-minute slot, but I don't want it to end here. I want people who are in that situation where they feel like they have the potential and they have an opportunity to sort of see this and try out some of the strategies that we're going to discuss in a little bit here and see how it works for them or talk about other strategies that they have employed that has been successful and have more people talking about this stuff. I also want to start a conversation among people who are more experienced, who are working with these new developers coming in. And I want them to sort of see what kind of mindset they're coming in with, what kind of struggles, like mental that they have to work through, and basically be better prepared to understand the new developer coming in with limited background and then have enough information to help them make the most of the formative six months. That is when you start at a new team, right? So let's start with some of the strategies. I think the first thing you want to do is, yes, there are a lot of things that you don't know when you first start out, and it's kind of overwhelming because the list of things that you need to learn keeps piling up and up and up, but rather than focusing on things that you don't know, you should focus on, well, what are the things that I do know? What are the things that I could bring? What do I bring to the table, a value proposition? So one of the best things coming in with no preconceived notions into a code base is that you can look at something and you're like, this does not make sense. Why are we doing this? Because you don't have the preconceived notion. You're not used to that code being there, and you've not accepted that as a new person. You're in a great position to identify stuff like that. The one thing is that you have to bring light to the situation, so you have to speak up, just be like, hey, this does not make sense. Why are we doing this way? Why can't we approach it this way? But do it in a way that have a positive outlook about it. Don't have some empathy for whoever wrote that code and try to understand what context it was written. Maybe there are certain constraints when it was written that are no longer valid. The other thing that you want to do is you want to leverage the skills that you've already have. Maybe you had a strong JavaScript background before coming into this new gig. Or maybe you did a lot of ops work for your previous company and you know your way around the Unix shell better than most people. Or maybe you have really strong speaking skills or writing skills. All these skills are valuable things that your new company and your new team could stand to benefit from. So definitely find opportunities where you could use these skills and then help your team basically achieve their goal in whatever way the goal may be. The only trick is to be cognizant that your skills should not be the hammer and everything shouldn't be the nail. Don't try to force just the stuff that you know onto everything. So I think Corey Haines was here, was responsible for this picture, although I found it somewhere else. But outside of the very sad possibility of making Pandas sad, I think pairing also allows you to give a great introduction to, give a new person a great introduction to not just the code base, but the domain of the app. And it allows a very interactive, engaging conversation on your first day. When you're going through the code and you get to ask questions, you get to play around with the code, the console. And it's really a great way to sort of get your feet wet with the app and then know where things are basically. The other awesome thing that it allows is that it enables the new person coming in to not worry about syntax. They could focus on the problem that they're trying to solve. And they can just not worry about like, oh, I don't know the syntax for this. That's secondary, because you could just look at the problem and you're like, okay, if I were to do it in pseudocode or whatever, I'll do this, I'll break this problem into these little pieces. And here's how I arrived at the solution. You could just talk it out with your pair and then with your pair's help, write the line of code that actually implements that solution. But what that does is, it gives you the opportunity to learn the syntax as you go, but it also engages you like very early on in problem solving and it builds confidence. You get excited when you're coming up with these solutions. You're already delivering value and you don't even know the syntax yet. And I think that's awesome. So once you've kind of figured out like your way around the code, like you have some idea for where things are, I think it's a great opportunity to take time and sort of take things on your own. Like just go for a little adventures here and there. And the best adventures are squashing bugs. Bugs, we try and always say like, oh, we have to minimize bugs, but bugs are absolutely the best friend for a new developer. And you should ask to be on bug fixing duty because it allows you the opportunity to test the knowledge that you gathered from the earlier phase when you're pair programming with your team and see how truly do you understand. And then when you're trying to figure out how why the bug is happening, maybe you'll discover something else. Some part of the code base they weren't sure of. It's just a very good way to start working on that quickly and then on your own pretty much. And then definitely ask for help, even though if you're on your own, don't feel like you actually have to figure everything out. The reason you're on a team is you could lean on each other. Not everyone has to be an expert. You're not expected to know everything. So even though it's tough to ask for help, they'll be like, oh, you know, like, yeah, I feel like I should know this, but I don't is a good way to start. But definitely ask for help. The only thing I would say is like, when you're asking for help, and I struggle with this initially a lot, is to at least take time and try different things. And at least from the person you're asking, like, see it from their perspective and make sure you've exhausted all possibilities of things you could try before asking them a question. Because if you do that, then you at least get more benefit out of that exploration phase of when you're confused, working with something. So again, like, you've been at a job for like a couple of weeks now, maybe three weeks, like squashing bugs, and it's been great. And you're asking a lot of questions, and you're finding out about all these things. And that's a great time for you to then be like, okay, let me start working on some stories. And the cool thing about stories is like, just like bugs, it forces you to go explore certain areas of the application, test the knowledge. But then it also like cultivates ownership. Like now you have a piece of the application that you've shipped. And that's exciting. That's exciting that like something you built is making someone's life easier somewhere, right?  There are things to watch out though, or at least one particular thing. We hear a lot of conversations around code quality, elegant code, like proper design, all that stuff. And they're important and it's good to keep that in mind.  And it's okay, everybody does. Like don't feel like the code that comes out of your hand has to be this beautiful, elegant piece immediately.  Let it actually do what it's supposed to do. And then you're in a better place to make it better. So you've been working on bugs, you've been working on some features, now you're like in a very good position to start like actually improving. At this time you should probably be like fairly comfortable with the app and you know your way around. So like this is a great time for you to start improving your workflow, your tools and then maybe understand more of like the stack, the technology stack. One of the good things that you can do to get started with improving is just like automate your workflow, pay attention to what you're doing and then just try and find ways where you could improve, like shave off like a couple of steps in what you do fairly regularly. So at Groupon, when we were at my team what we used to do was we follow the GitHub flow.  And so what we did was like, well let's just write a little bash script and see what happens. So now we have a little bash script that just pushes your code to GitHub and opens your browser in the pull request window ready for you to just click create. And it was not like too bad and it was not that big a deal but like now 15 or so people are using it and more people if they know about it they'll probably like it too. So stuff like that, just find ways to make your daily lives better. One-on-ones, they are awesome. Definitely try and talk to your team lead or your manager constantly, like fairly regularly to try and get feedback because they're in a very good position to tell you how well you're doing and what areas that you could use improving. I highly recommend. And then especially if your focus is on improvement it's a great way to have that feedback. Like every week you have or every month however regular you wanna make it. You have someone saying, you should rework on this this time around and then it's great. Like you're improving every day. Communication. Language inherently is very ambiguous and what that leads to is sometimes like your understanding of the sentence versus the other person's understanding of the sentence is completely different. And especially when you're new to the domain it's very important to clarify your understanding of the acceptance criteria for the story you're working on. Not just because of the potential ambiguity of English language but because you're new you may not know like external dependencies. There might be certain APIs that might have to be built like. So definitely communicate with your teammates like, hey, so this is what I think I need to do. Is there anything that I need to be aware of? Do I need to send someone an email to have some API endpoint be created and is there any possible ways that this could go wrong? So it's always important. And the other thing about communication, which again I'm slowly trying to improve on is to try and distill it to the core essence of what you're trying to say and give them enough context but let them ask for details. Don't overwhelm with all the details at once because they can't process all that information. Utilize the available resources that are around you. The sheer knowledge among your team is a great place to start. Like if you've always been interested in closure and someone's doing closure at work, that's a good place for you to get your feet wet and then kind of lean on them and then learn that. It doesn't have to be study groups either. It could be meetups locally or like within your company that you could go to. There are various other things. I mean training programs, companies might do training programs internally. So whatever resources are available, definitely take part in those and try and get as much out of them.  So it's a great time to take a breath and then look back and then congratulate yourself and then thank the people who've been part of the journey. It's also a great time to start thinking about how you can pay it forward. And there are different ways you could do it. With startups like Code Academy, with initiatives before like Ruby Mencon University, there are a lot of places where you could do mentorship. So that's definitely one thing to do. You could write blog posts, speak at conferences, that sort of stuff as well. There are definitely other strategies. You could, I think one of the biggest ones is side projects which I think Dave Hoover in his book explains as breakable toy, which allows you to try different ideas in the safety of a simple app. I highly recommend this book by the way for anyone who's trying to improve. And again, I'm pretty sure there are other strategies. If you have a strategy on your own, let me know. I'm $20.45 on Twitter. And I'm Ashish at groupon.com. So that's all I got. Do you have any questions? Okay. You can't do the questions right now. All right. Leon.


Hello and welcome to 90s Month. We will be looking at G.I. Joe toys released in the 1990s and since the 90s was the extreme decade We will be looking at G.I. Joe extreme No, no, this figure is not from G.I. Joe extreme. This is from 1993. We're not quite extreme yet. In 1993 G.I. Joe was mega 90s Month continues with our first look at the mega marines We're commander 788 here We're commander 788 here and welcome to the second review of 90s Month Yes, October is the month of Halloween and Halloween is filled with lots of Spooks and ghouls and that is pretty extreme Mega so this week we are going to look at mega marines gung ho the mega marines were introduced in 1993 And were only available that year. They added yet another science fiction element to G.I. Joe They also tried to capitalize on the neon colors that were popular at the time gung ho is also one of my favorite characters I really loved the first version of gung ho in 1983. This figure also came with a special bonus feature Play-doh, I mean moldable bio armor Mega seriously though. It's play-doh. Oh, but this isn't just any play-doh though I bought this particular figure because its canister of play-doh had never been opened. It was still sealed This is 24 year old play-doh. Do you want to see what 24 year old play-doh looks like? Well, you're gonna see it and I can tell you right now. It's mega Let's look at the final vintage version of G.I. Joe's first marine gung ho This is the 1993 G.I. Joe mega marines commander gung ho This is the fifth version of gung ho. It was available only in 1993. It was discontinued for the year 1994 mega marines was a sub team within G.I. Joe created in 1993 to fight against mutant Mega monsters created by dr. Mindbender the mega monsters were mutated Cobra troops Why was G.I. Joe fighting mutants in the 1990s? Let's see. What else was popular at that time? Yeah, this is another example of Hasbro chasing trends the mega marines had only one vehicle the monster blaster APC I did a video unboxing and assembling the monster blaster and I have to admit It's a pretty cool vehicle why mega marines gung ho was a marine so that makes sense He's the mega marines leader, but the mega marines also included clutch and he was not a marine So if the mega marines include nonmarines, why are they called that most likely answer? Aliens the 1986 movie featured the colonial marines They were really cool and badass and Hasbro wanted G.I. Joe to be like that Except Hasbro had already done a colonial marines ripoff with battle force 2000 in 1987 also the colonial marines did not wear neon colors They look like real futuristic military. That's one of the things that made them look cool So Hasbro has badly missed the mark here So why wasn't G.I. Joe's other prominent marine from the 1980s a leather neck a member of the mega marines? Well, that's because in 1993 leather neck was a little busy hunting giraffes I'm not gonna say giraffe trousers leather neck is the worst thing ever But you could say it I won't stop you version one of gung ho was introduced in 1983 the second year of 1980s G.I. Joe version two was released in 1987 wearing u.s. Marine Corps dress blues version three of gung ho was released in 1992 there were two versions of gung ho from 1993 I don't have version four, but that was just a reuse of the mold from version three in different colors Version five was the mega marines version version one was famous for having a chest tattoo of the Marine Corps emblem Version two was wearing a dress uniform. So of course the tattoo was covered up Version three makes the tattoo on the chest smaller. That's not how tattoos work. They don't just move around Version two removes the tattoo entirely version five again has the tattoo covered up I missed the tattoo. It was one of gung ho's defining features. Let's take a look at the card for gung ho I have the full card back this time and I have to say the artwork is not good The proportions are off the left arm holding the gun looks too small And it doesn't look like it bends in the right place His head is just sort of floating above his shoulders It has instructions in the space behind the figure based on this It looks like the bio armor is supposed to be used for the missiles as well We'll take a look at that later I like this part play dough modeling compounds sold separately can be used in addition to moldable bio armor We are really trying to sell the idea that this moldable bio armor isn't really just play dough Oh, sure. You could use play dough too. I mean you could steal it from your younger sister or something But moldable bio armor has GI Joe on the lid It's like calling a doll an action figure so boys would buy it flipping the card around to the back We have the other mega marines and the mega monster enemies oddly Dr. Meinbender is not included in this even though it mentions dr. Meinbender in the description And there was a new version of dr. Meinbender in 1993 But it was not in the mega marine series the figures are numbered which makes no difference since you don't have to buy them in any Particular order the figures also have numbers on them, but those numbers do not correspond with the numbers in the series So who cares we have some battle core figures here and we have the file card the file card is neon green and quite ugly But it isn't as hard to read as the salmon colored file card for supersonic fighters rock and roll Let's take a look at the accessories starting with the helmet of the helmet is orange It looks like a firefighters helmet It has a microphone and a flap on the back this helmet is totally unsuitable for combat It doesn't fit on the figures head very well look at this It pops off you press it on and it pops right back up not a fan of the helmet So let's look at the spring-loaded missile launcher also in that orange color I do not have the figure holding this because it does not fit in its hand very well A lot of 90s figures came with these spring-loaded missile launchers This one is not original to gung-ho it came with a couple other figures in 1993 and in almost the same color With this bright orange color gung-ho is really trying to make sure his enemy can see him This is intended to be slung under the figures forearm the hand goes through this opening and the grip is on the top It came with two black missiles and it could be operated by placing the missile in the missile launcher with the notch side down Slide it in until it clicks And then the trigger is here on the bottom. Let's test the missile launcher by taking out dr. Mindbender Let's look at the bio armor mold and this works with the main gimmick on the figure This is used to mold the Play-Doh onto the figure and it also molds warheads on the missiles So we'll look at that this of course works with the moldable bio armor That came in a black canister with a red lid and a silver label It is sealed with tape when I purchased this toy this canister of Play-Doh had never been open This is 24 year old never used before a Play-Doh This is what makes this review special what other GI Joe reviewer would dare to open 24 year old Play-Doh and show you what it looks like. Are you ready for this? Let's pop the cap off the canister and There it is This is 24 year old Play-Doh. It is hard It's completely solid except some parts have been crystallized it has crumbled a bit But it certainly doesn't look anything like Play-Doh. It's more of a rock It tastes surprisingly kind of minty Well, we can't test the bio armor mold with this So I got a fresh can of Play-Doh in red since that seems to be the color the original was So we're gonna use this to test out the bio armor mold This is supposed to be really easy You just take some Play-Doh and put it in the back half and then take a little bit more Play-Doh and put it in the Front half and then you press this on the figure the instructions say to point the arms straight out and to press the mold Haves Together on the figure I can already tell this is going to be excess so I'm gonna take this off now Let's pop this mold apart and see how the bio armor looks and There is the moldable bio armor.  He might as well carry a sign that says shoot me In fact, I'll bet you could carve that into the bio armor there fixed it I know with this Play-Doh armor you can simulate battle damage But I'm mainly concerned with getting it off the figure without leaving any bits of Play-Doh in the crevices This bio armor mold also makes a warhead for the missiles So let's demonstrate that place the missile in and squeeze the mold halves together now pull it apart And we'll need to remove the excess There we go now. Let's see how this fires with a Play-Doh warhead on it. All right. Once again Let's take out dr. Mindbender. It's still fires fine. It doesn't make much difference though The rest of the accessories came on this black accessories tree The two black missiles were on here as well none of the accessories that were on this tree were exactly original But there were some differences from the original issues This machete is very similar to the machete that came with muskrat and was later Recolored and packaged with a lot of other figures including Colonel courage and robo-joe The mold was slightly altered from the original, but I don't know why they bothered it is still mostly the same this submachine gun originally came with tracker from 1991 and was reused many many times This rifle originally came with grunt version 3 from 1991 but the rifle that came with grunt had two holes bored into the side So it would connect to his missile launcher. This shotgun originally came with muskrat from 1988 And it is very similar to that original muskrat shotgun only minor differences in the details Let's take a look at the articulation for gung-ho. He had the articulation that was standard for gi Joe figures by 1993 meaning he could turn his head from left to right and look up and down He could swing his arm up at the shoulder about so far and swivel at the shoulder all the way around He had a hinge at the elbow so he could bend at the elbow about 90 degrees He had a swivel at the bicep so he could swivel his arm all the way around The figure was held together with a rubber o-ring that looped around the inside that allowed him to move at the torso a bit He could move his legs apart about so far He could bend his leg at the hip about 90 degrees and bend at the knee about 90 degrees Let's look at the sculpt design and color of gung-ho version one of gung-ho was one of my favorite figures from 1983 I thought version two while not having much play value was a fitting tribute to the Marine Corps Everything after version two though does not work for me Of course the first version looks a bit silly in hindsight with the open vest and tattoo But I still liked it that figure started a lifelong fascination with the US Marine Corps Later versions though just don't look like gung-ho to me. Let's look at his head He has a bald head and a mustache a black mustache even though his original mustache was brown Gung-ho was always bald but in version one he had his Marine Corps utility cover Later versions took his hat away leaving his head looking like a cue ball Give the man his dignity let him have his hat on his chest He has bright yellow shoulder pads and a yellow bandolier with orange pouches He had to have pouches because it was the 90s and Rob Liefeld was popular on his chest He has a black circle with a sculpted number one on it on the card art that one is yellow But there is no yellow paint on the number on the figure I have mixed feelings about this the number is an unpainted detail Which is usually a problem for me But the yellow number on the card looks like something out of Sesame Street So it's a wash on his arms He has yellow shoulder coverings which conveniently stop at the arm swivel so they don't have to be painted There's still some Play-Doh gunk in there that stuff is impossible to get out He has green sleeves with yellow forearm pads and gloves and the detail on the forearm pads and gloves is not bad If they were in a different color, they would be great on his waist piece He has that green and black camouflage again pretty good But then he has a bright yellow belt and crotch covering on his legs We see green trousers with more of that black marbled camouflage pattern Man, they could have done something with that if they hadn't covered it up so much He has thigh straps sort of they're kind of big thigh coverings on the left side He has a pouch which to the file card calls a survival slash medical kit The paint mask on the thigh straps isn't too good Some of the yellow paint spills over to the leg detail that's poor quality control He has tall yellow boots that go up to his knees and he has a square knife on his right shin The detail on these boots is really pretty good but I have another big problem with him Because there is no paint on the lower legs there is a color mismatch between the green thighs and the yellow knees And that is very obvious when you bend the knee That looks very ugly and I will always have a problem with this Let's take a look at Gungho's file card and this is one of those 90s file cards that has a list of the features on the figure I am not going to read through those I'm going to focus on the character of Gungho His codename is Gungho and he is the mega marine leader since he was GI Joe's first marine I have no problem with that File name is Etienne Arlafit Primary military specialty is bio military expert Secondary military specialty heavy weapons In contrast on his original file card from 1983 his military specialties were Rekondo and jungle warfare training instructor His grade is E9 sergeant major and that is a promotion from his version 1 file card that had him as an E7 But like rock and roll that promotes him over Duke who in 1992 was still an E8 master sergeant I do want to see Gungho get promoted But I also prefer Duke to be the highest ranking non-commissioned officer on the team I think his role on the team should be reflected in his grade We have a quote here presumably from Gungho himself It says this isn't just another bug hunt it's war Well the bio viper is kind of bug like so I guess that could be the bug hunt he's talking about But the monstro viper isn't a bug This paragraph says born on the bayou Born on the bayou Gungho's background in hostile environments and experience in the U.S. Marine Corps made Him a natural choice to command the mega marine forces Gungho knows you can never be sure where or when a mega monster will turn up So you have to be prepared at all times At all times He demands that his mega marines sleep with one eye open That way they won't think it's just a nightmare they're having when the mega Monsters really attack Is that meant to be literal because if so it sounds dumb Even if you could force yourself to sleep with one eye open That doesn't mean you're conscious and aware of what's going on Gungho is known for his effectiveness in neutralizing the most dangerous enemies A skill that will be put to the test fighting these genetically enhanced creeps Lot of music references in this one Looking at how Gungho was used in G.I. Joe media He appeared in the very first G.I. Joe cartoon in 1983 He wore his version 1 uniform for that He appeared many times in the original series But he never appeared in his mega marines uniform As far as I can tell he didn't appear at all in the Deke animated series in the 1990s Which is unfortunate He was mostly forgotten after his brief appearances in the 1987 animated movie His next animated appearance was in Valor versus Venom Which is outside the scope of this review In the G.I. Joe comic book by Marvel Comics He was introduced in issue number 11 Along with a lot of other characters from 1983 I can't find a reference for this version of Gungho in the comic book either So I guess that makes the media section of this review easy Awesome Party time Looking at mega marines Gungho overall It has playdough Now there's nothing wrong with playdough Lots of kids played with playdough I played with playdough It's a fun toy It's a fun toddler toy Take a look at the age of the kids playdough was marketed to This is not the age group for G.I. Joe That kid can't play with G.I. Joe because he would eat the small pieces Here's my theory about kids No kid other than a toddler wants to be treated like a toddler But imagine mega marines Gungho without the playdough How does the figure hold up? Well the sculpting is pretty well done In fact I would say the 90s was a great era for sculpting on G.I. Joe figures I've heard some G.I. Joe pundits say we should ignore the hideous colors and focus on the sculpting No The color scheme was an artistic choice There is no reason to ignore it The designers will be graded on the whole project Not just part of it The base color of the figure is pretty good I'd go so far as to say the camouflage pattern is brilliant But it is totally lost behind the day glow yellow I want to hate the mega marines too This is yet another example of Hasbro chasing the trends that were popular at the time And I can't help but detect a hint of resentment at their competitors In the fact that the mutants are the enemies of the mega marines I don't hate the mega marines though The mega marines actually make a pretty compelling self-contained narrative You have a mad scientist that turns people into monstrous mutations And you have a squad of specially equipped soldiers that has to hunt them down in one bad ass vehicle That's not bad You could do something with that Just not in G.I. Joe As I've said before, the essence of 80's children's entertainment Was the fantasy universes in which they existed Transformers had a universe He-Man had a universe G.I. Joe had a universe And in each of those universes, there were rules Everything that happens in those universes has to make sense Because if it doesn't, it breaks the fantasy From the very beginning of the real American hero line Great efforts were made to give it a sense of military authenticity With a few science fiction elements thrown in to spice it up The file cards were filled with real world references They told us G.I. Joe existed in a world of very much like ours With a few differences This wasn't He-Man There's nothing wrong with He-Man But this wasn't He-Man This was G.I. Joe As the line went on, they stretched those rules You can decide yourself where the breaking point was For me, the breaking point was Cobra Law in 1987 And the Mega Marines are way past the breaking point They're just too mega I'll punctuate that point by leaving you with the words of Larry Hama From the forward of Mark Belomo's Ultimate Guide to G.I. Joe Volume 2 What I have attempted vainly to impress upon the unnamed Nabobs of industry Is the importance of the totality of interconnecting internal agreements That compromise the solid base upon which even the most absurd fantasies stand upon In other words, it's all gotta jibe, dude Those words to me are mega And they are the essence of my objection to the Mega Marines and Cobra Law And all the other silly elements that were added to G.I. Joe Even if they would have been fine on their own They don't fit in the universe you were trying to force them into That was my review of Mega Marines Gung Ho I hope you enjoyed it If you did, make sure you like it on YouTube And subscribe to the YouTube channel And share the video to help this channel grow Find me on Facebook, Twitter, and Patreon 90s Month continues next week I'll see you there and until then remember Only G.I. Joe is G.I. Joe


Welcome back, last class we have seen the advantages of fiber and its role in health. And the carbohydrate and fiber where the major nutrients though not essential nutrient because the energy can be given by the other nutrients. So, today we will let us see about the protein which is again a major nutrient and a very important nutrient. So, the term protein was first suggested by Bersilius and he described a complex organic nitrogenous substance found in animal and plant tissue. So, proteins are essential nutrients for the human body and they are one of the building blocks of body tissue and they also serve as a fuel source or the source of energy to the body. Protein is called a macronutrient because it is essential for providing energy and as well as it is important for body building maintenance and repair of worn out tissues. And this is made up of building blocks called amino acids and our body has 22 types of essential amino acids in order to function properly. There are hundreds of amino acids out of which 22 are essential for keeping the body fit. So, it can make 13 of them that means the body can synthesize 13 of the amino acids using the other material. But the other 9 have to be obtained from the food essentially so that we stay healthy that is why they are called as essential amino acids. They have to be essentially provided through diet. The 9 essential amino acids which human must obtain from the diet in order to prevent protein energy malnutrition are phenylalanine, valine, thionine, tryptophan, methionine, leucine, isoleucine, lysine and histidine. And all these 9 essential amino acids are present in animal foods. But when you take the plant foods there are some deficient amino acids out of these. Therefore, when all these 9 essential amino acids are present in a food it is called a complete protein. That means it has the function of body building, repair and maintenance whereas when something is deficient we have to supplement the amino acids. Now, types of proteins there are 2 types of proteins one is complete protein and the other one is incomplete protein. As I told you complete protein is found in animal source and plant source, when we take food from plant sources we have to combine 2 foods which are having the incomplete protein so that we get all the essential amino acids and make it a complete protein. So, there are some plant based foods including quinoa and soy which are complete proteins. So we can see here all the animal foods these are supposed to be the sources of complete proteins. Incomplete proteins are present in cereal grains and pulses. So the cereal grains they are deficient in the amino acids lysine and threonine whereas these are rich in the pulses and pulses are deficient in tryptophan and methionine which are again rich in the lysine and threonine. Therefore when we combine cereals and pulses together it becomes a complete protein that is how we have to supplement the foods to get plant foods as complete protein. And there are many excellent sources of the vegetarian protein like milk, the paneer and cheese then the you have when you make some foods combining cereals and pulses then the beans, flaxseed, then the pumpkin seeds, the sunflower seeds, hemp seeds same all these are the vegetarian protein which are good sources. If you see the protein content of some of the foods the cereals provide 6 to 14 grams per 100 grams of cereals and legumes provide 18 to 24 grams and that is why when you combine cereals and legumes you cannot combine as 1 is to 1 because the quantity of protein present in legumes is much more than the cereals. Therefore it can be combined cereals is to pulses can be combined in the ratio of 4 is to 1 and soybean contains 43 grams per 100 grams of protein. So this is the richest source among the vegetable sources and this is again a complete protein. Then nuts and oil seeds also contain 18 to 40 grams per 100 grams, oil seed meals after taking out the oil it becomes richer in protein. So you have 45 to 55 grams of protein in oil seed meals. Then hence egg contains 12 to 13 grams but this is a complete protein then milk also is a complete protein. So generally we call milk and egg protein as reference proteins. So we take reference from the egg and milk and compare with the other foods. Then fish contains 18 to 20 grams and meat and liver contains 18 to 22 grams of protein. Now functions of protein so main function is the body building and then when you do not supply sufficient amount of carbohydrates it acts as a source of energy. Then proteins are part of enzymes so they act as enzymes. Then proteins help as carriers for example hemoglobin in the blood hemoglobin is a combination of iron and protein therefore it acts as a carrier then for it acts as a buffer. So to maintain the acid based balance proteins act as buffers. Then protein act as lubricants and they are also important for immune system and they help in protection against disorders. Therefore the functions of proteins are very important and we generally have protein for body building right from the infancy and if you see the infants they have milk as their main food which is rich in protein and the baby grows from 2 to 3 kgs to 60 kgs when it comes to an adult. So that important is the protein. Thank you.


from San Jose in the heart of Silicon Valley. It's theCUBE, covering DataWorks Summit 2018. Brought to you by Hortonworks. Welcome back to theCUBE's live coverage of DataWorks here in sunny San Jose, California. I'm your host, Rebecca Knight, along with my co-host, James Kobielus. We're joined by Pandit Prasad. He is the analytics product strategy and management at IBM Analytics. Thanks so much for coming on the show. Thanks, Rebecca. Glad to be here. Why don't you just start up by telling our viewers a little bit about what you do in terms of, in relationship with the Hortonworks relationship and then the other parts of your job? Sure. As you said, I am in offering management, which is also known as product management for IBM. Manage the big data portfolio from an IBM perspective. I was also, I'm also working with Hortonworks on developing this relationship and achieving that relationship. So it's been a year since we announced this partnership. We announced this partnership exactly last year at the same conference, and now it's been a year. So this year has been a journey in aligning the two portfolios together, right? So Hortonworks had HDPE, HDF. IBM also had similar products. So we have, for example, BigSQL. Hortonworks has Hive. So how Hive and BigSQL align together? IBM has a data science experience where does that come into the picture on top of HDPE?  So what this year has given us is more of a solution sell. Now with this partnership, we go to the customers and say here's an end-to-end experience for you. You start with Hadoop, you put more analytics on top of it. You then bring BigSQL for complex queries and federation virtualization stories. And then finally, you put data science on top of it. So it gives you a complete end-to-end solution, the end-to-end experience for getting the value out of the data leak. Now, IBM, a few years back, released a Watson data platform for team data science with DSX data science experiences, one of the tools for data scientists. Is Watson data platform still the core, I would call it DevOps for data science and maybe that's the wrong term, that IBM provides to market or is there a broader sort of a DevOps framework within which IBM goes to market these tools? Sure, so Watson data platform one year ago was more of a cloud platform and it had many components of it. And now we are getting a lot of components onto the on-prem world and data science experience is one part of it. So data science experience. There's Watson analytics as well for subject matter experts and so forth. Yeah, so, and again, Watson has a whole suite of services-based offering. Data science experience is more of a particular aspect focused specifically on the data science and that's been now available on-prem and now we are building this on-prem stack. So we have HDP, HDF, big SQL data science experience and we are working towards adding more and more to that portfolio. Well, you have a broader reference architecture and a stack of solutions around AI on power and so forth for more of the deep learning and development and so forth. So in your relationship with Hortonworks, are they reselling more of those tools into their customer base? I mean, to supplement instead, they already resell through with DSX or is that outside the scope of the relationship? No, it is all part of the relationship. So this has been, these three has been the core of what we announced last year and then there are other solutions like we have the whole governance solution, right? So again, it goes back to the partnership HDP brings with it Atlas. So IBM has a whole suite of governance portfolio including the governance catalog. So how do you expand the story from being a Hadoop centric story to an enterprise data like story, right? So, and then now we are taking that to the cloud and that's what Truada is all about, right? So Rob Thomas came out with a blog today morning talking about Truada and that is, if you look at it, it is nothing but government data like hosted offering if you want to simplify it. So that's one way to look at it and it caters to the GDPR requirements as well. For GDPR, for the IBM-Hortonworks partnership is the lead solution for GDPR compliance? Is it Hortonworks data steward studio or is it any number of solutions that IBM already has for data governance and curation? Or is it a combination of all of that in terms of what you as a partner has proposed to customers for, you know, Supernet's GDPR compliance. Give me a sense for- Yeah, it is a combination of all the above. So it has HDP, it has HDF, it has a big sequel, it has data science experience, it has IBM governance catalog, it has IBM data quality and it has a bunch of security products like Guardium and it has some new IBM proprietary components that are very specific towards data anonymization and how do you deal with the personal data and sensitive personal data as classified by GDPR, right? So I'm supposed to query some higher level information but I'm not allowed to query deep into the personal information. So how do you block those queries? How do you understand those? You know, these are not necessarily part of Data Stewards Studio. Yes, yes. These are some of the proprietary components that are thrown into the mix by IBM. You know, one of the requirements that's not often talked about under GDPR and Abbas Ricky of Fort Worth's got into it a little bit in his presentation. There's a notion that, or the requirement that if you are using an EU citizen's PII to drive algorithmic outcomes that they have the right to have full, they the PII subject has a right to full transparency into the algorithmic decision paths that were taken, you know, whatever it might be. Now I remember IBM had a tool under the Watson or under the Watson brand that wraps up a narrative of that sort. Is that something that IBM still, it's called Watson Curator is something a few years back. Is that a solution that IBM still offers? Because I'm not getting a sense right now that Hortonworks has a specific solution, not to say they may not be working on it, that addresses that side of GDPR. Are you know what I'm referring to there? I'm not aware of something from the Hortonworks side beyond the data storage studio which offers basically identification of what some of the data lineage as opposed to model lineage. It can identify some of the personal information and maybe provide a way to tag it and hence mask it. But the Truada offering is the one that is bringing some new research assets after the GDPR guidelines became clear. Then like we got into the effort of how do we cater to those requirements. So these are relatively new proprietary components. They are not even being productized. So that's why I'm calling as proprietary components that are going into this hosted service. IBM's got a big portfolio, so I'll understand if you guys are still working out exactly what the position is. So Rebecca, go ahead. I just wanted to ask you about this new era of GDPR. So the last Hortonworks conference was sort of before it came into effect and now we're in this new era. How would you say companies are reacting? Are they in the right space for it in the sense of they're really still understanding the ripple effects and how it's all going to play out. But how would you describe your interactions with companies in terms of how they're dealing with these new requirements? They are still trying to understand the requirements and interpret the requirements coming to terms with what that really means. So for example, I met with a customer.  They have data centers across different geos. And they asked me, I have somebody from Asia trying to query the data. So that the query should go to Europe. But the query processing should not happen in Asia. The query processing all should happen in Europe and only the output of the query should be sent back to Asia. Like you won't be able to think in these terms before the GDPR guidelines got issued, so now. It's exceedingly complicated. But do you coupling stories from processing enables those kinds of fairly complex scenarios for our compliance purposes? Yeah, so it's not just about the access to data. Now we are getting into even where the processing happens and where the results are getting displayed. So we are getting into. You may be severe penalties for not doing that. So your customers need to keep up. There was an announcement at this show at DataWorks 2018 of an IBM Hortonworks where solution, IBM solution, IBM hosted analytics with Hortonworks. I wonder if you can speak a little bit about that, Pandit, in terms of what's provided as a subscription service to, if you could tell us what subset IBM's analytics portfolio is hosted for Hortonworks customers. Sure, as you said it is a hosted offering. Initially we are starting that off as a base offering with three products. It will have HTTP, big SQL, IBM DB to big SQL, and DSX, data science experience. Those are the three solutions. Again, as I said, it's hosted on IBM cloud. So customers have a choice of different configurations they can choose, whether in VMs or bare metal. Again, I should say this is probably the only offering as of today that offers a bare metal configuration in the cloud. So it's for data, it's geared to data scientists, developers and machine learning models that will train, will build the models and train them in IBM cloud. But in a hosted HTTP, in IBM cloud, is that correct? Yeah, so I would refresh that a little bit, right? So there are several different offerings on the cloud today. And we can think about them as, as you said, for ad hoc or ephemeral workloads, also geared towards low cost. So you think about this offering as taking your on-prem data center experience directly onto the cloud. So it is geared towards a very high performance. So the hardware and the software, they are all configured, optimized for providing high performance, not necessarily for ad hoc workloads or ephemeral workloads. They are capable of handling massive workloads on sticky workloads, right? So it's not meant for like, I turn this massive performance computing power for like a couple of hours and then switch them off. But rather, I'm going to run this massive workloads as if it is located in my data center. That's number one. It comes with the complete set of HTTP. So if you think about it, there are currently in the cloud, you have, you know, I have the Hive and HBase as SQL engines and the storage separate. You know, the security is optional, governance is optional. And so this comes with the whole enchilada, right? So it has security and governance all baked in. It provides the option to use big SQL, right? So for, because once you get onto the Hadoop, the next experience is to I want to run complex workloads. I want to run federated queries across Hadoop as well as other data stores. How do I handle those? And then it comes with data science experience also configured for best performance and integrated together as a part of this partnership. So I mentioned earlier that we have progress towards providing the story of an NTN solution. So the next steps of that are like, yeah, I can say that it's an NTN solution, but are the products look and feel like as if they are one solution. So that's what we are getting into. And I will feature some of those integrations. So for example, big SQL IBM product, we have been working on it, baking it very closely with HDP, right? So it can be deployed through a body. It is integrated with Atlas and Ranger for security and we are improving the integrations with Atlas for governance. And so say you're building a smart, a spark machine learning model inside of DSX on HDP within IHAH, IBM hosting links with Hortemarks. On HDP, HDP 3.0, can you then containerize that machine? That's what I was going next. And then deploy it into an edge scenario? Sure. So that's what I was going to ask. First was big SQL. The next one is DSX. So DSX is integrated with HDP as well. So we can run DSX workloads on HDP before, but what we have done now is if you want to run the DSX workloads, like I want to run a Python workload, right? So I need to have Python libraries on all the nodes that I want to deploy. So suppose you are running a big cluster, 500 cluster. So I need to have Python libraries on all the 500 nodes and I need to maintain the versioning of it. If I upgrade the versions, then I need to go and upgrade, make sure all of them are perfectly aligned. In this first version, will you be able to build, say, a spark model and a TensorFlow model and so forth and containerize them and deploy them across a multi-cloud and orchestrate them with Kubernetes and to do all that magic. Well, is that a capability now or in the future within this portfolio? Yeah, we have that capability demonstrated in the pedestal today. So that is a new one, that new integration that we are around saying. So we can run virtual, we call it as virtual Python environments, right? So DSX can containerize it and run that as workloads in the HDP cluster. So now you are making use of both the data in the cluster as well as the infrastructure of the cluster itself for running the workloads. In terms of the layer stack, is it also incorporating the IBM distributed deep learning technology that you've recently announced, which I think is highly differentiated because deep learning has increasingly become a set of capabilities that are across a distributed mesh playing together as if they were one unified application. So is that a capability now in this solution or will it be in the near future? Which one? DDL distributed deep learning? No, we have not gotten that yet. I know that's on the power, AI on power platform. That's what we'll be talking about next year's conference. Yes, that's definitely on the roadmap. We are starting with the base configuration of bare metals and VM configuration. Next one is depending on how the customers react to it. Definitely we are thinking about, okay, bare metal that is optimized with GPUs, optimized for TensorFlow workloads, right? Exciting, we'll be tuned in coming months and years. Indeed, we will. I'm sure you guys will have that in there. Thank you so much for coming on theCUBE. We appreciate it. Great, very good. I'm Rebecca Knight for James Kobielus. We will have more from theCUBE's live coverage of DataWorks just after this.


So, I learned this trick from Guilherme Olivera and it works so well, I just had to share it with you guys here. So shoutouts to him, thank you so much for the info. In Blender, instead of creating a texture map, you can also just straight up vertex paint different areas of the model into different colors. And instead of exporting as an OBJ, export it as an FBX, then once you're in substance, import the file as usual, under texture settings, bake the maps as usual, set your output size, dilation width to zero, and under ID, set it to vertex color. And now, when you want to drag in a material, just hold CTRL and drag the material onto the vertex color you want it to be applied to. You're done. Hope that helps and as always, I'll give a fantastic day and I'll see you around.


This study examined the effects of burnishing on the surface layer of 317T steel valve stems. Burnishing improved the surface roughness, hardness, and residual stress, resulting in significantly longer durability of the graphite seals. Based on these findings, it is recommended that sliding diamond burnishing be used as a finishing treatment for valve stems. This article was authored by Michyslav Korzynskiy, Kazimira Dudek, and Katerzhena Korzynska.