Before we jump into numerical methods in heat transfer, what I want to do is answer a couple of questions and these are sometimes questions that help students understand a little bit better what numerical methods actually are. So the first question is what are numerical methods? I took a course in numerical methods when I was an undergrad and I'll be honest I went through the entire course and didn't really know what was going on. It was able to get a very good grade, do the programs, write programs, but it was a little bit on the confusing and abstract side mainly because there weren't really any tangible applications that could provide an understanding of how you would apply numerical methods. So I think it can be beneficial for students to answer these questions before we jump in. So to begin with what are numerical methods? So from the perspective of engineering, engineering education, engineering programs, we can say numerical methods are the solution to mathematical physics problems and so we create mathematical physics problems in almost every engineering course. Numerical methods provide a method by which we can solve for certain aspects of these problems. Another thing that we can say about numerical methods, numerical methods provide us with approximate solutions to these mathematical physics problems. So that's another point that is important to realize and this is opposed or different than if you are able to come up with an exact analytic solution. So that might be something like f of x is equal to x squared plus 2y. With an analytic solution you come up with, actually that should have been f of x y because we have the two variables there, but you'll come up with an exact analytic relationship with a numerical method. You have things on a grid at discrete points and so you're just coming up with a solution at those discrete points and that's where you know your answer and what goes on between those points you don't really know. You could guess in order to obtain that you would have to have a finer resolution grid and then you would be able to figure out what is going on in the intermediate points. So that is another thing that is unique about numerical methods. They are approximate solutions to the problems that we're solving and so the next question is what types of problems can we solve with numerical methods? So let's take a look at that and I'll also talk about what types of methods we might use. So if you take a course in numerical methods quite often it will begin with very simple types of problems and usually it'll begin with interpolation of a function. And so if you're doing interpolation of a function the simplest is linear interpolation. So you know two data points and you're trying to find out some value in the middle you draw a linear line between the two and that enables you to get the midpoint. So that's linear interpolation and then as we get more complex you can have cubic spline interpolation and that involves matching conditions that go higher than just the slope. It might be second-order derivatives at the boundary points when we're doing our interpolation. So that's one type of problem that you can solve with numerical methods. Another one is linear algebra, a system of equations. And with a system of equations quite often what we end up doing is inverting a matrix. And so in numerical methods there are ways that you can do matrix inversion. Now I realize that we today have very modern tools such as Matlab and Mathematica, things like that that enable us to do this quite quickly. But with numerical methods you can get programs that you can develop methods of inverting a matrix using these programs. Other things you might be doing in a course in numerical methods and another topic is integration of a function. And example applications might be something like area under a curve or volume of a shape. And when you're doing these you might use techniques like the trapezoid method or simpsons method. So if you've taken a course in numerical methods you'll recognize a lot of these. Another very common application in engineering is integration of ordinary differential equations. And there are different techniques that we can use but a very common one used in engineering is the I'll probably say it incorrectly. I've heard Rungikata and Rungikata. I'm not sure how to actually pronounce the first name there so I apologize if I am saying it incorrectly. So that's a common technique. And then the next in this escalating scale of complexity of numerical methods applications we get to what we're going to be looking at in this course and that is solutions of partial differential equations which we know the heat diffusion equation is a partial differential equation. And so we can look at heat conduction as we're going to in this course. You can look at fluid flow external aerodynamics so the flow overbodies. And these latter two here are quite often referred to as being CFD or computational fluid dynamics. And in solving PDEs or partial differential equations we have a couple of techniques. The one that we're going to look at is the finite difference technique. And the other one that I mentioned is the finite element method. So now this is not exclusive but quite often finite difference is used for heat or for CFD fluid flow problems. And finite element quite often is used in structural analysis or in solid mechanics. But what we're going to be covering in this course we're going to be looking at the finite difference method. And we will in the next segment go through the different steps of applying the finite difference method which is a common technique within numerical methods to the heat diffusion equation. And so we'll be going through all the steps that you go through in applying numerical methods to solve heat transfer problems. So I just wanted to give you that segment to kind of go through what numerical methods are and what types of problems you can solve with numerical methods. So from here on we're going to dive in and start applying this to heat transfer.


