Ladies and gentlemen, the President of the United States and Mrs. Reagan, anthems of the Republic of Singapore and the United States of America. The spirit of Singapore but also as a friend and as a senior world citizen, a statesman. The dazzling success of Singapore in these last two decades shines as a tribute to the hard work and ingenuity of its people and also as a monument to the wise leadership that you have provided your countrymen over your 26 years in office. Mr. Prime Minister, today it is common to hear of the vitality and prog-mplifies the spirit which is catapulting Pacific Rim nations into a new age. The people of the United States, Mr. Prime Minister, are committed to being part of this great experiment in enterprise and freedom. We are and will remain a Pacific Rim country. And with this, our two countries enjoy ever-broadening commercial ties. Two-way trade between us continues to grow rapidly. The United States is now the largest foreign investor in Singapore. Over 400 United States corporations have a presence there. Our people are joined together in a multitude of profit-making enterprises that benefit all concerned. As in many parts of the world, Singapore is struggling to overcome the effects of the international economic downturn. Yet your people are free with every reason to have faith in tomorrow. Freedom is the main spring of progress that has enriched the lives of our people. Comfort and policy objective of the United States is to protect and expand free trade by opening markets now closed or unfairly regulated. This will be a major goal at the next round of trade talks. When stride once unleashed, it will set in motion a cycle of reaction and paralysis, eventually destroying those it claims to protect. Mr. Prime Minister, I look forward to our discussion today. I'm confident that peace, as a country like the United States, composed of citizens with many philosophies and religions, your democratic institutions encourage social harmony by protecting the rights of the minority. You have demonstrated a sense of responsibility that few can match, playing a constructive role in the world, community of nations, and in the Asian Pacific region. Or at its colleagues in the Association of Southeast Asian Nations have taken against the Vietnam occupation of Cambodia and ASEAN's reasonable proposal for a political settlement returning self-determination to the Cambodian people. You and other ASEAN composed of people who are fiercely competitive, who strive for and expect perpetual progress. We're builders, entrepreneurs, people of wisdom. It's natural for us to be friends and to work together. And I'm grateful to have this opportunity to meet with you and discuss a broad range of issues and to renew our personal friendship. Mr. President, it is an honor to be received by you in facing the future with confidence. Since 1945, American leadership has been a constant factor in an ever-changing world. What the leader of the world's most powerful country and the world's largest economy does affects Singapore and the rest of East and Southeast Asia. Twenty years ago, there was no external power that could have challenged the preeminence of the United States and of cooperation between themselves. They grew closer together in political and economic cooperation as member states of the Association of Southeast Asian Nations. Mr. President, I look forward to my discussions with you and your colleagues. The ties between the United States and Singapore will strengthen. For it is an association that rests easily on both of us and our governments and bring mutual benefits. Thank you, Mr. President, for this warm welcome. Good. Let's conclude the ceremony.