Okay, very good morning. Hope you are doing well. It's Wednesday the 13th of October and I'm gonna talk if you a few different things We're looking at Apple's aftermarket Decline in share price that we saw last night and I'll explain why that's happened as it's reported the company might well Slash its iPhone 13 production and targets. We're also gonna talk about Chinese trade data a couple of Fed Comments as well to be aware of one of which Bostick said that transitory is a dirty word and in fact when he was giving his speech last night He was dropping dollar bill every time into a naughty jar. He said the word transitory And we also talk about the formalities around the US debt ceiling and then of course the day ahead and actually just before I get stuck into Apple looking at the general Set up of the charts at the moment this morning. So just to remind anyone who's who's new to joining us I've got euro dollar top left cable top center gold futures top right and I've got this center left to right DAX future now that's that 100 s&p futures and I've got WTI crude down here on the bottom with bottom right the US Ten year and so overall pretty flat this morning in fact There's not too much movement scene their dollar index is is pretty much unchanged and therefore just marginal gains seen in The major pairs to get the European session underway As far as the equity markets are concerned pretty similar set up for the nasdaq as it is in the s&p where Yesterday's lower bound levels that were seen around this time On Tuesday morning session are still holding for the time being so certainly key areas to watch as support Now really on three more meaningful tests that we've had in the last 24 hours around 43 21 and a half in the s&p and as I said the nasdaq is is pretty similar here In its formation for the time being on a daily chart On the downside, we're still a little bit away from what would be seen as more longer term crucial levels of support With generally that rising Channel that we have with the horizontal area of support coming in around 14 471 As you can see here, we're trading well above that at the moment by around 200 points or so Markets at the moment as you can see here Just moving up the nasdaq future to its pivot level under no real new fresh catalyst this morning But perhaps people just looking to just enter again Lower down on those technical areas of support. Otherwise gold not too interesting right now But positive around five bucks Oils pretty much just locked in a bit of a sideways Period of consolidation for the time being after some of the recent surgeon price that we've had so it's pretty flat overall But holding an $80 handle and t-notes just tracking sideways for the moment basically training unchanged So let's jump straight into it and talk about Apple first and why Did their share price decline around 1.3% aftermarket while the headline is here The company is likely to slash its projected iPhone 13 production targets for this year by as many as 10 million Units and the rationale behind this is because of a prolonged chip shortage Hitting then its flagship product again. I'm a stress This is according to people familiar and have knowledge of the matter rather than an explicit comment from the company itself, but You can pretty much take it that it is the way that these new cycles tend to work And so Apple shares. Yeah, they did fall aftermarket and certainly something will be keeping an eye on I guess for a bit of context Here's a look at you know, given the impact that these global Chip chip supply shortages having on a number of manufacturing processes that this is looking at the gap between Ordering a chip and a delivery of it hitting Are now a record of 21.7 weeks as you can see here in pre pandemic times The average kind of time from order to delivery would have been in terms of weeks Roughly about half of what it is at the moment currently So definitely puts that into a bit of perspective But in this article it was on Bloomberg if you want to have a more of a read I did retweet it from the amplify me Twitter account It does go on to talk about the fact that it's still likely that Apple's gonna have an absolutely Phenomenal quarter going into that Christmas season when we get to Q4 Given the fact that the refresh rate for the iPhone 13 is like to be quite strong And I think we're looking at Predictive revenues for that quarter alone when that time comes around 120 billion in a quarter, which is just phenomenal In that respect. So some snags now I don't think ultimately this is a real deal breaker And some people talking about look at weight in the nasdaq future overnight But can't really say I see it that evident on my charts to be to be quite honest and the market at the moment It's moving higher for the time being otherwise the other thing from overnight in the Asia pack session is Evergrande assigned they're still generating a few headlines But I think important is that yes, they are missing some of these bond payments still And it is still a bit up in the air about what is the next step for them as a company But I would say overall broader markets in the assets that I've just shown you on my charts I think generally have just kind of accepted the reality of whatever grand is at the moment And I think that that kind of period of heightened sensitivity to that whole contagion effect has Definitely diminished a great deal And so as much as their headlines and I continue to monitor them remain vigilant They don't really see that really shaping much of the intraday short-term sentiment or strategy for the time being On the flip side though from an economic point of view. We did have overnight China's export growth accelerated in September and it has defied quite a lot of expectations of a slowdown Amid a nationwide power crunch that has forced factories to cut Productions so by numbers the Chinese trade balance came in at sixty six point seven six billion This would be US dollars in September That was above the expected forty six point eight billion their export number year-on-year for September was at twenty eight point one percent above the expected twenty one percent and up on the previous twenty five point six couple of things though and This was a comment from spokesman of the customs department in China Who said that fourth quarter trade growth may slow because of higher base of comparison from a year ago plus logistical problems In addition global appetite for Chinese goods and let's say could also start to kind of wane After buyers front-loaded their Christmas orders because everyone's kind of the chicken or the egg at the moment people are aware that there's going to be Production distribution issues most likely going into the Christmas period Given the kind of bottlenecks that we've been experiencing and that is that going to change consumer behavior and therefore Companies forward Front-loading very early their Christmas orders, which means then we get quite a dramatic drop-off as we go into the latter part of this year Perhaps so yeah, I mean how important is this Chinese data? I mean It's interesting, but if it is good, I don't think it's necessarily a positive trigger to initiate any type of long-lasting sentiment I think it is what it is on the surface level But as I said it's probably unlikely to remain at such Good pace as what we've seen with the last two trade data numbers coming out of China Which have actually exceeded expectations. I probably don't see that lasting for too long And I think the markets are aware of that for the factors. I've just mentioned the other thing then is yeah transitory It's a dirty dirty word. I can honestly say I can think of worse dirty words, but Yeah, the three speakers that we've had Bostick who is a voting member of the Atlanta Fed Voting member in the FOMC said inflation surge is lasting longer than expected So it is not appropriate to refer to such a rise as transitory. I don't think that's surprising I think that's just generally how the markets Become to view that situation and hence the reason why yields have seen some of the biggest moves in recent recent months In the last couple of weeks Bostick favoring tapering bonds sees lift off in more than a year So very explicit again to kind of define the timelines that tapering is not rate hikes the two are kind of two different processes The other speakers that we have had Is well, here's a look at the not so transitory inflation figures and certainly obviously we're looking at this today Because we get US CPI which I'll touch upon in a moment coming out this afternoon Which is obviously a critical component for for how sticky or not this inflationary pressure is at the moment The other speakers that we've had was the vice chair Richard Carida who noted that conditions required to begin tapering the Fed's Bomb buying program have all But been met and so again given the green light as markets are very much expecting for that November announcement of tapering and then the last one is bully bullard Who sits right at the most? Kind of hawkish end of the spectrum said in here bomb purchases should be tapered quickly In case rate hikes are needed Started talking about Advocating trying to get finished with tapering processed by the end of the first quarter of next year and to give that context as What will be heard at the previous FMC meeting they were talking more around the summer of next year So hence the reason why he sits much more on that aggressive hawkish end of the spectrum Not unusual to hear that comment from bullard So again of the three nothing really there too shocking I would say and hence the reason why there's been no reaction Despite the kind of hawkish sound and comments in the US dollar, which if anything is retesting actually as they speak Some of the recent lows that the Dixie has been trading So actually keeping an eye on the Dixie as I'm speaking now. It's just retesting the APAC low At the moment down about two tenths of one percent this morning in the Dixie And then a few other things to be aware of today, you've got corporate earnings We kick off the big banks today JP Morgan's coming out just ahead of 12 o'clock London time You've got the likes of black rock as well pre-market and then that kicks us off with then Wells Fargo City MS on Thursday and Goldman's coming out on Friday quick look at JP. What can we expect? so Focus on JP M's net interest margin so key metric of course for the banking Industry reflecting the difference between the interest banks earn on their assets and the interest they pay out to depositors and other creditors quick refresh though in Q2 of 2021 results that that came out in mid-July for for JP Morgan their bank bolstered their profits by freeing up another 3 billion in pandemic loan loss reserves that it originally set aside for pandemic related defaults So again, it's kind of how do you kind of pump the numbers and make them look fantastic? Well, yeah, if you're freeing up reserves to the tune of 3 billion that certainly helps and so that will start to obviously fade as those Loan loss reserves have already been kind of shifted in that sense In recent months, JP Morgan's rebound has faced a couple of challenges And I guess some of these are quite true of other bank stocks as well That we'll be looking out for later in this week that the Delta variant of COVID-19 Particularly over the summer has slowed the rebound somewhat of the economy JP Morgan's costs have also risen Boosted by pay to attract junior employees. You remember course there was that kind of infamous Goldman report that came out and Yeah, rather than seeing any structural change in the hours that they work a hundred hours, which of course is pretty insane Just throw some more money at these kids and and hopefully the problem goes away And so obviously your cost base going up in that respect as well Analysts expect tepid year-over-year growth for earnings per share to the EPS and revenue for the quarter And this would mark a significant slowdown in earnings growth compared to the previous three quarters So again, there's probably a reoccurring theme that we'll see through this earnings period Is that there's a bit of a realization about what the future now is going to look like and so a bit of a deceleration for some of the astronomical growth that we were seeing going through this Really strong Equity run that we've had through the post pandemic initial period now We're kind of to see the the top and slight fatigue of that And so a bit of a recalibration back to a degree a sense of normality From those much more bullish outlooks that we're seeing before is probably going to be the order of the day to some degree Final point from a student perspective because I know there's a number of students I've been talking to that are interviewing the likes of JP and and other us banks one thing I would say is that you know jump on the earnings The investor relation pages of these these banks after they come out and do take a look at those top level sheets to get a real Just glossary of like what the major divisions how they're performing. They're the different drivers of different divisions Just just generally get a flavor of how beyond just then the surface level that bank is performing So when you go into these interview situations, you're just that better equipped about knowing your target institution Anyone who needs help with that. Just drop me a comment. I can shoot you the The full actual press releases that come out not problem at all Otherwise just jumping to what's happening today We've already had some UK data to be quite honest pretty disinterested in that I mean GDP estimate for August month to month was point four against point five The three months on three months figure two point ninety is three percent In terms of sterling reactions not really so much sterling reaction, but I'd say dollar a little bit softer this morning Eur a dollar cable Kind of following a uniform approach cable just accentuating that move a little bit on the short term technical breach of the late APAC high That we've seen so just a short run up here towards its R1 up about 30 pips this morning But equally so you're a dollars up about 21 albeit that's being held for the time being by the APAC high So yeah, I'd say the UK data really not a big deal As far as really shaping any new thoughts about the UK economic recovery at this point Otherwise jumping further forward. You've got your as an industrial production at 10, but the real More interesting events are really happening this afternoon. You've got US CPI of course happening at 130 That's probably going to generate the most interests probably one of the main highlights of the week and certainly I think much more interesting perhaps than what we'll get out of the FMC minutes Which are coming out at 7 p.m. Later on this evening that it's going to be scanned for clues, of course any hints Towards the formalization of the announcement of tapering in November meeting But I think that's no surprise if that is the case So I don't think we're going to get too much more out of those minutes. So for CPI Analysts at the Dutch Bank IG write that the reopening spiking key areas that we've Seen the rate of price increases moderate But it's still faster than what we saw pre-pandemic with higher food housing costs particularly evident They suggest then that this will keep the year-on-year inflation rates elevated with the risk being that they Rise further in coming months given supply chain issues and infantry Shortages as we go into the key holiday season Hence the reason why as well you're getting the central bankers talking about well look We shouldn't really be using this word transitory so so clearly at the moment because perhaps that's not quite the case I guess more importantly, how's the market going to take that figure and react? Well, I don't think whether it's a little bit stronger a little bit weaker That's really going to change the game for the Fed in November. So any type of price volatility We see intraday is probably going to be relatively short-lived. I'd say in that respect Could it move I mean certainly sure I mean if we get a forecast beating number the headlines expected at five point three if it goes up to five point five and Let's say the core reading as well comes in at the top of the range four point three percent Yeah You probably expect the immediate reaction to be dollar yield strength gold under some pressure perhaps equities have little Bump on the downside and if we break that technical errors of support that we were looking at in the likes of the Nasdaq and the S&P you might get a little extended run on the downside. I don't think it would be dramatic though even under that scenario Because I think at this point it doesn't really change the bigger picture I think people are of that view that inflation is gonna hang about a little longer if it comes out a little higher on This side again with always with the CPI report in the US just having a look through the breakdown of the report What is causing these price pressures to determine or not whether how transitory they are? And so, yeah, I'll tweet that table and identify for you any of those things that stick out later on this afternoon And Yeah, that's pretty much it. So otherwise speakers. You've got ECB to cost speaking at 11 30 bank of England cunliffe Feds George this afternoon 230 and then the evening George at 9 30 Speaking alongside Brainard as well and then fixed income supply Italy Germany and then 24 billion dollars in the 30 and no auction as well coming out 6 p.m. From the US. So that is it gonna leave it there I hope that was useful any comments or questions at all. Feel free to just just drop those below Otherwise, I will see you guys tomorrow. Thanks very much