So, I want to talk to you about designing for your users. I'm a developer and sometimes I forget that I'm not the person who's using the product that I'm making. I'm building a website for somebody or I'm building a plug-in and I'm not the person who's actually going to be using it. But spending so much time building it, of course, it's so obvious to me that this is how this thing should work, you know, right? Of course, you just go to this page and hit this setting and do this thing. We fall into this trap in WordPress too. There are a lot of things that we just kind of forget are hard. You know, we kind of forget that setting up a homepage for your site, you know, setting up a front page, we've all kind of gotten used to that, right? Like, it's, okay, well, we know we have to do this or I want to set up a menu, but first I have to make sure the page exists so I have to get out of the menu page and go to the page thing, add them, then go back to the menu page or the customizer or whatever. We've put up with these things. But we shouldn't do that when we're building things for our own users. Those can have disastrous consequences. So there are a few things that we need to focus on. First is you need to build things that are easy to understand as best you can. So for instance, I loved this thing here. This is a Vietnamese yamaha fiora.  There's a lot of hearts, so someone was very happy. In fact, it looks like it uses hearts as gasoline here. If that's what the icon says, I'm not sure. What I don't know is how can I tell if I'm empty or if it's even half full of gas? There's like two little extra diamonds there. Also, am I only supposed to be going either 40 or 100 kilometers an hour? There's a big gap there. Why does 20 have one star next to it? Zero has four stars. Or hearts, excuse me, is that happier? I don't really know what the design here was, but admittedly, it would be hard for me to look at this and kind of quickly figure out the things I need to know. How fast am I going and am I going to run out of gas? Now this is just a simple little, you know, whatever, I can work with this. But what happens when you get to a machine that is a little bit more complex? So this machine here is an airplane. Now there's a difference between the one on top and the one on bottom. Unfortunately, the little arrows might be a little hard to see, but the one on top used manual controls and also used manual gauges. So with the top aircraft, you can very quickly see what position all of those different gauges are at. I can't tell you what any of them actually do, but I can definitely tell that the ones on the left are all pointing really high and the ones on the right are all pointing really low. The one on the bottom was an updated one. This was in the mid-80s, this aircraft was introduced, that it used a new fly-by-wire system and it also used these new digital gauges. And you probably can't see from a distance where those gauges are pointing at the bottom. So let's say you're in a situation where the plane is shaking very violently, there are lights flashing, there are sounds, there's stuff going on, and you need to quickly tell something going on upon these gauges. This specifically, if anyone is familiar with the Kegworth air disaster, this specifically was named in the report as one of the causes for the airplane disaster, that the pilots were unable to easily read these gauges and determine that they were getting a little bit too close to the ground. In this one about a third of the passengers died, and I'm not trying to be super down here but I'm pointing out that it was specifically a design flaw in the official report, excuse me, a user interface design flaw, was found to be a reason that this disaster occurred in the first place. They were a bit too distracted to tell exactly what was going on. You also want to make sure that these interfaces that you're building are easy to use. You need to do a few things that can allow people to consistently utilize them. So first of all, I want to make sure that first time users can use the things that I'm building. I can't assume that everyone who's going to use my plug-in or start setting up my theme has already been using WordPress for a long time. I love playing the Wii. I love video games, tell them I'm a shirt, and I love the fact that so many people were touting it when it came out as this amazing device that was bridging generations together because people could just pick it up and just swing it along, and it's the same motion I make when I'm going bowling, so I was able to translate something that I already knew from the real world into a digital experience, and that makes grandma very happy. I also want to maintain some consistency when I'm building something. These are pictures from the same building. Maybe somebody put the handles on the door, and then they realize, oh, crud, whatever, I'll just slap the signs on, but there's no consistency here. So I'm betting that they fairly often have a lot of people walk up to that first set of doors and for a while try to figure out why they can't open it. You need to think, if I'm doing something one way, then can I continue that along through my experience? If somebody goes directly into the page to edit some content, then it's not their fault that they don't realize that this other bit of content is in a widget over on a completely different page, or that a menu on page A is set in an options panel, but in page B is set through the menu page. I remember that when you're building things, people are going to look for the path of least resistance. They're going to try to find patterns and try to figure out what the heck you were thinking when you made it. Make it easy for them to do that. I also wanted to point out, this is when I submit these slides, this is more of a problem. There is a new unified login coming to wordpress.org, which is enough reason for me to applaud, but the very first screen up top is me trying to log in to the wordpress support forms. You can see those little yellow boxes that have my username and password. When I'm on the get involved, the make page, it's not quite as simple to figure out where to log in. These are sites. These are on the same website. I want to point this inward at us to point out that we also have this problem sometimes. Can you figure out how to log in on the make page on the bottom there? I don't know if anyone, I mean, if you already know how to do it, then that doesn't count, but there is little text near the bottom under the hide threads and keyboard shortcuts that says log in to leave a comment. It's very light gray. It's tinier and it's hidden amongst other texts. It's not where I expect it to be. Again, I'm pointing out something that, yes, thankfully in the past few weeks has been, they're starting to remedy. But the fact that I'm looking at a site here and on two separate pages, I have two separate things to do. That doesn't bode well for an end user. You want to make sure that your designs are as error-free as possible. You're never going to get rid of every error that you have, but if you can start working on things in advance, then I can see this as a place that people might have problems. That's a good place to start from. So there's another fun disaster. I'm guessing a lot of you know what this wonderful place is. If anyone happens to be familiar with the story of Three Mile Island and the failure there, again, one of the things that led to it was a user interface problem. There was a specific shutoff valve that was not shut. And there was an indicator light that indicated that it was shut. Why was the light on when the valve wasn't shut? Because the light was tied to the press of a button. I pressed the button to shut the valve. The light turns on. I pressed the button to open the valve. The light turns off. The button was tied to a separate system that actually controlled opening and closing that valve. There were no sensors on the valve to determine is this valve open or closed. That light was tied to the button press itself. So the valve itself failed, but everyone thought it was fine. I'm not going to post any other pictures of this thing. Again, you cannot solve for every problem that your users might have. But one method that one company that a lot of us use has done is take the things that their users have made. For instance, retweets, hashtags, and doing at somebody. None of those were built into Twitter when it started out. Users are the ones that came up with these different features, and they eventually built these in. Finally, you need to make sure that your designs, your experiences are effective for your users. I'm sorry, I'm going a little faster. For instance, Evernote. This is both the web interface and the Mac interface for this app. It is something that I can navigate easily. It's something that I can tell what I'm doing, where I'm at, and they match one another. Mailchimp. When I'm utilizing Mailchimp and looking at reports here, at the end I'm hovering over a specific day. I can see the exact numbers that I want to look at very easily in one place. It's an effective design because with one glance, I can see what my campaigns have done. I can see how well they've worked or not worked. And that was, yeah, I'm sorry, out of time. Oh, that was actually my final point. Excuse me. You can very easily tell what they intended you to do. So again, you want to make sure that you will have easy to understand, easy to use, effective, and error-free design. Sorry, over time. Thank you. I'll be back in five minutes.


We have silver up 39 cents, $25.45 an ounce, copper, look at that baby, up $7.00, 7.5 cents, light sweet crude, flat, $80.96 a barrel, notes and bonds, a 10-year note, down 4 ticks, trading 110 or 2, the 30-year flat at 1823 in Kingdala, where are you, Kingdala, Kingdala's up 75 ticks, trading 103, 437, Euro 108, yen at 149, British pound, 127 to 1 US dollar. Triple witching coming up folks, here we go, let's take a look at this contract, this S&P contract, and figure out where we're going to go here. So we've been down as far as 40 handles, right now, you're down 33, excuse me, you're down 50 handles. Yeah, so let's see what we got here. So the lows have already got tested. Yeah, the lows got tested for sure. Now the question is, but there's no high volume highs out here either. So bottom line is that we'll see where this shakes out, that's the ying and the yang. Let's go into the NQs and see if the NQs are giving us anything. NQ, okay, so the lows tested. You know, when this happens, yeah, probably the counter trend bounced when we went earlier today, that's where we'll probably go, because the sellers stopped selling inside the NQ at the 18,103, and we're at 18,085 right now. So below that number, my point is, is that when you don't have any high volume spikes down, it's like you're going to go higher. So I suspect we're going to run into the 18,172 here. So that's up 100 from where we are. So let me go back over to these S&Ps for a second. We're going to see the same thing there. So, yeah. So that number there is 5201, and we're at 5186. Stay right there, folks, come right back.