Hello everyone, over there in Singapore for FOSS Asia. I'm so sad that I can't be there in person. I was really looking forward to my first FOSS Asia event and to talk about the projects that I've been working on around open design and open source design. But instead of me being there in person because of these unsure times, I'm here recording what I would be talking to everyone about for you to watch afterwards. So let's get on with the design contributions to open source, the learnings from the open design project. OK, so a little bit about me. My name is Errol. My pronouns are they, them, theirs. If you want to tag me in any tweets or any content, please use my pronouns that are the ones that I use, they, them. I am a humanitarian designer, so I primarily do work in the design field around humanitarian and human rights cases. So for things like election monitoring, things to do with crisis response and things to do with street harassment. And these are all tech responses to these kinds of humanitarian challenges. I've been in the product and digital and web space for about 10 years now, working in design and UX across lots of different titles. And I've been working in humanitarian and non-profit sector for around seven years, both voluntarily and professionally, so both paid and unpaid work. And I'm fairly new to open source. I'm fairly new to the world of openness and open source. About two years was when I had my first role in an open source technology non-profit doing design work for their tools. And when I was working in this open source organization, this non-profit, one of the things that me and my colleague, my other design colleague used to talk about a lot was why there aren't many design related contributions to open source. So we were there working within the open source day-to-day and we were seeing developers and people that could code and people that could write documentation. Anybody really that was from a sort of technical background or perhaps like a part of the coding community or that kind of techie community, they were ready and able to be contributing anything that they could to the repo when they had the time. And us as designers we were really curious as to why there weren't design related contributions as well because we were working openly in issues in those open repos as well, publishing our design work as openly as possible as we could while still using proprietary tools at the time because we weren't really sure about what options there were for design open source design tooling. So yeah, we were curious why aren't there more design contributions. We did a couple of different projects around this. We did one within the open leaders and Mozilla open leaders program to try and break down some of the barriers to design contributions or at least investigate it like very early on. We also did that for product management and a few of the other kind of functions that you find around design and tech products in general. We were basically just really confused as to why people that aren't coders don't get more involved in open source as well. One of the partnerships that we had really early on was with an organization called designer.  So free work for a non profit and they were really interested in us at the time. The open source organization that I worked for was called Ushahidi and they made tech products for lots of different cases like I said humanitarian cases but predominantly the tool that they were doing some pro bono work on was a tool called 10 for which was looking at how to solve the communications problems in crises. So when you try and get in contact with multiple people through multiple different methods all at once to try and find out whether they're safe. And this was a real use case for the tool when we first created 10 for within the Ushahidi open source nonprofit. It was off the back of a terrorist attack that happened in a mall in Nairobi where some of our staff were present in the mall as the attack was happening and we couldn't get in contact with them. So we went through this frantic process of trying to get in contact with them trying to get in contact with their families through just, you know, the regular ways you get you communicate in a crisis, you know, texts, calling, WhatsApp, all the different kind of methods to try and find out whether they're okay. And we didn't find out if they were okay for many, many hours and it was very frantic and very upsetting at the time for the team that was working at the time. And on the Monday, they decided that, well, we create open source tools. So let's try and find a way to create a tool that helps this process. And that was the tool called 10 for. And the organization, the agency designer were doing some work on this tool. They did, they did some work in just in isolation as they do as an agency. But then one of the things that they suggested that we do was a kind of a hackathon, but for designers, they called it a design jam. And this was our first event that would later become some of the format for open design and the open design work that we did within Ushahidi on the tool 10 for in communities really around the world. So we did that first event in Berlin in 2018. It was a really interesting event. We learned a lot about how to do the next one, which was in Seattle in 2019. And the main thing that we learned about designers engaging with open source tools and contributing to open source tools and specifically open source tools that aim to do some kind of very obvious good in the world. So very obvious nonprofit or humanitarian use case is that really designers want to work on projects for good. It's a real fundamental part of the design designer brain that we want to solve problems. We want to solve problems using our skills, which are design skills. And one of the things that we don't get to do as often within commercial corporate roles is work on projects that very clearly are for the common good of humanity or the earth or for any kind of for good process. And it was really a simple learning that we discovered at first this designers wanting to work on projects for good. And after those first two events we were having conversations with Adobe at the time. So Adobe, if you're probably aware of what they create, they create proprietary or commercial tools for designers. And really there are lots of other design tools that you can use nowadays both open source and still proprietary or commercial tools. But Adobe is one of the most popular ones. It's one of the ones that we typically first learn to use as designers. So it's really important that Adobe came on board with the with the idea of this project really early on. And they were present at the Berlin event and at the Seattle event. And they were curious how they could progress this work, you know, how they could support designers working on projects for good with the added benefit of learning better, how designers want to contribute and collaborate in an open source kind of way. There was some, you know, things that Adobe were going to get out of that kind of engagement. They were going to learn better how designers collaborate across different time zones and different kind of complications and maybe not as part of a employed team. So they really wanted to find out how they could make things better and genuinely how that they could surface open source projects that need design help a lot better within their tooling. So together, the three of us, that's Adobe, Oshihidi and designer created the project called Open Design. And we were trying at first to investigate and solve questions around the why aren't there more designers in open source. And what we what we really wanted to do at first was a lot of in depth research. So we spent a number of months researching how to go forward with the with the project and how to how to build on the success or the learnings of the first two events. So we came up with the with the statement that we kind of wanted to wanted to go with which is designers still collaborating and contributing to specifically at the moment humanitarian open source software and tech for good at challenge gatherings. And these this was the primary focus initially of open design to learn and to carry on the format and carry on learning from the format again in an open way. But there are lots of challenges. There are too many challenges actually that we really learned within the process of both our research and doing the challenge events to really go into any depth within within a short talk time. But I'm going to cover some of the challenges that we discovered some of the most important ones I think. But if you are curious as to know what all the other challenges were, then they're all available on our open repo which has a link at the end of the talk. So lots of different challenges. One of the first challenges is really that most designers don't have a clue what OSS can be or is. So when you speak to designers and other kinds of roles that aren't necessarily coding or development roles, they can really be perplexed or surprised or just largely unaware of what open source software is. Maybe they've heard of the term. Maybe they've talked to coders or developers before and they've heard of it. But if they have then often their response are, you know, unencouraging suggestions that open source is really limited to terminal based tools or very developer heavy tools or things that are very complex and code related. And they actually really get very surprised that there are open source tools which are much more, you know, accessible to a designer, both for use from designers, but also to be involved in how those develop. So that it's not just about trying to understand the terminal or very, very code heavy things in depth, but there is a whole world of open source to discover that is very much on the kind of for good or humanitarian side of things. And often what happens when you talk about the kinds of open source software that is out there to two designers, like try and break their misconceptions of what open source is, they then are able to better understand why the developer tools for open source exist. And they then are able to start understanding that a lot of these open source developer tools and things that are created and used predominantly by developers are the foundations of the open web and how they also use the open web. And then they can better start to understand and engage with open source software as a larger concept. The second challenge really is a pretty huge one to be honest. It's the open source software isn't really part of design education or at least not explicitly so. So when you are in formal or informal education as a designer, a lot of what gets covered is not at all really code related or open source related. There even might be certain modules within your design education, again, formal or informal that actually use open open source tools or that have some kind of open source tooling within it. But the designers really don't get kind of educated or told about open source as either a set of principles as a movement as a history or as a practical kind of application that they are likely to be using. So it's absent from my education largely and it's coming more into educational practices now. So I know that I've worked with a university in West Germany in Darmstadt that do modules on open source software and building on open source software and teaching the principles of kind of open source software in us like the ethos of how you work openly. And really that's like one of the first times that I've heard an educational institution of any kind really talking about open source or openness. And connected to this issue around education is another issue, which I won't go into too much depth about, but it really is then connected to how designers go into employment. So if we're not teaching open source and contribution to open source within our educational institutions, and we're also not educating our hiring companies, our companies that are looking for designers, then even if we did teach open source within design education, when they go along to the interviews for these companies or these organizations, then the people hiring them are not going to be knowledgeable about open source either. So when they have these designers come to them with these portfolios full of maybe lots of great design contributions to open source, they're not really going to know how to digest that information and regard it as highly as it possibly should be. So what we'd love to be looking at and doing is like this synchronized effort for education within the industry and within the community as a whole. So not just within design education institutes, but within our workplaces and within our community as well, because that's how the practices and the ethos scatter throughout the whole of the design community, and how it becomes part of how we operate in general and how we engage with each other and with a better understanding. So hand in hand with education needs to come our workplaces as well. So another problem that we have is even if the designers know about open source, so maybe they really have an in depth understanding of open source or maybe they have worked on open source tools like myself, or are really really interested in the process of open source and they don't need convincing, then the fact that a lot of open source exists within GitHub or GitLab or places where repositories and projects are stored is a really huge barrier for a lot of designers and basically people that don't consider themselves technical, which is really, really toxic kind of view of things. It's one of our big problems within the tech industry in general. But basically whenever you talk about open source and GitHub with a designer, if they're not comfortable with a certain what they consider a certain level of code competency, they think that it's not for them. So that's just a place, a sector of the internet that they just don't feel included and they just don't feel like they have access to that. And often this is because a lot of the open source software projects really do require you to have a very basic level of knowledge of like how to even navigate the interface on GitHub, how do I even find where issues are if I've never been shown before, let alone try and clone a repo and then create a local instance of open source software to contribute to maybe a UI improvement or some kind of UX improvement. That's not even going anywhere near actually cloning and creating like an instance of the open source tool. And yeah, so GitHub is just really, really tricky space because it's where a lot of things happen. It's a great place and it works really, really well for some of these existing functions. But for designers, it's really, really a barrier. It's really, really tricky and really can often only be successful if you have somebody that knows the open source repo really, really well working alongside you to help you set up an instance. Okay, so another another problem for designers within open source is on the other side of things. So from the open source software side of things and when you talk to them about design. And often when you say the word design to them, they often immediately think of logos and graphics or basically user interface or visuals. So anything that you can see essentially. And this really, you know, removes a whole huge section of really valuable design practice like user experience and usability and interaction design and research led design and design thinking and discovery pieces. And all the all the stuff that is less about the visuals and less about the implementation of those actual sort of interfaces or products and actually really about how you design an experience that's right for the people that are using them. And this is actually a kind of really tricky problem because a lot of this can be attributed to a problem around, say jargon or really specific functional language. So even when I was describing some of the design functions, then some of those you might have been familiar with others you might not have been familiar with in that process of when we hear technical jargon for a function or a job that isn't our own, we can get quite, you know, closed off and scared when somebody starts, you know, really sort of talking about their jargon language. And so what we really need to do as designers and as open source projects within this problem is start having bigger and better and more inclusive conversations about what design can offer an open source project beyond like logos and graphics, and be really sympathetic and inclusive when people within open source projects do understand design as logos and graphics and really help them along with with how much more design can can offer open source projects beyond beyond those those things. But also those are also important things that are great contributions as well logos and graphics are very important too. So open source issues within a typical repo can also be a problem they can be really restrictive. So I think most of the audience at FOSS Asia will be familiar with issues or tickets or how we describe pieces of works pieces of work within repositories on our on our open source software. But they are often really solutions focused technically wise. They use again, like I was saying about design jargon, they use a lot of technical jargon or code jargon and a lot of these issues are really just not accessible to designers. So even if they might want to help on a specific part of the open source software, they might really even not know how to read some of the issues that actually are part of, you know, that section that they want to work on. And what we can do for this is make our issues a lot more friendly, a lot more informational and a lot more open to other kinds of ways of explaining what is needed in that issue. So that if it's a technical issue, it's solving a technical problem, then you can explain it in less technical terms, maybe, or in a really simple terms. And if somebody that isn't a coder stumbles across that issue, or if you think design might be able to actually help that issue and you tag it as a label, then with a design label, then a designer could come along and read that issue and say, hey, I think that there's a way that we can improve that from a different perspective. And that way you can actually grow your open source project in new and kind of unknown ways by being much more inclusive in how you write your issues. But alongside restrictive issue descriptions that are typically found within most open source issues within the repositories, when you take these issues to, or when you take generalized problems around a piece of software to design workshops and you say, hey, we want to improve this part of this product, this feature, they then become unfocused and the design responses to those problems lack relevancy. So what will be created there by the designers, and this is what we experienced in the first two design events that we had, was designers came up with these great sort of responses to solve those problems, but none of them were anywhere near implementable by the even a full time like huge tech team, let alone an open source contributions tech team. So what you really need to do with issues that you or features that you want to take to a design community or to designers for open source design contributions, is find that middle ground between a restrictive technical sounding issue and an open explorative design issue that still has the relevancy to that implementation. So you have to find a really good middle ground between these two places. A huge problem that designers have is lack of version control in both our software that we use proprietary or a lot of open source tools don't have this just yet. There are some things that are happening, which is really exciting, but our software and our processes are very removed from the idea of version control. So within coding there is this whole way of branching code and conflicts when you try and merge and there's this process of communication that is really reasonably well established within the code community. But within the design community we don't really have the technical ways of doing these things and a lot of it has to happen through communication and through almost our way of pair designing. So that we're not basically two designers working on a same issue and in conflict or that we're also sharing our resources really, really openly and collaboratively as well. So we have a huge problem around version control conflict and processes for designers to participate in open source. And one of the best things that could happen is in the future is seeing this not only within the tools that we use as designers, both proprietary and open source, but within the systems where open source software is housed. So the GitHub and the Git Labs and the places where the projects exist as well. So to move on from the many, many challenges that we tried to solve, at least in some way with our next few events that we did for the open design project, we're going to go on to what we did for the open design events. So we did a lot of research, we did a lot of investigation and we created a comprehensive set of tools and methodology and framework and approaches that were based on really robust research with people that have done similar things before. So we partnered really, really closely with a lot of organizations that have looked at things like this before or done similar activities to this before. So you're talking about your open IDOs, you're talking about your global virtual design sprints, you're talking your open source design community and things like the Hague Hacks, which is again another design event that's focused around humanitarian cases. So we worked really closely with these people that have done some of these things before to say, hey, how can we make some progress within this on our events?  We did one in Bangalore in India for the Design Up Festival, the Design Up Conference there. And we did one in Taipei in Taiwan for the Open Up Global Summit there. And we focused on the tool within Ishihidee's open source tool base, which was 10-4, the one that I mentioned earlier on, which was crisis communication. And we focused on very local events that had happened in those countries that were very relevant to the people that were coming to these events. So in Bangalore, we focused on the floods that had happened in the southwest of the country in the Kerala region. And in Taipei in Taiwan, we focused on the effects of typhoons and hurricanes around rural farming communities and the loss of livelihood there. So we wanted to make them really specific and really relevant to the locations as well as bringing the processes that we'd created as well. So what we did at these events is we did a series of different design activities. So these are what we chose as initial activities to do over a full day workshop. And they are empathy mapping within our user base for our tool 10-4 and for our use cases of floods and typhoons. We did a exercise which was called define the problems, which helps you really identify the problems that are part of the issues that you're trying to solve in the open source way. We did ideation around the defined problems that came from that activity. There was a storyboarding exercise to try and fill in any gaps and see if there were any things that we'd missed when we were thinking about our solutions. And then we looked at sketching and prototyping within the workshops as well as our final contribution to the open source. And I think one of the main things to talk about here is the pre-work that went into these workshops. So when we were constructing these workshops, there were a series of different things that we created as a team, as the open design team, in order to make these workshops go a lot smoother. And one of them was the process of taking a restrictive issue and an open design challenge and finding that middle ground. And we tried two different approaches. We tried a more restrictive, less open approach in Bangalore. And in Taipei, we tried a much more open approach but still some restrictions. And we think that we found pretty much the middle ground between testing those two different extremes. We've now found after these two events the kind of the sweet area for where you would like describe a challenge for a set of designers that would still be able to be implemented by a technical team in an open source repo. And one of the great things about the events that we held is that they were for designers largely, but they weren't isolated just to designers. So within Bangalore, we had developers, we had product managers, we had different kinds of designers of all types, all different kinds of functions, all different kinds of backgrounds participating. And in Taipei and Taiwan, we also had people that were from every section of the design community. So people that were still studying and people that had been part of the design industry for a number of years and worked on different kinds of tools and different kinds of cases as well. And one of the really big learnings from the events that we did and the way that we'd be taking the open design project further is the first one is around the locations specificness and how it builds community. So because design in open source, it's relatively new and our processes and communities, they're not structured or socialized in the same way as developer communities. We really need the design workshops for open source to be really location specific in the beginning. So this might not be the case much further in the future and we might be able to do much more like remote less location specific things in the future. But right now, as this initiative and as designers in an open source is growing, we really do need it to be location specific for the people that are new to open source. The designers that are new to open source, it really needs to make sense to them and there really needs to be that community building alongside the practical elements of contributing. So this means that the that the location should ideally be somewhere where the open source is used. So when we were choosing where to go with the open source open design workshops, we were choosing places like Bangalore and Taipei where there was a real use case for 10 for the open source tool that we were contributing design tool to. And we were lucky that 10 for in a sense is very global has a very global use and crises are kind of, you know, universal everywhere, especially at the moment we've got a global crisis happening at the moment. So a lot of we were a lot of benefit was from a tool that was very global in nature. But if you have a tool and open source tool that is much more specific to a certain region, a certain location, a certain group of people in a sense, like if it's specifically for people from Nigeria that are interacting with the Nigerian government, perhaps like open data around the government use, then it would very much make sense to hold it in that location at the very least in the beginning to grow that community and to really strengthen the community. And this really, there's a second benefit to this and it allows designers to really understand what's involved in building a team around open source and how to communicate with an open source. And the process of discussion and collaboration and sharing that is inherent within open source software and the kind of coding community that we're again beginning to explore as designers. So this is really, really important location wise. Eventually we'll be able to move to more remote processes, I think, but the moment it does really matter about making things location specific. And in Taipei we trialled actually doing a different format. So in Bangalore we did a full one day workshop where we did about six or seven hours nonstop except for with breaks for lunch and coffee. And they did that whole workshop within a day and in Taipei we split it into two workshops. So we did four hours on a Saturday within the conference. We did a remote week of activities where the teams could self-organize remotely. They were given tasks that they could do each day that typically would take around anything from about half an hour to an hour of somebody's day, depending on how they split up the different work and when they wanted to do different pieces of work.  And that worked really, really well in a lot of ways. But again, we were trying things out and seeing what worked well for the design community. We're trying out a lot of new things within these processes. So there's a format for that as well that is again open on our repo. So first learning from the open design workshops was location specific and building community very important. The second thing is a little bit more specific to the actual workshops that you do. So inviting what we called a witness to the event. This is absolutely essential. It's absolutely critical. I actually would not have gone through with any of the events if I wasn't unable to get witnesses for the events. And what a witness is is sometimes you might hear them called users or you might hear them kind of called like users or personas. It's basically people that use the software basically in a lot of ways. But it's so much more important within the use case that we were doing which was crisis around our tool ten four. It was much more critical to call them something different to call them something more sympathetic. Call them witnesses because they were there and they witnessed the crisis and they were affected by the crisis. It humanizes their participation and it legitimizes their participation in a way that often isn't afforded to the kind of label of user in a way. So they were critically important to the workshops that we did. So we had in the Bangalore workshop we had a person called Akila come along and she had done a lot of work within an NGO with the populations in Kerala and produced a really comprehensive report on the process of the flood and what happened and who was affected by it. And in Taiwan we had two people from an organization one rural farmer that actually sadly had his farm devastated by a typhoon and a person who helped organize the volunteer response to not only that farmer but other rural farmers in the area and then organize a community group or an NGO afterwards. I can share the links for the places that these witnesses worked and the information of how to find out more about them. But they were involved in the whole process so there was briefings for them prior to the event and why we wanted to involve them and how we wanted to involve them and how we valued them. And also they were there throughout the whole event as the designers were working on the issues or on the challenges. They gave around a 30 minute or an hour long talk about how they experienced the problems that the designers were going to be solving within the open source software. So they had the chance to really speak from their own experience because that's vitally important within designing better experiences for not only commercial tools but also open source tools. And they were also there to, so the designers within groups could ask them questions at any points if they weren't quite sure whether they were on the right track with what they were designing they could validate their assumptions and they could validate their direction with the witnesses and they also were there when the designers would present their prototypes at the end so they would show what they'd created within that day for their open source design contribution and they were able to have that feedback with the witnesses and say the witnesses would be able to say hey this wouldn't quite work in this situation for these reasons and that really is the direct feedback that designers need to iterate on the things that they're doing so they're actually not only creating open source design contributions but the best kind of open source design contributions for the use case that they're designing for so what we're really trying to do is not just have a design contribution that's created in isolation but that it's created in this really user centric, witness centric and really specific to the tool kind of way so that's why it's vitally important to include witnesses and a slightly connected note as well is also vitally important that you pay your witnesses it's hugely important that a lot of these people are taking time out of their own lives and their days to be there and participate in this process so we made sure that we paid our witnesses their time or if they didn't want to be paid themselves we made donations to their NGOs or the community groups that they were organising and the link there on the screen at the moment is the brief that we sent to witnesses and the information about how we decided or how we explored the idea of witnesses within open design so the last finding from the open design workshops that we did was something that I've talked a little bit about already so translating issues into design challenges and there's an example here on the screen within the open 10-4 repo on the Oshihidi account this is an example of an issue that we took from sort of very technical issue language through to a design challenge language and this was one of the ones that we took through to the workshop in Taipei in Taiwan and this is one of the ones that works really really well and it's sectioned in different ways and it really is carefully constructed in that it has a section for describing the challenge it has a section for describing the people that are going to use that function, that feature or the people that you need to design for it also has a section around constraints so things that need to be in place for you to be able to design so this is the bit that makes the implementation a lot easier so the designers understand the limitations or the restrictions that they're working with i.e. the example is that a lot of the challenges that we were working on they had to assume that the people that they were designing for were already part of the system so they'd already been added onto the 10-4 system in some way shape or form to solve that challenge so we took these restrictive issues or these issues that were very technical and we translated them into the design challenges we still have some work to do on this really because what you can find within the design challenges is even when they are created collaboratively with your technical teams or with people that are going to implement things it's really hard to not want to describe the solution that you want or to describe the thing that you know that you can implement and it's a really tricky place to be because what you want to know within any kind of software that you can implement the solution but what you really want to do by engaging designers within this is understand whether there's actually a more valid or a more beneficial solution that you haven't discovered yet so you really want to allow for that design discovery that is not prescriptive so that you could potentially discover a really groundbreaking new way of solving a key problem that your users, the people that are using your open source might have and you can do that by engaging these designers and balancing really carefully between restrictiveness and open to design thinking and design interpretation so to move on to the outputs that you get as actual design contributions so we didn't really want to restrict people too much as to what their design contribution would be but we did suggest that one of the best things they could do is offer a prototype and to be able to offer these prototypes we internally as the open design team created a template file of 10.4 the open source software so we had a Adobe XD file Adobe XD is a prototyping tool that Adobe create and it's the tool that we use internally in Ushahidi on all of our tools so it was the tool that made sense to use so we created this template so it basically had every single screen within the tool within the live open source tool and it also had a design, what we call a design system so all the different elements within that tool and we created that and we made it available to the designers to explore and to use and to pull pieces out to redesign certain pieces of the UI, of the visuals and it gave them like a starting point because one of the hardest things to do with design contributions is not really having a starting point and also not really knowing exactly what the system the open source software system actually looks like and how it operates and if that how it operates the barrier is that you need to do this cloning of a repo and creating a local instance what this does is it bypasses that process of needing to do that and it actually allows the designers to see oh well this is how it's set up at the moment and we can solve this design challenge within our groups and contribute this design open source in an open source way by using these certain elements and we can really clearly see how it's structured so the designers would create a prototype often the prototypes didn't have to be a certain way they didn't have to be this many pages this many functions they didn't have to look a certain way or anything like that it was really to see what happened and what we could create within teams after one workshop and what was feasible within that and also to add to the kind of sort of limited timing of a prototype it was actually great to give them a stopping point as well because then the witnesses could give them feedback on what they'd already created and they could actually change things for the next iteration of the open source design contribution so prototypes are really really useful but we also got other contributions in other ways so documentation, sketches we got the empathy maps like empathy maps that were created for the different users both digital and physical ones so physical ones with post-its and paper and digital ones we used a tool called mural which I can share and we created a lot of different templates that they could use especially when they were doing a remote sprint so there were lots of different things that ended up as contributions lots of different artefacts lots of different insight, research understanding that ended up as open source contributions to this project and to now kind of move just a little bit into the future so those are a lot of what happened within the open design the first phase of open design essentially so this was about six months of doing all the different kind of end to end open design work so right through from starting the project and setting up all of our cons and outreach and starting to formulate all of the different things that we wanted to deliver right through to finishing our last event this was what we did within that time period and I've not actually mentioned it yet but it was actually funded by Adobe so Adobe have a fund which is called Adobe Fund for Design and we received funding enough for a very small team of people to deliver this over the course of around six-ish months in 2019 so the future of open design I think is really really bright and it's really really fantastic that we were able to do this project through the support of Adobe and really what we're looking at continuing is increasing and sustaining contribution to tools like Oshahedi's 10.4 but also to other open source projects as well so taking what succeeded within the open design project on Oshahedi's open source tools and really making it known that you can use that for all the other open source tools that you might want to use it for supporting a community of collaborative and peer led designers learning new skills and working together and mentoring each other we do that alongside the open source design.net community who have been doing this work for around five or six years now we really want to do more building of understanding between design and open source and we want to help open source projects better understand design and the design community better understand open source and we need to do that at the same time and as synchronously as we can so what we really want to do is build that understanding in a really compassionate way so that nobody feels like one function or one sector is taking advantage of the other and that we all understand each other's aims and goals with open source design and then bringing open design to education and workplaces so this goes alongside the understanding within the community it's about getting into those educational practices educational institutions and getting into those workplaces and making open source design contribution a part of a designer's experience as a designer and likewise with developers and with open source projects making understanding design and working with designers a part of their process to do so really what we want to do by being virtually at Fossasia is we want to build more relationships with open source projects and start to understand how we can deliver these kinds of workshops for more open source projects and build communities around these with designers and we want to build the same relationships with designers and developers globally because when you isolate this kind of experience this kind of project to one place in the world is where a huge failing can occur especially when you've got open source switches used across borders so lots of open source tools are multifunctional for lots of different kinds of people in lots of different countries and it would be absolutely foolish of us to not want to grow the community and engage with people everywhere and not just in the places that are convenient for people leading these kinds of projects and initiatives it's really a global initiative it's a global need as well to participate with everyone in this process so you can find the open design like open stuff on this link here the github.shihidi.com so it's got the methodology there it's got all the frameworks that we use to create the workshops it's got the processes it's got a lot of our learnings a lot of writing and articles and a lot of our positions on certain things it's got a whole lot of interviews that we did and all the research that we did before we conducted the workshops as well so if you want to contribute to any of the things within the open design project as well it's fully open and you can do a pull request for any of those pieces of information and you can fork that repository and modify it however you see fit and use it widely, use it energetically and use it in the ways that you think are best and lastly if I can leave you with the link for the community of designers with an open source which is the opensourcedesign.net community so this is where designers that have had an interest in open source collect and congregate and communicate for many many years now and I'm part of the core team there I lead some of the meetings and I do some of the sort of welcoming new people there and coordination but there's a whole load of amazing people that also coordinate and lead this group so you can find a lot of those core members within the forum that's on the website and you can also find a section on that website where maybe if you're not quite sure what your first design issue should be or how to engage with designers you can add a post on the forum the discourse forum on this website asking for support so anything from oh we actually know that we need a logo or a set of buttons or we need some UX help or we need some user interviews for our open source tools and we'd love a designer to help us with those right through to we're actually not really sure how we can improve this tool but does a designer want to take a look or does a designer want to have a synchronous pairing session where one of the developers, maintainers of an open source takes them through the tool and they can do some feedback there's also some great first design issues that I can suggest and I have a Twitter thread on so again if you want to know what some just good first design issues that you can create are that are very exploratory to sort of test out the waters of design engagement then please find me on Twitter you can find my Twitter handle on the bottom left hand of the screen there at Errol does design and you can find the open source design team at OpenSRCDesign on Twitter as well so I'd like to thank the Fossasia folks for screening my talk I hope that you found it interesting and informative if you want to talk more about open source design open design any of the things that I've talked about throughout this talk then please contact me in any way that is most comfortable for you I'm on most channels and I believe we'll be doing a Q&A as well so thank you very much for listening and now I must find how to stop the recording so thank you very much, bye bye


If you've ever known someone that was a really good person, and yet no matter what they did, they never got the results they wanted in life, it's actually a really sad scenario. They followed all the rules. They did what their parents said. They played by all the things you're supposed to do in society. And yet, for lack of a better word, they ended up losing. Now in this video, I want to share what I think are two or three reasons why even good people fail at life. What's up guys? Alex Hein here, author of the book, Master the Day. Now, the very first reason that I think even good people fail at life is because they don't have what Andrew Carnegie called a definite major purpose. In other words, they don't set goals. You know, when I had my first really professional desk job, it was essentially the same thing every day. And there was nothing wrong with it.  It really, really quickly falls into routine. And at some point, everyone falls into routine, especially when you're working a nine to five job. It's just the daily process of life. But the thing is for most people, when they get into that routine, they take the easy route. And the easy route is usually coming home, watching TV, hanging out on YouTube, playing video games, or just getting drinks every night with friends. Again, there's nothing wrong with that. But what it doesn't guarantee is a life of growth. How many people actually sit down every day and they're like, you know what? Even if it's not building an empire, they're just like, these are my goals.  They write down what they want to have happen in their lives. And then every day they just look at it. Like that by itself is so basic and very few people I'd wager less than 5% or maybe less than 1% of the world actually does something that simple. So you can be a good person, but you're stuck in the routine and the grind of day to day life. And you're not consciously thinking about what is the active growth goal that I'm going towards. Now the second reason that I think even good people fail to reach their goals in life is because they listen to fear and they make their decision based on that fear. Not the excitement or the passion or the love or the cool stuff, the dream that they want to create. You know, 10 years ago I already knew that I was passionate about integrative medicine and learning about medicine and herbs and meditation and mysticism. But you know what? When I talk to the people I respected and admired, my mentors, advisors were my family. And my parents and my grandparents were like, you know, integrative medicine, like naturopathic medicine, Chinese medicine, is there any money in that? And they meant well, right? They want to see their kids succeed and be able to provide for themselves. But the thing is I did not decide to do what I love the most until 10 years later. I'm 31 now, halfway through my doctorate because I caved to the fear and not the excitement and the love. And there are plenty of people doing great in my field. But you see the same thing in terms of travel and marriage and all the way that people live their lives. I mean, look at the number of people that get married because they're like, well, I'm 30 and I'm a female. I guess I'm not going to find any other guys that are as good as this dude, even though he's not really that great or he's not really what I want. And then they settle because they're like the clock is ticking. I got to do this. That's a major decision made by fear and people do the same thing with travel. There are those amazing adventurous far off places they want to go for the cool adventures, the best stories of anyone they know. But what do we choose? We choose the safe places like Europe. We go to Southeast Asia. We go to the places that are easy. Not the ones that are going to create the best life stories and are the most exciting. And I think so many people get caught up in caved, getting caved and beaten by that fear rather than this is the exciting, amazing life. I'm going to do it no matter what. Now, the third reason that I think good people don't live a great life is because they don't commit. Now, the difference between being interested in something and committing is that a person who's committed like in a marriage or a long term business deal or towards a goal, they will do whatever it takes as long as it takes. You know, sometimes I wonder if there's actually anything special about what I've done compared to other friends who started at the same time and now don't have anything or don't have any business or any kind of audience. Besides the fact that I committed and I told myself I promised I would do whatever it took as long as it took to be able to earn my freedom doing work that I really cared about. And it was a really difficult process. But I think people think that after three weeks they're going to have the dream body. They don't commit until they get there, as one personal development speaker said. People say that they want to go to Paris so much, but they only can save 10 bucks a month. And so they're like, well, screw it. It's not worth it. It's never going to happen. Rather than I'm going to commit until I have the $3,000 to go on this Paris trip or the same thing in relationships, people like they're so easy to give up rather than work through the thing, figure it out and commit until whatever it is they want. It's one of those things where if you have not been committed to a goal for an extended period of time you may not know that you're giving up way too soon. So if instead you said, this is what I want. The body to write a book, the business, the marriage, the relationship, the travels. And instead of thinking, I'm going to give it my best and do three weeks or three months or three years. Commit, which means you're going to do it until it happens. That's a scarier thing. It takes longer. And I think if you factor in, here's your goal. You're going to commit. You're going to do whatever it takes as long as it takes. Then chances are you're eventually going to get there, no matter what. And you're not going to be like the 95% of people that give up on their dreams so soon. Alright guys, so I hope that helps. Those are some thoughts on why I think even good people fail out life. Now, before you go, I want you to leave a comment there below. Let me know what you would add to this list. Do you know someone who's a legitimately good person, but their life is just not that good? And you're kind of wondering why. Comment there below. Alright guys, best way to stay in touch is to grab my free personal development and weight loss challenge at modernhealthmonk.com forward slash YouTube. And you can check out my last two videos right here and right here.