Welcome to Attributes of a Class, Fields and Properties. In C-Sharp, attributes provide a way of associating data with an object and they take two forms, fields and properties. Fields store the data and properties allow access to the data. In this activity, we'll look at the differences between the two and how they should be used when creating code. An attribute describes an object. For example, a person's attributes include first name, last name, height, eye color, date of birth, and age. Each one of these attributes describes something specific about a person. Each instance of a class also has attributes. Let's look at a person class using some of the attributes we've listed. Public class person, private string first name, private string last name, private float height, which will represent height in inches, private string eye color, private date time, date of birth. As you can see, we've created private variables called fields for some of our attributes. By keeping these private, we've provided a bit of security for our objects and the only way to change or even get to the value of these variables is from within the person class. Now you might be asking, what's the use of having a class where none of the attributes are visible to the rest of the program? That's a good question. The answer is, typically it isn't very useful. So we need a way to access our fields. The way we do this in C sharp is by creating properties to access and set our variables. Using our previous example, let's create a property that allows us to get a person's name. The syntax is public string first name, get return name, set name equals value. More on that later. Let's break this down line by line. Even though the first line looks a lot like our name field, there are a few minor differences. First, we're using the public accessor instead of making it private. Next, notice we capitalize the word first name. We can't use a lowercase first name because that's already being used for the field. C sharp is a case sensitive language. So you'll often see field variables starting with a lowercase letter like name or with an underscore as an underscore name and their corresponding property starting with an uppercase letter. Finally, one more small difference is the addition of curly braces in place of semicolons. Inside the curly braces, we're required to add either a get statement, a set statement, or both statements. Let's look at the following code. Here we have a person class with some default values. Notice it has two properties, a first name property with only a get statement and a last name property with only a set statement. Public class person will initialize some of these fields to have default data. We'll set first name equal to Hussein. Last name equal to Ahmed. Height, 71. Eye color, brown. Date of birth, a new date time object, 1985, 130. We'll expose public properties, public string first name with a get statement, also known as a getter, returning first name, public string last name with a set statement, also known as a setter, last name equal to value. We'll talk about what value means shortly. In this next section, we'll create an instance of the person class. In this case, we're using a non-standard naming convention based on the Hungarian naming standard. We'll call our person Ohussein, where O represents object. While this is not a standard C-sharp naming convention, it's important to remember to use the naming convention provided by your instructor or where you were. Within our main method, we'll instantiate a new person object called Ohussein. Since the person class has a getter property for the first name, we can get the first name from Ohussein and store it in another variable. However, since there is no setter property, the next line generates an error when we try to assign a value to Ohussein dot first name. In contrast, since the person class doesn't have a getter property for the last name, an error is thrown when we try to assign Ohussein dot last name to a new variable. And unlike the first name, setting a new value to Ohussein dot last name won't generate an error because we've created a setter within the property. Because class fields are typically private, they're not accessible from code outside of the class. As we discovered earlier, access to those fields can be exposed and controlled via properties. In most cases, it makes sense to create get and set statements for your properties, such as public string last name get return last name, which returns the value stored in the last name field. Set last name equals value. Let's take a second look at the code inside of the get and set. Get is pretty straightforward. In this case, we're returning the value of the last name variable. However, set uses a keyword you may not have seen before. Value is a temporary variable used to pass in a value to the property. We actually used it in the previous example when we set Ohussein dot last name to equal Ahmed. So far, all of our examples have tied fields directly to properties, which often happens. Although properties can also be derived or computed from one or more fields. Let's look at two more examples demonstrating this. Public class person, we set the private variables to have some initial values. Let's take a look at our public properties. Public string full name get return first name plus space plus last name. Public int age get return date time dot now minus date of birth dot total days divided by 365 cast to int. Notice we have two properties, full name and age, and there are no fields called full name or age. In the case of the full name property, we're returning the first and last name fields concatenated with a space between them. Imagine for a second that we have fields storing first name, last name, and full name. Not only is this data redundant, but what happens when Ohussein changes his name? Now we have to change the data in multiple places. By creating a property for the full name, the redundant data is removed and the complexity of the code is reduced. The same is true for the age property. If we have someone's date of birth, we can calculate how old they are. To review, attributes of a class take two forms in C-sharp, fields and properties. Fields store the data and in most cases should be kept private. Private string first name. Properties on the other hand allow access to the data and are usually public. They also have a get statement, a set statement, or both. You have completed attributes of a class, fields and properties.


Low-carbon hydrogen could play an important role in achieving a net zero-carbon economy, as it can help reduce emissions in hard-to-abate sectors such as transportation and industry. In order to ensure that low-carbon hydrogen production does not lead to increased emissions, the US government recently introduced an escalating production tax credit, PTC. This tax credit provides financial incentives for producers of hydrogen that meets increasingly stringent embodied emissions thresholds. However, the PTC could be improved by requiring producers to source all of their electricity from renewable sources, or by imposing additional clean energy procurement requirements. If these requirements are met, then the PTC can effectively reduce emissions associated with hydrogen production. Otherwise, emissions will remain higher than those of conventional, fossil-based hydrogen production pathways. This article was authored by Wilson Ricks, Chinyushu, and Jesse D. Jenkins.


Hi, my name is John Kevom and I want to show you how to build a touchless soda machine. I have a couple of sensors here and I'll show you how they work, but it starts. Take your ST branded cup and put it in the cup place. The sensor right here notices that there's a cup there and says, I'm ready to pour. It activates the little guy and if you look at this green dot right there, that's where my hand is relative to the sensor right there. Let's choose apple juice. Leave it there and it says fine and I push to pour. Now if I take my hand away, it stops. If I bring my hand back, it continues and we're going to leave it here until the sensor gets full. There is another, the same sensor that detects the cup is detecting its fullness level and when it decides it's full, the soda will stop, see? Now if I insert another cup, it'll notice that the cup is upside down right there. Turn it over and it'll activate. Once again, I can pour some Chew's of Soda. Let's pick ginger ale's fine and push to pour. Just like always, pick it away, take the drink and you should be happy. For information, come to ST.com, like always.