This study investigated the efficacy of a novel vaccine for COVID-19, called DNS-1-RBD. This vaccine was found to be effective against multiple strains of the virus, including those that have evolved since the initial outbreak. It also reduced the severity of symptoms and decreased the amount of virus present in the body after exposure. Additionally, it reduced inflammation and prevented overactive immune responses which can cause further damage to the body. These results suggest that this vaccine could provide broad-spectrum protection against all strains of the virus, making it an important tool in the fight against COVID-19. This article was authored by Liang Zhong, Yao Jiang, Jin Hang He, and others.


Hello everyone. Thanks for coming in at such short notice. I'm Ian Stewart, the Deputy Commissioner for Regional Operations. My colleagues obviously Steve Hollins, the Chief Superintendent and Operations Coordinator from Southeast Region and the Deputy Commissioner for Queensland Fire and Rescue, Mr. Ian McKenzie. I'll make some, when you're ready, I'll make some brief opening comments and we'll open it up to questions from that point if that's alright. Okay, so everyone's okay at the back? Thank you. Good afternoon, ladies and gentlemen. This morning at Kingston in Brisbane there was a terrible tragedy, a house fire which resulted, we believe, in the deaths of 11 people. The people who perished rage in age from three to 47 years of age. We also believe at this stage that there are two main groups of deceased who belong to individual families and there is one further person who is a who is also related to one of those families. I wish to place on record the condolences and sympathies of the Queensland Police Service to the extended families of all of those who perished and certainly also to the local community. I believe the community is in shock in the Kingston area where this tragedy has occurred. There is a significant support structure being put in place to address the issues surrounding the community issues at Kingston in terms of the outpouring of grief that's occurring down there. There are a large number of church organisations and police chaplains have been dispatched in the early hours of this morning to assist in that process. There is also significant support from the Salvation Army and a support centre has been opened at a Salvation Army facility in Barden Road at Saxe Creek. I'd like to acknowledge the great work of both the Queensland Fire and Rescue Service and Queensland Police in dealing with this tragedy. Many of our frontline officers have been confronted with a with the terrible tragedy that's occurred. Certainly there are large numbers of support staff now working towards the investigation which will report ultimately to the state coroner on the outcome of that investigation. Again I would also like to highlight the fact that there is a need for privacy for the families and the community in that area at this time and our investigation team will be in place for a significant number of days while this investigation is undertaken. A major incident room has been set up at Logan Police Station and there is a forward command post near the scene of the tragedy. We will be guarding the scene continuously until the investigation is completed. We are happy to take any questions that you may have. I perhaps I could hand to Mr McKenzie in relation to that. Thanks Mr Stewart. In relation to the cause it is very very early days. I was on scene this morning and the crews there described to me what they were faced with. It was a very intense fire even then when they arrived so working with police investigators the scenes of crime it will be quite a painstaking process to try and get to the exact cause and it won't be something that's achieved in the short term. When will the house be safe enough that you can go with Andrew Covey's voice? The Queensland Fire and Rescue Service, Urban Search and Rescue teams have been working on site through the day making the floor safe for the investigators to go in. All I can say is it'll be as absolutely as soon as possible to try and bring some closure to the families and the community but obviously safety is the precedent. Are you still treating it as unsuspicious? Yes we are at this point in time. Are you seeing photos of the victims? I doubt very much whether any photos will be released at any time in the near future because those photos become the property of the coroner in terms of the ongoing investigation so it'll be a matter for the coroner at some stage. And what about the ages and details of the victims? Certainly at this stage I know that some ages have been released. I'm simply telling you today at this time the ages range between 3 and 47. How many of the 11 actually live in that particular premises do we know? Steve? Look there were 13 people there at the time. At this stage whether it appears their household was asleep at the time or whether people were awake with the fireplace? We do understand that everyone was asleep except one person. It's fairly early at this point in time but that's how understanding. Why was there really any indication of how they? Two got out through windows and one person was already outside. Which one did they get? One got out from a window at the front of the premises and another got out from a window at the side. Were there other people trying to escape behind them once they left? Or did they not know where the other families were at the time? I think ultimately the investigation will look into all of those facts. This is very very early days and you can just imagine how traumatised those three survivors are. So whilst there has been some preliminary enquiries made with them obviously a more fulsome investigation will be required. Given the extent of the fire when it broke out was there any danger to neighbours on either side of the property? Certainly the intensity of the fire did cause some superficial damage to neighbouring properties and that was the focus of the crews once they realised obviously that rescue was not an option to protect the properties on either side and that's what they said about doing. Can someone share with gas cylinders? Certainly at the side of the premises there were four large domestic gas cylinders all connected to the house and all of them were involved in the fire so they added to the problems. There was also two vehicles that were well involved in fire in the front and the side. All of which posed problems and risks to the firefighters. Can I just clarify, you say that 13 people were in the house but we've got that three people survived and 11 people. Sorry it would be 14 years. So obviously it was an intense fire, how hard is it going to be to find out what caused this fire? The investigating process will be a painstaking one for both the police investigators and the fire investigators. They do look for certain traits and things that point to where the fire started and then look in that area for anything that would have been likely to cause it and certainly statements from the survivors will be all important. Are there any closer to knowing if there were smoke lines better than the home? At this stage we're no closer to. I'm sure that will form part of the police and coronial investigation and that will come to light. You mentioned statements from the survivors. Obviously they're doing a lot of trauma. Have you managed to interview them formally yet? It's my understanding that at least one of those has been interviewed but as I said before the degree of trauma that's been suffered and the hurt and pain obviously there will probably need to be followed up in investigations and further statements before we can be definitive. Any idea of the injuries that they might have sustained? I understand that one person suffered a possibly a fractured shoulder and I think the others got out okay without any injuries. He's at the moment, yes. What did it take from your agency services to arrive once they've received that first call? The first fire crews were on scene in under seven minutes and the first call was received just after four minutes past midnight. How many calls did you receive? There were many triple zero calls. I think that they're going to need counselling themselves. For all the emergency service workers on scene certainly all the emergency services offer support and guidance to our crews. In the first instance we try and do that as quickly as possible if they would like and that has happened already today and that support will be ongoing. Obviously until the investigation identifies the actual cause we have to treat this as suspicious but at this stage we haven't got anything that is deeming it to be suspicious. The major incident room is set up as we do with every major investigation to ensure that the investigation is absolutely thorough and rigorous. Folks unless there's anything else that you'd like to ask us? Ian McKenzie, Deputy Commissioner, Queensland Fire and Rescue Service. M-A-C-K-E-N-Z-I-E. Stephen Hollins, Chief Superintendent, Operations Coordinator, Southeastern Police Region, Service Paradise. And Steve's been on site since about... Probably at five o'clock this morning. So he's been managing the police response as is appropriate in the circumstances. I suppose we could say that we...


Hey, Psych2goers. Are you having trouble in the romance department? Maybe you're really into someone but can't tell if they're into you. One minute, it's a yes with them. The next, it's a no. So do they like you or not? Well, here are six signs that they're not into you and just aren't telling you. Number one, they aren't engaged in your conversations. Take a close look at their face next time you're talking with them. No, not just their dreamy eyes. Stop it! Notice whether they're actually listening to what you're saying during your dinner dates and if they're engaged in your conversation. Are they on their phone? Are they scanning around the room directionless? Are they looking at someone else or something else? Their pasta perhaps? Well, I would too if I was eating good pasta. But that's besides the point. If they don't engage with you often on an emotional level or even any level during your outings, then it looks like a no in the relationship department for you too. Number two, they don't communicate or text consistently. Do they text you regularly? Check your phone. Go ahead. I'm waiting. When's the last time they texted you? Eight hours ago? Eight days? All right, years. I'm just kidding on the years part unless you're long lost friends. But if they don't communicate with you often, texts are no text. It's a sign they don't care enough about you to pursue a deeper relationship. The only relationship they're in is the one with their pasta. Pasta puttanesca! Number three, you're the only one always making plans. Who's making the plans in the relationship? Who's asking who out? Who's initiating the conversations about availability people? If they're not putting the effort in to even ask you out or at least hint at your availability, they may not be into you. If they've grown distant and asking you out and you haven't seen any effort from them and going out, and doing things with you in the real world, they may not be as interested as before as well. Number four, your relationship with them is one-sided. Are you both benefiting emotionally from this relationship? Are you both supporting each other? Hearing each other out? Or do they just come to you with their problems, but don't listen to yours? Do they always pick the dates when you go out with them? Are they putting in extremely minimal effort? This could be a sign they aren't really into you for a long-term setting. These signs indicate your relationship could be one-sided, so it's best to sit down and talk about it or call it quits. There are more hard-working fish in the sea, ones that will mutually give you that attention and support you deserve. Number five, they're just hearing what you have to say, but not really listening. So we've covered engagement, but when you're discussing serious topics with them, are they really listening to you or just nodding along and then completely changing the topic? A healthy relationship requires communication and some active listening. Honesty is also key. If they cared about you, they would listen to what you have to say, respond thoughtfully, and continue the conversation, especially if it's on a topic you care about. Why? Because they care about you. And number six, they've told you that they aren't ready for a relationship. Buzzkill, but it's true. It's time to face the facts, my friend. If they've told you they ain't ready, they ain't ready, even if they subtly hinted at it. Ask them or take the hint. It's best to be on the same page with your partner. It's healthy. So if they've told you that they aren't ready for a new chapter with you, or rather they're ready to close the book on your potential romance, then it's time to close the book. And head to the library for a new one. Odds are, their book of choice will be a pasta recipe. If we're talking about the literal sense now. Pasta putlanesca. What? Who doesn't love pasta? Leave me alone.  Like you or like you not? Do you even like them? Do you like pasta? Do let us know in the comments down below. We hope you enjoyed this video and if you did, don't forget to click the like button and share it with a friend. Or that person who's not that into you. Too soon. So subscribe to Psych2Go and hit the notification bell icon for more content like this. As always, thanks for watching. See you next time.


Using the Global Innovation Index framework, we are able to collect data and metrics to assess the results of innovation in different economies. This year we collected data on 81 different variables and we use these different data sources to assess innovation trends in 143 economies of the world. So at a very simplistic level, if you think about which economies are doing the best, you see a lot of familiar countries out there. Of course you have a mix of both European and American economies, but what is also interesting is you see some Asian economies. So Switzerland is ranked number one, you have US ranked number six, Singapore ranked number seven and you see that in the top ten, innovation really has become a global game. So there are hotspots or bright spots of innovation across the globe. It's not just localized in any one part of the world. At the same time, if you look at a little broader range of countries, you see that in the top 25 things haven't really changed. And this basically shows how innovation divide exists in the world and actually persists over time. And if you have the benefit of looking at trends over time, this raises a very important question for policy makers in different economies about how to overcome and how to cross this innovation divide across economies. Now, if you look at these economies that are performing well, you notice that one thing in common across them is they all perform uniformly highly across all the different dimensions. If you take a slightly different analysis of the data, you can compare economies and look at the performance compared to other peers. Peers as probably defined by income level to GDP levels. Now, if you look at these peer comparisons, you start seeing some interesting trends. You see, of course, some of the leaders performing much at a higher level of innovation output as compared to some of their peers. Switzerland, US certainly outrank their peers for similar GDP or wealth levels. Now, if you look at some other countries, you see some interesting trends. If you look at, for example, the middle to high income economies, you see some countries like Moldova, like Mongolia, like Vietnam, Jordan, Senegal, who are outperforming. You see, for example, China, that is today ranked at position number 29. And this is a phenomenal ranking. In fact, a very dramatic progress over time of the last few years. And I would not be surprised if China keeps up its rate of progress if it soon hits in the top 25 and is really counted amongst the most innovative countries in the world. If you look at lower income economies, you also have interesting names and interesting results out there. You see economies like Kenya, Uganda, Mozambique, Moldova, and Gambia. These countries are also coming up and they are in fact performing better than their peers in many respects. So once again, you have an element of comparison which gives us some hope that some economies are in fact moving forward at a faster pace and learning at a faster pace. In fact, we term these economies that are outperforming their peers to be innovation learners. Now there's another interesting metric that we can in fact include and measure inside this analysis, which is looking at what is the efficiency of innovation, comparing and dividing the output by the input indicators. So at different levels of performance, how efficiently does a certain economy transform its input parameters and input conditions into actual output results? And what we find is once again some interesting new names come up as some of the leading countries in this sector. Gambia, Senegal, Kenya, these are names that are ranking very high on the innovation efficiency metric. And to us, they indicate important trends for the future because they show which economies are learning faster and where probably a lot of the future growth in the economy and other interesting new innovative ideas will emerge in the future. And this is an important lesson for business leaders who want to choose where to invest. The R&D resources or setup manufacturing plans is an important element of indicators for government leaders who are looking for best practice examples. Not every country can become a Silicon Valley. What is there in the US is very unique. What is there in Finland is very unique. Not every country can become another Finland or another Switzerland, but every country can learn from others. So what these other examples give us really are inspirational stories, examples that we can learn from and hopefully leverage these better practices and integrate them in economies to become more competitive ourselves in the global economy.