So welcome to our webinar on the Golden States. Today I'm happy to introduce two of our California documents librarians, Lucia Orlando and Jesse Silva. Lucia is the government documents coordinator and research support librarian for arts, humanities, and social sciences at the University of California, Santa Cruz. She's a NorCal native with a keen interest in local history and politics. And Jesse is the librarian for federal and state government information, political science, public policy, and legal studies at the University of California, Berkeley. And he is a native Californian as well. So thank you very much. Thanks Linda and thanks Jesse. Welcome everyone. We're so glad that you could join us today to talk about some California issues that are reflected at the national level. We hope by the end of our talk you'll have a better understanding of issues being championed by California and where to go to find more information about these topics. We have a lot to cover, but don't worry. We'll provide a list of links to all the resources we mentioned on our slides and with a few more at the end. Now Jesse is sharing the webinar so you'll hear me let him know to advance our slides whenever I'm speaking. Here are the topics we're going to be covering. Politics, a little bit about agriculture, the environment, mainly about our changing climate, information about energy, immigration, and open data. So the title of our talk is California issues reflected at the state level. Most of you probably know California has challenged federal policy in the past. So the current opposition to federal policies is not a new phenomenon. For example, California filed suit to defend the constitutionality of federal health care reform in 2013. And so the EPA in 2008 over California's right to set stricter air pollution standards. And then going way back, California also challenged the federal government over the right to institute the use of medical marijuana starting in 1997. With this in mind, we'll hope you'll come away with an understanding of these outcomes, basically an understanding of the forces shaping pressing issues in California, and give you a sense of the rich variety of resources that are available from both state and non-government policy experts. So the image on this slide is of the California.gov website. If you haven't had a chance to use it, I strongly encourage you to take a look. Like the North Carolina website, it's designed to address a variety of audiences and needs, like living in California, working, living, and doing business in California. It's powered by a really good search engine, so you can find resources we show by typing in the name. We do always have to have the URL. It's true. California is big. Before we launch into things, a little context is in order. It's important to bear in mind that California is a really large state, as you can see from this slide. This map shows a reverse image of California, with San Francisco overlaid on New York City, to give you a sense of how big the distances between coastal cities and the Central Valley farmlands are. Basically, California is a big state with a variety of people, viewpoints, and economic conditions that make for very interesting politics and policies. We wanted to have some fun and kick things off with a quick trivial quiz called How Much Do You Know About California? We'll be interspersing these little quizzes throughout our talk. Most of these are true or false questions, so please add your answers to the chat. Here's the first one. Put your answer in the chat box. The question is, the nine counties that compose the San Francisco Bay Area consistently vote to support both socially and physically liberal positions? Actually, the answer is true. Well done, everybody. I know it's surprising even for people who live here, but let's get into the political picture a little bit more. So when you see a map of California counties color-coded with their political leanings, it's easy to think that the state is split pretty evenly between Democrats and Republicans. And depending on your color preference, you might even think that the state means a little bit more Republican. And this is because the state population is unevenly distributed with conservative voters more likely to be dispersed throughout rural or less populated areas. So this next slide actually changes the size of geographic areas based on population density, which makes the rural population place and touching the political makeup of California much more apparent. You might need to enlarge your screens a little bit more to really see this, but this slide really helps conceptualize how much influence the heavily populated San Francisco Bay Area and Los Angeles area have when it comes to statewide elections. This particular slide came from a report issued by the Nonprofit Public Policy Institute of California, or if we just call it PPIC. They're an excellent source of nonpartisan objective information about California politics and provide background of pressing issues. PPIC regularly surveys Californians to solicit their views on issues like politics, education, crime, and the environment. The most recent addition to those theories titled California's Future, Political Landscape, presented findings that provide good insight into the makeup of the California electorate. So now that you've seen the role demographics plays in state political makeup, it's important to note a few other things about political leanings in California. So California has become a part of the Democratic state over time. Starting in the 1980s, California started to move away from voting Republican and national and statewide elections. This trend accelerated in the late 90s, which Jesse will provide some insights on in a little while. Today, the California legislature and officials in other elected offices are primarily affiliated with the Democratic Party, which makes California one of the most predominantly Democratic states in the U.S. And it's important to note that there are varying shades of liberal in the state. So the San Francisco Bay Area, according to the public policy, to PPIC, is most strongly liberal on both social and fiscal issues, whereas other areas of the state tend to lean more moderate to conservative. So independent or declined state voters are also a fast-growing group who make up a little over 23 percent of voters. While they vote independent, about 60 percent of them tend to lean Democratic. PPIC surveyed Californians and found that in California, 14 percent are very liberal, 21 percent are somewhat liberal, and 30 percent consider themselves middle of the road. 20 percent are somewhat conservative, and 13 percent are very conservative. So that just gives you a little bit of a picture of California, even though we tend to be much more liberal and vote Democratic. It's not a one-size-for-all. Now I'll turn it over to Jesse to talk a little bit more about some things to keep in mind when trying to understand California politics. Probably the most well-known aspect of California politics are the ballot and propositions. These get a lot of press during election times with some weird or crazy proposition on the ballot in California. These propositions are the result of government reforms in the early part of the 20th century to allow direct democracy participation. Anyone or any organization can have an initiative qualify for inclusion on the ballot. There is a process they must follow which includes fees gathering a set number of signatures by a deadline and having the state verify a sample of the signatures. The legislature can also place propositions for constitutional amendments and other issues on the ballot. The initiative process is not unique to California. 26 states also allow initiatives and referendums, but few use it to the extent that it is used in California. Counties in California also allow propositions to be placed on the ballot, and a number of measures placed on the ballot can vary from county to county. Over the last several years, the number of propositions to skyrocket in California, which can lead to a book-length election quote-unquote pamphlet. When I was living in San Francisco, I usually devoted a weekend afternoon to reading the pamphlet. These pamphlets have gotten so large that the NPR ran a story on the 2016 election about California's 17 propositions and San Francisco's 25 county propositions. The propositions also make for hundreds of millions of dollars to be spent on California elections, such as 83 million being spent on during Proposition 8 in 2008. Some of these propositions are not always moving straightforward in a liberal way. Some of these more infamous propositions that have passed include Prop 13, which was property tax limitation, which we'll talk more just a bit, same-sex marriage discrimination, which is Prop 22 in 2008, illegal aliens, ineligible for service, or what it was also called the Save Our State initiative, which is Prop 187 in 1994, which we'll talk more a bit later, and affirmative action being removed from the state in Prop 209 in 1996. A couple additional infamous propositions that didn't pass during the early days of the AIDS crisis, California voted on setting up quarantine camps for people who are HIV positive. This was Proposition 64 in 1986 and Proposition 69 in 1988. Both failed. I guess the point we're trying to get across is California has not always been the progressive state that it's known for now. Another point to keep in mind about the proposition process is that even though a proposition qualifies for an election and is voted in, there is no guarantee that it will be implemented into law. A number of propositions end up in court for various reasons or where they are overturned. This happened with Proposition 187 and eventually Proposition 8. If you want to research propositions in California, there's a database that's provided by UCH beings that has all the propositions going back to 1911 when the proposition started. Now let's talk about Proposition 13. Proposition 13, there are very few political events that have affected California and the California budget, like 1978's Proposition 13. I won't get into all the specifics of what the law does, but the big thing is that it limits property tax, except in a few cases it limits increases in property tax to 1%. I will also say that Proposition 13 cut the revenue generation for the state, resulting in major budget swings over the last 40 years since its passage. One of the reasons for this is it also set a threshold for passing a budget to two thirds of each house in the legislature. It also requires any bill enacted for the purpose of increasing state revenues to also pass by two thirds margin in each house of the legislature. California is the only state where supermajorities are required for legislation that will generate revenue and to pass a budget. Since Prop 13's passage, the state has used the ballot proposition process to enact a number of other propositions with implications on the California budget and its process, such as 1988's Proposition 98, which specified that approximately 39% of California's budget goes to KB Call of Education. Over time, this has preallocated much of the California budget, and according to one legislative member I spoke with a few years ago, the legislature only has power to change approximately 25% of the budget. This can create some strange bedfellows to get the budget passed, with a number of concessions made on both sides of the aisle. In recent years, California has had supermajorities of Democrats in the legislature, but this hasn't always been the case. Now we'll switch gears to a bit and talk about one of the big key drivers of California, California's economy, agriculture. But first, another quiz. Which state produces more dairy and cream, California or Wisconsin? While everybody's answering, I wanted to point out, we felt that with so much attention devoted to the industry in California, like Hollywood and the technology sector, we needed to make sure that California's agricultural sector didn't get overlooked. And if you said California, you win the prize. You win bragging rights. So, yes, California produces more dairy and milk products than Wisconsin. I know, I was surprised, too. I always hear about Wisconsin cheese, even here in California. So, as you can see here, California supplies a lot of the food consumed in the U.S. and abroad. California agriculture needs summation in many crops and livestock commodities. This is especially true for nuts like almonds and pistachios. And a lot of that surplus is also exported. So you can see the top five export markets. And again, our top exports are almonds, wine, which is not too surprising now. And I was a little more surprised to see rice and hay make the top of that list, too. So agriculture is a big business that needs lots of workers, land, and water. And agriculture is very vulnerable to the effects of climate change, which brings me to our next topic on the environment. But first, a quiz. So, how many inches of sea level rice have been measured along the California coast in the last 100 years? I'm impressed. That's right. Seven inches it is. Go ahead to the next slide. Really, the conversations about the California environment and energy use always come down to a discussion of climate change. That is the driving force when it comes to talking about the environment in California, as well as energy usage and energy production. Reducing greenhouse gases is crucial.  So together, they're powerful climate warming gases and harmful air pollutants. Methane represents one type of greenhouse gas that would definitely spark some pushback in the state's course to reduce them. This is because the California Air Resources Board has put forth a reduction proposal that could significantly affect California's dairy industry, which is responsible for more than half of the state's coal and methane emissions. So I'd say keep an eye on this. We're keeping an eye on this, too. So really, the changes that we're seeing in the climate are already happening. California has embraced a leadership role in combating climate change. And this makes sense because we have a lot at stake with a huge population concentrated along the coast line, hundreds of acres of forested mountains, and a thriving agricultural economy. All of these things require, excuse me, a plentiful amount of water and the ability to mitigate changes such as as much as possible and adapt to things that we can't change. So what is California doing? The governor's office developed a climate change portal that outlines the multi-pronged approach needed to reduce greenhouse gas emissions. Reducing transportation emissions is key. Although transportation emissions have been reduced by 10% since the early 2000s, this sector is still California's largest greenhouse gas source. It was 39% in 2015. So policies that are being shaped up to reduce greenhouse gas emissions include low carbon fuel standards that aim to lower the carbon intensity of fuels by 10% by 2020. There's also a push to add one and a half million zero emission vehicles or electric vehicles to roadways by 2025. And the state is also working to reduce vehicle miles traveled by integrating land use and transportation investments. There's a plan of foot to add a high-speed rail line between Los Angeles and Coventry Stone, but it's presently mired in fights over the spiraling costs, efforts to secure land along the route, and environmental concerns about some of the proposed areas that rail lines will cross. Water is also a huge area when it comes to mitigation, adaptation, and conserving. So California is working with agriculture and regular citizens to conserve water and employ water-saving technologies. The state is increasing its reliance on cleaner energy sources. California's Renewables Portfolio Standard requires power utilities to provide 33% of total electricity from renewable energy sources by 2020. In 2015, the latest figures available, this target was raised to 50% by 2030. So the states on track to meet the 2020 goal since more than 25% of electricity came from renewable sources in 2016, 2016's the latest year we have available. However, achieving the goal for 2030 will require substantially increasing to move away from natural gas as a power source. Another mitigation strategy is a program called cap-and-trade. Cap-and-trade is an approach that gives businesses and industry more flexibility with reducing greenhouse gases. However, it's expensive and controversial. California was the first state to enact a cap-and-trade program, which was started in 2012, and last year was extended to 2030. By allowing businesses to trade emissions permits, cap-and-trade allows market forces to help determine the cost of reducing emissions. Permit auctions now cover 85% of the state's greenhouse gas emissions. The auctions began in 2012 with electric utilities and large industrial emitters, and then transportation and heating fuels were added in 2015. So the program is controversial due to the expense which gets passed on to consumers. It's also met with skepticism by environmentalists who view it as not doing enough to make polluters stop emitting greenhouse gases. So combating climate change is complex, so it requires a multi-pronged approach. Cap-and-trade is just one part of it. The state is developing a strategy to align traditional environmental and economic benefits of natural and working lands with potential carbon storage. Basically, this means taking advantage of forests, farms, and wetlands to capture and store carbon, since carbon dioxide can germinate from the atmosphere by plants, and store it in vegetation and soils. So moving on to international and national agreements, the saying goes, think locally and act globally. So in addition to uniting with 15 states to pursue climate policies despite federal inaction, Governor Jerry Brown has reached out internationally to involve California in climate agreements and action plans. So the U.S. Climate Alliance is a coalition that he started with the governors of Washington and New York state, and it includes U.S. states committed to upholding the Paris Climate Agreement and taking aggressive action on climate change. So our governor, Jerry Brown, has really gotten around, and I am thinking he also got a lot of press. He attended the United Nations' 2015 climate conference called COP21, and in the lead up to that conference, he started a coalition called Under Two Coalition with Baden-Württemberg, Germany. It's an ambitious international climate action pact among cities, states, and countries to limit the increase in global average temperatures to below 2 degrees Celsius, which is the level of potentially catastrophic consequences. So it's basically a global pact that he started. He also had basically just moved ahead fearlessly in the climate arena, and in 2018, September 2018, to be specific, the state of California is going to convene the world's climate leaders in San Francisco for the Global Climate Action Summit. So that was a little bit about California and climate and climate change and some of the work that's going on on the national and international stage. Now, Jesse is going to talk about the other elephant in the room, which is California stands on federal policies that affect some of the most marginalized people in California. I'm going to talk about California stands on immigration. California now welcomes immigrants. However, this wasn't always the case. I mentioned Proposition 187 earlier. This proposition would have restricted all state services to U.S. citizens, including public schools, public health, police, fire, etc. The proposition passed in 1994 but was quickly challenged in court and ultimately was never enforced. This racist proposition galvanized immigrant communities and over the last 20 years since the proposition was voted on, these communities have built strong political coalitions and networks, making California strongly supportive of immigrants and in 2014, Jerry Brown signed a bill to remove Prop 187 language from state law. Now that California is very supportive of immigrants, nearly one in four native-born Californians have at least one immigrant parent and many of my friends growing up fit this mold. Several of the large tech companies were started by immigrants or children of recent immigrants and according to the American Immigration Council, nearly 800,000 immigrant business owners accounted for 38.2% of all self-employed California residents in California in 2015. These businesses also generated $21.8 billion in income that year. Since Brown was elected in 2011, he and the legislature have made California a more welcoming environment for immigrants, creating a number of websites detailing state services for immigrants, including a page from the Attorney General on immigrant rights, which has linked to a number of resource guides. And California just announced in the last couple of days a lawsuit against the federal government over the inclusion of a suicide question on the 2020 Census. California also created a special driver's license for undocumented residents. Under AB 60, which was passed in 2014 and went into effect January 2015, California allows undocumented residents to qualify for a driver's license, which enables them to obtain auto insurance. This license is only valid in California and has a noticeable stamp on it, making it known that it's only for driving and to obtain insurance in the state. It cannot be used for federal identification purposes, such as going through airport security or going through customs of border crossing. And it doesn't qualify as a driver's license outside of California. Since implementation, California has issued over one million AB 60 licenses. And I love the little note at the bottom of this DMV graphic. This design may change because Department of Homeland Security wants California to have the AB 60 licenses a different color, but the DMV has no plans to change. California is also very supportive of DACA, the Deferred Action on Childhood Arrivals. This is a program that's in the news a lot. It started under the Obama Administration for undocumented immigrants who came to the U.S. as young children and have lived in the U.S. entire lives. After meeting several requirements, they register with the program and cannot be deported. California has the largest number of DACA registrants with over 424,000 as of March 2017. And many of these registrants are college students for which the state has been very supportive since around 2001. A key point in this is that most Californians recognize that a child cannot be held accountable for the actions of their parents. Assembly Bill 540, passed in 2001, allows for undocumented immigrants who meet certain criteria, including graduating from California high schools, can qualify for in-state tuition at California Community Colleges, California State Universities, and the University of California campuses. They can also qualify for some state-sponsored student financial aid via the California Student Aid Commission. In California, it will be the only state that has programs like this for students. Several states have passed similar legislation, including some red states you might not expect, like Oklahoma, which passed similar legislation in 2004, and Nebraska, which passed legislation in 2006. Having worked with a number of dreamers over the last few years, I see them as extremely hard working, sometimes holding down two jobs to go to school, and they really do dream for a better society and are willing to work to put the work in to get us there, even if it risks then being sent to a country they've never lived in. DACA recipients also pay California income tax and can qualify for state-sponsored Medi-Cal and several other state programs. The state maintains a guide for DACA recipients that is updated regularly on this rapidly changing situation. And now, we're going to talk a little bit about California's sanctuary state law. But first, another quiz. Which state was the first sanctuary state in the U.S.? Little hint, it was not California. So the answer is it was Oregon. In 1987, Oregon passed a sanctuary state law preventing local and state law enforcement from working with federal immigration officials. And this law is actually going to be on the is up for referendum this coming fall. So immigration has gotten a lot of media attention over the last several years, and especially since Trump has come into office, and Trump has been targeting, the Trump administration has been targeting undocumented people living in the U.S. Prior to Trump, several cities in California and across the U.S. enacted sanctuary status, where the local law enforcement is directed to not cooperate with federal immigration officials except under specific limited instances. This has gotten much stronger under Governor Brown. In 2017, California passed SB54, the Law Enforcement Sharing Data Act, also known as California's sanctuary state law. California's sanctuary law forbids state agencies from asking about an individual's immigration status, unless it's specifically required like for the BNB licenses. It also forbids law enforcement agencies in California from sharing data and working with immigration and customs agents, except in cases where the person has the history of being previously charged with one of more than 40 misdemeanor or felony charges. During the passage of this legislation, the Senate and Governor Brown did a lot of negotiating, and one of the concessions made by the legislature was that Brown wanted to expand the list from less than a dozen of these misdemeanors and felony charges to what we have now is over 40. The law also does not prevent ICE immigration and customs enforcement from intervening people in prison or in jail. A little bit about open data in California. Over the last several years, California has become a number of open data initiatives, and the main portal is data.ga.gov. This website provides access to data from 14 different agencies, including the California Department of Transportation, Caltrans, and the Department of Water Resources, and the Department of Justice. You can find data by topic, search for specific data set, or browse by agency. This site also publishes events like hackathons using their data. You will need to register for a free account to access the data. Besides this, there are a number of agencies who have made data available on their websites but are not included in the open data portal. California's Department of Education provides a lot of data on their website, and there's a process where you can actually go in and request additional data if you're a researcher. There can be a charge, and their website provides instructions for making this request. The California EPA also has a number of data resources on their site as well. Great. Thanks, Kathy. I know this has been a whirlwind tour of the California issues and sources, so I felt obliged to point out one more. And this includes work that we're doing to preserve California government information. This is a project that the University of California, Stanford University, the California State Library, and the California State Archives are doing to archive and pursue preserve California government information. So please take a look at it and even use it to track down California government information. It's most robust and complete starting in 2015, but there are captured sites and data back to 2000, so keep that in mind. We're going to wrap up now, and I know this has been a whirlwind of sources and information. We hope it's been informative to you and given you a good sense of the rich sources of information on California.gov and other websites. Jesse, if you could show the next slide real quick. The next slide also lists some other sources and they'll give some policy and legislative information. So we encourage you to take a look at that. And with that in mind, we'd like to open it up for questions. If anyone has questions, they'd like that. I saw a cost of living slide there. Originally we were going to put something in here about housing and the cost of living, but there was just so much to say at the wrap-up, just a sort of amount of time, and it's a very complex subject in the state. It generates a lot of discussion on both sides. Can we see the slide? Sure. So this is from HUD, and this is showing the income, meeting income limits for qualified for HUD housing in the city and county of San Francisco. This got a lot of news a few, several months ago, where it was announced that a family of four can qualify for HUD housing if they are making $105,000 a year. Well, thank you so much. This was wonderful. Oh, yes. I'm going to ask you about the posture on climate change. Okay. Let's take a picture that you have. The ones that I have, I actually got from the Climate Change Portal at the California website. Well, thank you so much. This was really wonderful. It was very interesting and informative, and if everybody could join me in thanking you. If you have any questions for Lucia or Jesse, I'm sure we wouldn't be more than happy, either now or in the future when you have a student who is asking you about things in California. Here are some experts you can turn to. Thank you very much, and do try to join us on April 18th.


नग्ध सीक्रटे उंफ्रे लगाईप्ते ज़ाएं ग़ाच्ता ज़ी लोग आपतो हूँ आप आप़ शदखं दीए उस्ताणी लगाच्तज़ी लोग अदद तो रंबोद न चाटकूत दीए उरे पवर्डे उदलनेंव, बेज्याब Services N cattle have aikum al-FORThis women, यह plausible, उरो इसरी सब ँली क्षे या पनाष्ब ,emptions stopped ,चोलन astronomers did. विजटीкая क्षे अगिराकग हenger , अव� books fall, विछ मंदवी चा समगलीं कर दिसिए। ,। These ladies are likeов girls. इसन've मानडे के दाल द्ढ़़hini, भा Tam характер, these ladies were the women of rolling in the cart with the help of her heart they wanted to smoke this out into the sultr they wanted to kill people and thrown people in, lifted up few things some people were♥ there are 1 & 1 late this item comes from one of the network whoique adjacent to the spot so people couldn't significantly survive my families who used to kill this zentail believers 175  HARROW ÉNO ancestry 260  Hoch to  enhan dh appoint a praraj releasing cando ay


Welcome folks, this is Tom O'Brien of TFNN. We have five days a week, we have seven hours a day, we go 24 hours a day on the internet at TFNN.com. Always remember folks, whatever you think about, you bring about whatever you focus on grows, hope everyone's having a great day, safe day. It's a TGIF folks, it's making a great weekend. Always do your best, take action on your ideas. Doing your best to meet, take action on your ideas. You have many great ideas in your head, but without action upon that idea, there'll be no manifestation, no results, and no reward. Market-wise, let's take a look at it out here. We have the Dow Industries trading up 780, NASDAQ's up 276, S&P's are up 85. That's a gain inside the NASDAQ of 2.5%, 2.3% in the S&P, and 2.4% in the Dow Industries. Gold, gold contract down $19, 20 cents, trading at $16.46. You get silver down 31 cents, $19, 18 cents an ounce, light sweet crude, off of Buck 11, $87.97 a barrel, notes and bonds. You get the 10-year note trading down 1.4 ticks at 1.2107. The 30-year is trading down a full 1.4 ticks. Sorry, no, the 10-year is down 22.6, 1.1031. 30-year off a full point, plus 4 ticks at 1.2107. The 10-year right now is at 4.010, $1, $149 ticks, trading at 1.10734. The euro's at 99, the yen is out here at 1.4744. The British pound is at 116 to 1 US dollar. Our phone number's<PHONE_NUMBER>. Give us a call, folks. I know what's going on in your world. In the world of the S&Ps, let's take a look at them. What do you have? Well, the bottom line, we're gonna go to these big dogs first because what we had is that, you know, well, no, let's go to the S&P first. Okay, so take a look at the S&P. Bottom line inside the S&P, well, here, no. This is where I'm going first. I'm going, remember when we were getting off the air yesterday, the bottom line, you had the pullback, the pullback was much lighter volume, and you can see how this is shaking out. This was the NYSE, so we did about the same. One billion versus one billion, okay? On the pullback, now watch this, though. Watch the NASDAQ. The NASDAQ, you had 5.2 and you're pulling back with 4.7. Now, when that happens, folks, what I've found is this, is that this is about as twisted as you can get, meaning that if you believe in price and volume, you know, and I do, I've been doing it so long, like yesterday when he's pulling back with light volume and then after the close, man, after the close, folks, it was a disaster. You know, Amazon, I think that, here, well, let me see, I've got to show you, because we were down like 350 points inside the NQ at one point. Yeah, beautiful, here it is, okay. So, we were down, okay, at 10,921, okay? So, the bottom line is that you're up 650 points from there, right? So, you can imagine, it's like, okay, man, I didn't get this one, man, this is really screwed up. And, but the bottom line is that I knew that volume, I'm saying to myself, I've seen it, I've seen this happen before and it's the consistency, you know, that you kind of have to go through this with the consistency that, okay, man, this thing wants to go and sure enough this morning, okay, if you were inside in front of a machine this morning, you know, you could kind of see it. And what also happens is this, inside the NDX100, I believe I brought this up yesterday, inside the NDX, this Gilead has always been a high weight structure that you never think about inside the NDX. This is what's pushing the NDX out here in a monster way, also, I mean, it's helping it, okay? But it was helping it right off the get go. It opened at 74, 36 and, you know, the bottom line, you're at 78, 78. Intel, Intel also, bottom line, you know, but everyone knows about Intel. There's plenty of people that don't know about Gilead, but Gilead, I've been trading Gilead for a long period of time. If Gilead goes down, that can drag the industry down with it. Bottom line, we can see what happened. You've twisted right around it in a monster way. Now, that being said and done, now kind of let's go through it. Because what you have here, now you can see, I mean, that's an ABC up now. You know, we'll see how that's, you're blowing away a B point, you have volume behind the move all the above. You got, I think we own this one right now. I think there's gonna be another ABC up too. Yeah, so, no, it's not, it's not. Because it's, well, it already is an ABC up, but this is, you know, you get general mills taking out the swing today.  But bottom line, higher prices they want. Okay, so now let's go through these indices. We take a look at the spy first. And what we have with the spy is that now you are getting a big contraction of volume, okay? You're going into ice. Ice is set up at 390, folks. We're at 389, 24. So this is where basically the pedal, you know, hits the metal. And I suspect that's exactly what we're gonna get. Now, you can see there's two different things that are happening here. Is that you're not only into ice, but you're also at a 50% retracement of the move. So you gotta be careful here, man. This thing is not just gonna go right to the moon. We're gonna take a look at the NVX100, the three cues. I think they're gonna go a little bit higher, believe it or not. Now, what you have with the three cues is that because we actually went lower and higher, it's like, okay, you're gonna lower, lower the volume. It's not bad. Now the cues at a 50% or at ice is 292. I don't see it getting to that point. I see it's gonna get challenged at the last high, which is probably the 284. So if we take a look at that and say, okay, what's that whole run of 284? Well, guess what? That's a 0.382. Now, that totally makes sense, folks, okay? The reason being is that when you take a look at the mic, oh, here. Now let's go to the dow. Because the dow was in the ABC up. I think the dow finished the ABC up. Look at this man. Unreal, actually. Let me do the diamonds. So we take a look at the diamonds. The diamonds are coming into, this probably just 786, man. You gotta love expansion contraction theories. Look at this, man, 786. 786, rather. 786 is at 32, 328. 32, I can't read that right there. It's about three, three. It's just a little bit higher than we are. So I suspect that we start coming in next week. The bottom line is that you more than likely are gonna start building some cause. Cause the sideways move, that's actually telling me that more than likely what we're gonna see is that the doll is gonna probably start rising up, going into the Fed. Trading market, it's a big trade market. Stay right there, folks, come right back.


A product of Oklahoma State University, Tony Banfield was a fearsome defensive back for the original 1960 Houston Oilers franchise. He helped the Oilers win back-to-back AFL championships while being named to the All-AFL team twice and named a three-time AFL All-Star. His most memorable play came when he returned a blocked punt 58 yards for a touchdown in the Oilers victory over the Oakland Raiders.


Duluth Denfeld on the road, taking on Grand Rapids. After the Thunderhawks would fumble on their first possession, the first play for Denfeld, Dominic Klaus takes the hand off and does the rest, turns the corner, takes the hit, but is in. The two-point try is good, it's eight to nothing. In the second now, GR facing a third down, the quick pitch to Wade Browse, hits the juke button, makes his way for the first down, spinning along there. Thunderhawks driving still, but Brendan Morlin wants it all, but Caleb Lustig makes the pick in the end zone. Denfeld would go on to win 28-22. If you enjoyed this segment of Lakeland News, please consider making a tax-deductible contribution to Lakeland PBS.


Hey, what's going on? It's Steve at Surfstations Store. Just wanted to do a quick board review on Surfstations Tarantula surfboard. Overall, this is a great board for some of the smaller to medium-sized waves. Personally, I really like this board just the way that it's got a wider nose. You have a little bit more surface area just to get you into the waves a little bit easier. You know, when you catch the waves, it's a little bit easier to pop to your feet. What's also great is it's got a narrow tail. So, you know, while you get into the wave, you're not going to really risk or sacrifice the maneuverability of the board. This is very similar to the Takiyama Scorpion. You know, again, another board that's very popular right now. It's just recently coming up, you know, in our shop. And, you know, the Tarantula is just something really good, especially for some of those small summer days. These boards come anywhere from a 3 to 5 inch setup. Occasionally, some of our boards, you can have the center fin set up so you can ride it as a single fin. We have these boards as small as 5 foot. This is a 5-0 board and they go up to 8 feet. So, you kind of have a range of boards. All these boards are glassed and polished with a different color. We've got some blue. We've got green. We've got red, you know, just all around just a great board. We've got a bunch of them in at the shop and we will consistently be getting more. So, if you just stop by the shop or visit us online at surfstationstore.com and pick up a surf station Tarantula.


Hi everyone. Thank you so much for coming. My name is Philip Mendoza-Vieta. You can find me on various social media at PhilMV with 2Ls, many other places online as well as Twitter. I am one of the co-founders of RubySec.com which is the, we host the Ruby Security Advisory Database. And so if there's anyone in the audience who maintains gems, I would love to talk to you afterwards about how you handle security disclosures. But for my day job I run a startup called App Canary.  And basically we spend a lot of time thinking about, are you running vulnerable software? So this talk is ultimately about a series of technical decisions we made and implemented while building the service at Power's App Canary. And as a result I feel that it's best in order to best understand our thinking process. We should start a story today at the beginning of our incredible journey as it were. So back in 2012 I began a consultancy with a friend of mine, Max. And we specialized in doing penetration tests and security code audits and doing MPPs and business automation and advising teams on how to improve their software development process. And one benefit of being a consultant is that you have a lot of control of your schedule. So by the time November 2014 rolled around I had just spent two months working 12-hour days on the Toronto mayoral elections. And my co-founder Max had just had magical summer at the recurse center. And as a consequence I was really burnt out and he was really bored. And we were really looking to do something more challenging. And so we'd happened upon this market opportunity that could really use our skills. And we said, okay, let's build a product. We'd had some experience with this problem domain because we'd built this free service called Gem Canary a few years earlier. But in a nutshell an advisory has many vulnerabilities. A vulnerability has many packages. A package has many versions. And we need to keep track of all of this in order to tell you if you are running a version that you shouldn't. And so we looked around and Max turns to me and says, hey, let's use this thing called Datomic. So if you've never heard about Datomic, Datomic is really cool. Datomic is this key value stored graph database where instead of SQL you write Datalog, which is kind of pro-law kind of language. And on top of all this you get a free point in time database, which means that you can roll back to any previous state of your data. It's basically nothing ever gets deleted. It's kind of really cool. And so the way we're kind of thinking about what are struggles from the kind of free service that we built, we're like, this would be really handy. Let's try using this. Unfortunately, all the client libraries for it kind of sucked. But it worked really great with closures. So let's use closure. Closure is really cool. For those of you who don't know, closures is functional programming language that features immutable data structures that give you all sorts of asynchronous primitives for free. And it runs on the JVM, which is supposed to be web scale. I don't know. And I mean, shouldn't we all learn a Lisp really? Is not what you're supposed to do. Isn't Lisp supposed to be this profound enlightening experience that will forever change how you program for the rest of your life, right? I mean, for me personally, at this stage I've been writing Ruby for five years. Most of my career, you know, a dozen of apps. And to be real with you, these are all compelling reasons. But one thing that kind of dominated my thinking was this fear, right? Am I stagnating, right? Because when I jumped into Ruby, it was like synonymous with bleeding edge, like web tech. And now not so much anymore. Am I still going to be able to get a job, right? What actually happened is to programmers after the age of 35, right? Did it vanish or something? And I really didn't want to spend the rest of my life writing JavaScript, right? So the idea that there's this other technology set that I could invest in and kind of broaden my skills is really appealing.  We're going to run out of money in six months anyways. Let's do it. So we went out and we built it in closure. It was really great. So for people in the audience who might know closure already, I know using the wrong words because people in the audience I'm assuming are more familiar with Ruby. So just please stay with me. So closure is a bit familiar, right? Both closure in Ruby are truthy, where things are nil or false or good enough. They both really spend all their time dealing with hashes of symbols. And they both have all these fun metaprogramming constructs. So why is closure cool, right? Let's start with the big one, functional programming. In closure, functions are the basic semantic building blocks, right? They're encouraged and captured with the smallest units that are practical. So in this little function here, we're filtering out all the even integers by applying the even function to this array. And if you squint, you've seen this before, right? This is not, like, unreasonable to you. And there's this old joke that Ruby is an acceptable list, right? There's this blog post from like 2005 that makes this argument. But if you kind of think about it, even is an artifact, a fixnum, select is defined in innumerable. But if we can contrast this with the closure code, filter is the one that worries about what kind of data structures it takes, right? It's not, it's, the data structure itself does not know the hash or the map doesn't really concern themselves. And even is just any function, right? This is really cool, right? It's not a property of the numbers or the things inside of the array. Like, I can do whatever I want in there, right? And so, being able to combine bits of behavior like this can be really powerful. Another thing that's really cool about this is when everything's a function, nine times out of ten, you can just select the whole thing, cut it out, create a new function, put it in, and rehab call what the thing was originally, and then you're free to just change this new structure. You don't have to really worry about it, right? Everything gets passed in, don't think about it. And finally, immutability is really, really interesting. Historically, it was an expensive feature to have until in 2002, there's this breakthrough and a bunch of cool papers got written, and so it became like a reasonable thing to put on your computer. And in the most trivial sense, immutable means something that can't change, right? And in practice, it means that for every insert, update, or deletion, you end up with this brand new structure. And this is important because if you think about it, when you're mutating state, that gives you a lot of complexity that results from it. And if you can just remove having to worry about things changing when you're not looking, huge amounts of bugs are just gone. And the best way to illustrate this is with a little bit of Ruby code. So suppose that we have this list, just a bunch of strings up in there, and we assign this list to another variable, and then we have, we apply this append method to it, right? Appending, whatever that means, d to the first list. What happens with list 2? In Ruby, this question requires a lot of thinking, right? Or strings immutable, right? Or arrays immutable. Does Ruby pass by reference or by value? Does append, and most importantly, does that append method mutate or copy? Because, I mean, you could have something with the same semantic, you know, the same semantic purpose, does the same thing, but in practice, very different outcomes. So this method will insert something at the very end of the array, right? And this one will create a new array, right? You don't know that from the top. And as you use them in practice, they have very different implications. And the thing about Ruby is that you can't get away from this, right? Freezing won't save you. I can freeze this array, and I can still modify the contents of it, right? So I can't add things to the array, so pedantically that's true, but for my purposes, like, some other thing could mutate my state. I can't dupe it, because I can dupe something, and I can still modify the contents of the thing, and it still points back, because in Ruby I've cloned the array, but it's still pointing back to the original objects, which in this case are immutable strings, right? Literally the only way to guarantee that your objects aren't being messed with is to do some atrocity like this, right? Now, I have code that does this because I had to, because I have a thing deep in the bowels of active record that had to do something, and I was like, why is my thing disappearing, and it turns out it consumes the objects literally? So this code I used, right? And I think we can all agree this is kind of ridiculous, right? But it's Ruby, so there's nothing you can do about it. You have no control over whether something can be mutated or not, which is really unfortunate, because once you have immutability, I found, in my experience going through this, the flow of state through your app becomes obvious and predictable, and there's a kind of a way to illustrate this. So this next page is a function from our old app, and it's just a route that takes in the user and the database, and there's some parameters that we've passed in, and it processes the stuff and tries to parse it out, right? Because we do a lot of text. You send us text, we figure out what packages you have, stuff like that. So the specifics don't really matter, and that what's cool about this is that I know from the level of indentation that the stuff at the furthest level of indentation literally can't modify things outside of this lexical scope, because they're just immutable. I can maybe redefine the meaning of a variable. I mean, I can't unless it's, if it's not the same scope, right? If it's in the same scope, I can change the meaning of that variable, but stuff that's outside of it, literally, I can't touch it, because it's all immutable. And that's really cool, right? There's this kind of confidence you can get out of it. And so this is, I don't have all the time of the world, but I'm going to give you a quick illustration of why the atomic's kind of cool. So your boss comes up to you one day, and she says, hey, so I have this report, it's really cool, but can you just do this if last year's data? And in traditional databases, depending on how you, it just depends entirely on how you design your system, right? You either specifically designed it so you could do this, right? You took snapshots of the data, or your report collects the right things, or whatever. This request can be the simple, this rather simple request, can actually be a nightmare to execute on. And what's really cool about the atomic is that I can have a function that, given the database, will give you whatever value you're interested in. And then I can grab that database, and I can say, oh, this is cool, but I want exactly what I had a year ago. And then I just re-run the same report, and it just works, right? That's cool, right? And I'm not saying that datomic as a key value graph database is something you want to do reporting on, but in principle this is the kind of stuff you can get away with. All right, cool. We really want to play this new technology. It's cool, it's in the right place, we got a use for it. But I've been doing all this time, I've spent years building websites. I have zero interest in figuring out how to do user authentication, and cookies, management, and whatever in a new language. I already know how to do that. Let's just do the hard parts and closure. And so we ended up with something like this. We have this API that speaks to the atomic, and we have this Rails quote front-end that does boring things like talk to Stripe and deal with users and stuff. Cool, great. In the meantime we start working on this full-time in February 2015. In May, much to our shock, we got into Y Combinator, which meant that money was slightly less of a problem. In July we released the production, and then we moved back to Toronto in October, and we just slaved away at this adding more features. And so we ended up with paying customers real demands and real problems, because it's taking weeks to ship and debug simple features, even though we're holed up in our office working our butts off. And in retrospect we had three large broad issues, right? Number one is that we just made a bad architectural assumption. We underestimated the domain complexity, because it turns out that what is a package really is a deeper question than what we'd consider at first, because everyone has a slightly different definition. But it just meant that we had this messy data model that was hard to modify. Number two, we had these separate deployments that added all this overhead. And it turns out there's this high fixed cost to orchestrate all these different features at once. And I have more to say about this, we'll kind of come back to this a bit later. But on top of all this, I found myself really struggling with the environment that we're in. It kind of felt that we had this death by a thousand paper cuts. All these different small issues that in and of themselves are not a deal breaker, but they added up. So first and for all, it's not clear how to structure large apps. It's like if I'm trying to model a chess game that works pretty well, but then if I have users that come in and they have these preferences that have to be stored and how do I put this and this, there isn't a lot of literature in how to structure these things. Rails kind of holds you by the hand, and you kind of get used to that. Closure can be really fun to write. A lot of the time you feel really clever writing it. You're like, yeah, yeah, this is computer science right here. But as a consequence, it can be really hard to read. There's this like in between stage where you're like, I understand how this syntax works. I know what most of these functions mean. I have to really think hard what all these things are doing unpacking themselves. It can also be too expressive. You can pack in too much meaning and too little of a bit. Closure has all these deep subtleties. When I was writing this, it came to the conclusion that a good analogy would be like C++. You can pick up C the subset of C++ really quickly that you can be productive in it. But in order to read anyone's code, you have this infinity of other stuff that you need to understand in order to apply to it. If you have templates, you have boosts to what? It's an analogy. And in closure land, you have reducers, transducers, atoms, agents, protocols, reader macros.  But it makes it really hard to kind of like feel confident what the hell you're doing. Another problem is that when everything's an anonymous function, your stack traces are useless. And some of you might have direct experience with this dealing with JavaScript where you have some complicated nest of JavaScript and it goes at barfs on your lap and you're like, what happened? And they're like, well, somewhere in here, there was a problem. And when you're debugging something on production, that's not a good feeling.  I need to figure this out. So compounding this, there's like comically terse documentation. It's like in order to append, you take a list of f's that have x. I didn't bring up a good example, but it's tough to parse out sometimes just the gotchas that are just hidden, et cetera. There isn't really a debugger in the system. There's the REPL, which Lisp is famous for. But I can't really attach something and say, aha, here's the data. Show me what's happening. And finally, the Java virtual machine is just, I mean, our app took 30 seconds to boot, which means that deep integration is required in order for you to not tear your hair out, which in closure land means that I sure hope you love emacs, because if you don't, I mean, you can make it work with Java land stuff, but then you're dealing with Java land tools, which is maybe it's just not me. Our deployments, the deployment story in Java land is kind of complicated, so you have to grab all your dependencies and shove them into one object and then push them onto your server, which meant hundreds of megs somehow, which meant that I can't fix something from a coffee shop, which is like, from Ruby land is like, oh no. And our app took gigabytes of RAM, it literally needed gigabytes in order to boot, and I still don't comprehend why. And finally, just like miscellaneous Java land stuff, fine. This is all just another way of saying that I'm really fluent in Ruby in a way that I'm not in all this other stuff, right? It's not necessarily their fault for any of this. Like six months of closure or 12 months of closure does not compare to five or six years of Ruby. I'd gone to a certain stage in Ruby where like, while you see the difference between 2.3.11 and 3.2 is that in Rails lands, you don't have that same depth of knowledge. But regardless, I spend a lot of time feeling frustrated because I'm finding the tool set.  And so it wasn't until I found this comment on Hacker News that described the ecosystem as user hostile. I was like, oh, it's not me. Other people feel this way. And everything kind of clicked. And kind of in a nutshell, if I had to summarize it, it seems like developer happiness is not a virtue in that community. And the best example off the top of my head is like, I went to this local user group and I'm like, hey guys, I need a debugger. I do debugger-driven development. That's how I live. And they're like, well, you have a console. I should be good enough. What do you need a debugger for? You can just type in all of your state onto the console and deal with it. So I had this strange feeling of culture shock. So time passes. It's now May of this year. And we knew we had to refactor our application. We needed to clean some things out, because if you're a hold up in some Aspid of Suburbia, desperately working, trying to push this birth this app out, you're not going to make good long-term architectural decisions. We needed to do some spring cleaning. And I happened to be visiting a friend in California and I'm like, well, you know, I just spend two weeks cleaning things up. It'll be great. You know, whatever.  And I'm like, huh. I mean, it's not an original idea. I'd thought about it before. But after that stage is kind of this watershed moment after which I couldn't really ignore that option anymore. And the problem, of course, is that rewrites are risky. When you engage in a rewrite, you have a hell of a lot of effort that if everything goes well, no one will ever notice. That is a success condition. That is the best case scenario is that your users log in and they go, oh yeah, this is exactly the thing I had yesterday. But that said, I mean, we're spending all this time fighting the ecosystem. We're going to be migrating this platform, you know, really, really well. Frankly, we were not using Atomic properly. Flat out. Just like we're not using it. You shouldn't just be shopping everything in there. You should have specific things you're trying to do. And most importantly, we'd be reducing the number of moving parts that we had. Because this is what shipping features look like. We would add features and tests to the quote API. We would submit a short code review, aka have the other person review it. We'd deploy it to staging. And the web, get it to talk to the API, the adjacent, test that, code review that, and then manage the deploy both to production, both apps to production simultaneously, right? And so it turns out that if something like this with two people, this is a bad idea, right? Like, don't do that. Because we actually unintentionally built a distributed system and microservices incur large fixed costs that are really difficult for small teams to pay.  Because your service boundaries should roughly mimic your team boundaries. If you can't change the color of a button without having three meetings about it, like, microservice is fine. That is not the part of your overhead. You can orchestrate that. But for a two person startup, it was just like, we're spending all this time. Whether we're fighting closure or personally fighting closure, my business partner loves it. Or you're finding architecture that we actually set ourselves up with. The end result is that we're spending a lot of time working on things that don't really matter. And so Dave McKinley, who is this early guide at Etsy and does a bunch of other stuff, has this somewhat famous talk where he called Choose Boring Technology. Which I think the key takeaway from that, the one that really sat with me, was that you can work on about three hard things at once. And you should make sure that they're the things that matter to your business. We built ourselves an object relational mapper for Datomic. No one cares. No one's going to send me emails like, oh man, I pay you X dollars per month, but that GitHub library release is dope. Not a thing. So in the end, the way we thought about it, we're reducing our exposure to risk. Which is what you want. We're already doing something really risky with our time, money, and careers. You don't want to do things that don't pan out. As a small operation, we had the luxury of stalling a little bit. If you're like Netscape in 1997, whenever they did their big rewrite, they had millions of customers and people breathing down their neck. A bit different. And we set a deadline sort of eventually. And if anyone tries to do something about a deadline, they're not serious about it. So that's just kind of a quick pro tip in there. Cool. So we set about it. We did it over the summer. On October 11th of this year, which is not that long ago, we had 8,300 lines of closure and about 3,000 lines of Ruby. And on the following day, we had 1,700 lines of Ruby. We still have 1,500 lines of Go, but that's another story. It took four months to rewrite the thing top to bottom, which is good compared to the year and a half it took us the first time when we didn't know what we were doing. But it's just not a good way to spend your summer working weekends because it's really deeply demoralizing. Because you're slaving away at something that you can't ship. And meanwhile an email come in and be like, so your product's neat, but it would be great if you had this. And you're like, yeah, soon. Soon I'll have everything. And so it's just a really immense relief to ship, right? So result, point-in-time databases are not that hard to design in Postgres. I really highly recommend doing some reading on data warehousing or domain-driven design. I have like 80% of what I need, just in a couple triggers, which is cool. Really recommend that. Despite going back to Loll Ruby and away from web scaleness, our app is actually faster. It's somewhere between 50% to 100% faster. But we wrote the data model, so duh. And if you'll indulge me in a brief tangent, there's this whole subgenre of technical blog posts that go like this. So we rewrote our app from boring technology to amazing new shiny technology, and things are 10 times faster. And so if you took all the lessons you learned the first time, you rewrite the thing and you didn't squeeze more performance out of it, like what were you doing? Like what were you trying to accomplish? Like what's going on? But my Ruby point, kind of the takeaway from the talk into you is that when I went back into Ruby land, I found that my Ruby's different now. All that time I spent in closure kind of had really crystallized some thoughts I'd been having.  I don't know about that. And then there's that concerns that came out, but like concerns are not really a good way, so you just have the same problem, they're just spread across 50 different files for some reason. So I still have this like 500 method user.rb, but through all these different files, that's not great. And so I've been having these different ideas, and people have different ideas of how service objects, but then they try to make it too functional, so you have to call dot call and everything. Anyways, so key takeaways from my experience in closure land that kind of helped existing thoughts that I'd had. One is that I try to be as immutable as Ruby will let me. Ruby won't help you, but you can be disciplined in what you do. One example of this is something people have been calling a value object. And so it's really handy to pepper your code with them. And these are objects whose sole purpose is to represent a bit of state, where you pass it in when you initialize it. And then afterwards you're just not allowed to modify it. You pass it in once, and any time you try to update it, it just says, nope, can't do it. So I don't use this gem, but it's a good example of what's going on. So T.Crayford had a little immutable value object gem that you can just install. And when you do it, basically the way it works is that you thank you, initialize it, and then if you try to change it later, it's like, nope, not doing it. Another thing that really changed in me personally post closure land is that I've become much more aware of how state flows through my application. I'd say more that I'm paranoid about it. So this is kind of hard to articulate and a good key takeaway. But I'm going to give you a bit of an example of a pattern that I've been using lately. And something I've been calling for lack of a better word, a quote, manager object. So managers for me are distinct from controllers, which I see as handling input.  The model strictly only deals with persistence. Either it speaks to the database or queries it or saves it, that's it. And then the managers take input from the user. They look inside the database via the models and they kind of mingle it together. So I'm not saying this is the one true way of doing things, nor necessarily that I'm going to stick with this, but this is how a lot of my code lately has been looking like. So here's an example. Take the package manager. So pretty straightforward, very simple. We have an adder reader at the top, which means that the one and only time that they ever get modified is through the constructor. And then you pass an all state you need for things within this class. And then when you add instance methods you just have to be really careful to never modify your inputs and never set instance variables. So a lot of my code ends up looking like this, where I have something that is responsible for dealing a package manager will be initialized for once per platform. And then anytime I want to find packages or change them, or anything that mixes a lot of different business logic together, it will be like this. I can pass in an input, but I will never change it. I never set any more state. If I set state that I have to pass along, I create a value object and things operate on that. Because again in Ruby, anything can mutate, but none of your code has to. So if you kind of walk away if you have some key takeaways, one is that despite my moaning and complaining, closure is worth learning seriously. It's maybe not like the most transcendental thing you'll do with your time, but it was neat. I learned a lot from it. I would happily work on someone else's project for it. And while we've personally moved away in our business from relying on it, I'm actually kind of really excited for closure scripts. Once they get into a state where you can just drop it into some pre-processor and dump it out, I can have a whole talk on the ways that we're avoiding JavaScript from our application, but I'm not going to share my prejudices with you. And that's just mean and pointless. But this is all just to say that when the day comes and people are like, these things need to be nicer, they're like, all right, well there's a lot of cool stuff that's coming out of this. If you ever thought with if you ever screwed around with React, for instance, a closure script will just work beautifully with that. Another key takeaway, avoid building distributed systems for as long as you can. We now have this beautiful monolith where if I update something in one end, I don't have to worry about how it gets to the other. Eventually, there's only so long you can do this for. Eventually, you will have to have multiple things that talk to each other, and then we can talk about the cap theorem at that stage and whatever. But it turns out you can get really far without having to worry about it, because I don't know about you, but I can configure really beefy machines these days. So if you just have this once, you can get away with a lot of traffic before you really have to think about it too much. And this is kind of a corollary of avoid working on problems that don't matter. Does it really matter that you have these containers that you can shove in and out that goes through it if you don't really have a thousand machines that you have to put it on? Exhaust the tools that you know before reaching for a new one is kind of like a more pleasant way of saying, I don't think things are boring, it's just something you know really well. And so reach to the end of the things that you know really well before you... If you're pressed for time, if you're just doing this for a hobby on a Saturday morning, knock yourself out. But if time's clicking down, you've got options to do. And finally, I think most importantly, kind of something that I've been thinking a lot about in this experience is that code should make you happy. And it was kind of like a rude awakening after spending effectively my whole career in Ruby that the notion that programming should be fun and painless is not a universal value. This is bewildering to me. But I mean the less charitable interpretation some people are just happy to be clever, to feel clever in their programming and not necessarily happy. So I would say, take it for what you will, I think programming shouldn't be fun and painless. And this is all just to say to cherish what we have here in Rubyland and make sure you bring it, kicking and screaming through your new communities. So that about wraps it up. This is the story roughly of how we built this service that will happily notify you if you're ever running vulnerable software on your stuff. And that's about it. Thank you very much.


Hey, this is Brett, and this 2021 Dodge Challenger RT Scat Pack Widebody is stock number 12902Z. We are here at Summit Automotive in Fond du Lac, Wisconsin, your new and used sports car and Dodge Challenger headquarters. This 2021 Dodge Challenger RT Scat Pack Widebody comes with the 6.4 liter V8 Hemi engine. It puts out 485 horsepower. This car has been fully-safetyed and inspected by our service shop per the state of Wisconsin inspection process. It has a fresh oil and filter change. All the fluids have been checked and topped off, and this car is 100% ready to go. We're going to go all the way around in this video. Inside in the trunk, start it up, take a look under the hood, pitch black, clear coat is the color. We shoot all of our videos in 4K, so if you have HD capabilities on your computer, tablet, smartphone, or television, I highly recommend turning them on right now because it is your best way to check out the quality, condition, options, and cleanliness of the vehicle before seeing it in person so that you can make a smart purchasing decision before seeing the car in person. If you like the video and how we do things here at Summit Automotive in the lower right-hand part of the screen is a subscribe button to our YouTube channel. Click that, and then click the bell notification so you'll get updates every time we do these videos of our new and used inventory, which is each and every day. This one comes with the Granite Crystal painted alloy rims, and it has Pirelli P0 tires. These are 305 35 ZR20s on here, and they have just about all the tread left on them. This car has a little bit wider tires. You also get the SRT Rembo brakes on here, but you get the little bit wider tires with that wide body package, which also gives you these fender flares. Fender flares are in nice shape in the front here. Front bumper and lower valance are in excellent condition. It does have the HID headlamps, and we're going to turn on all those lights at the end of the video, so stay tuned for that. It'll be a pretty quick video. This one has my favorite hood on these challengers. You get the heat extraction on the sides with the cove induction in the middle. I think it's such a good looking hood. Really tough looking, but I didn't see any dents or dings on that hood, and the passenger side front fender is in excellent condition as well. You saw on the front bumper that it's never been drilled into, so that's a really nice plus on this car as well. Rear side rim, no scuffs, no scrapes, and as you go down this side of the car, take note of how clean that body is, how reflective, and mirror like that paint is. We take these HD videos so if you are far away, or even if you're close by, and you just cannot make the trip down, but you're still interested in purchasing the vehicle, you can see the car, hear the car, and of confidence in the vehicle that you're looking at before you even get here. So when you do get here, there's absolutely no surprises, and you can make a smart and informed buying decision from wherever you're at. And if this video helps you make that decision, let your salesman know that you saw the video, that it was helpful, and that Brett sent you. Back rim is in excellent shape as well, and the back tires have just as much tried as the front tires. These are also 305 35 ZR20s in the back. So same tires in the front as in the back. Coming around to the back of the vehicle, rear bumper is in great shape. You do get the chrome tipped dual rear exhaust, the backup parking sensors, you get the LED tail lamps, deck lid spoiler, and the backup camera, and the spoiler is not sure if it's a Hellcat spoiler, or if it's a special spoiler, but it's bigger than the normal ones that come on these cars. So really good looking spoiler. Trunk area is very clean. This one comes with the tire inflator kit, and then the battery is in the back as well. Trunk shuts nice and solidly, and as you go down the driver's side, just as clean as that passenger side, you can see just how reflective and nice that paint is. I didn't see any dents, I didn't see any dings. Just for full disclosure, this back rim, no scuffs or scrapes on that. Down the rest of the side of the vehicle, doors look really good. Does have the blind spot monitoring, heated mirrors, the enter and go system. So when you have the key fob in your pocket, it'll automatically unlock. Inside the RT Scat Pack package gives you the red suede, or Alcantara suede. The black leather, you get the rumble bee stitched into the backrest. Side curtain airbags, seats are in excellent shape. Power driver seat lumbar, you get the black floor mats with the red outline, the bright pedals, auto headlamps, power telescopic, and tilt steering wheel. You also get the red stitching on the leather wrap dash, Alpine premium sound system, memory driver seat, power windows, power locks, and powered mirrors. The doors are also red leather bolsters, black leather armrests, and red trimmed. As long as we're standing here, we'll take a look at the back seats. Very clean back here, latch child safety system, and those seats do fold down for extra storage. You also have the floor mats back here with the red outlines. We'll hop inside, check out the miles, radio, and everything that this car has to offer on the interior. You get the 392 animation at the beginning, has the digital speedometer, miles per gallon, then this car only has 2,008 miles on it. So very low miles, very nice condition, 7 inch LCD display, comes with the heated leather wrap steering wheel, cruise controls on the right, Bluetooth and information center controls on the left, and that steering wheel is flat bottomed. Comes with the 8.4 4C radio, you get AM, FM, and Sirius XM radio capabilities, you have your heated and cooled seat buttons, you also have your heated steering wheel controls right there, you can do your climate controls here as well, you do get dual climate controls, you have all your different apps here, including projection manager where you can project yourself onto the screen, we actually did a demo on Android Auto, if you want to check that out on a 4C, it's in the upper right hand part of the screen on here, and why that's nice is because this one doesn't have the factory navigation system, but you can project yourself on with Waze or Google Maps to the screen, and then it's like you have Nav right on the screen, so really a cool system right there, this one also has your performance pages, where you can do like quarter mile times, top speed, all that stuff.  Anyways, this is also where your backup camera shows up, down here you have your launch mode, your different drive modes, so you can do that up here as well, you have track, sport, custom, and auto, line lock, all that stuff, so a lot of stuff you can do with this radio and all the pages that come with it, dual climate controls, your six-speed manual transmission, you get your keyless entry right here, passenger side format and seat are absolutely perfect, this car has never been smoked in, it smells absolutely brand new, and the headliner is in excellent shape, you also get your power sunroof, map lights, and home link buttons for your garage door security systems and lane systems, sunroof controls, SOS, and assist buttons in that rear view mirror. We will start it up and take a look under the hood, we will also check out all those lights in the front, they are very impressive, to say the least. Car sounds really good as you'd expect for, I love those LED tail lamps, we'll check out under the hood, I would personally like to thank you for checking out the video today, and hopefully from this HD video you will have gotten a really good idea of the overall quality and condition of this car inside and out, there are those HID headlamps, LED running lights, and then these are actually dummies, they're for air intake, but that one's capped off, but you can see it, you get the Dodge logos or the Rambai inside, which light up, it's really cool, but those headlights are really bright, and under the hood, as promised we have the 6.4 liter V8 Hemi engine, 485 horsepower, engine bay is very clean, runs very smooth, once again this car has been fully safe and inspected by our service shop, has a fresh oil and filter change, all the fluids have been checked and topped off, shocks are doing a nice job holding that hood up, and this car is 100% ready to go, there is your emissions sticker, and I would highly recommend this car from a quality and condition and looks, and just a really neat ride standpoint, and to see more pictures of this car, or one over other, 450 new and used cars, trucks, SUVs, minivans, Wranglers, sports cars, challengers, chargers, Mustangs, Corvettes, Camaros, you name it, we got to go to that website right there, summitauto.com, full pictures and descriptions of every single vehicle from two locations, all at summitauto.com, and if you'd like to check out more HD videos you can go to youtube.com slash summitauto, remember to like, subscribe, and share on this video and all the videos that you see there, click the bell notifications, you'll get updates on the videos we do each and every day here at Summit Auto, in fact in a second you'll see a link to subscribe to our YouTube channel in the upper left to link to more challenger videos like this one the upper right, link to this vehicle on our website in the lower left and a link to one of our latest YouTube videos in the lower right, click those check us out and we are super excited to be offering this ultra clean like new 2021 Dodge Challenger RT Scat Pack wide body in pitch black clear coat, thanks again for checking out the video remember to like, subscribe, and share


The flash message at this point, I suggest we read as follows. This made by preliminary reports of heavy fighting between Israel and Egyptian forces. As you know, we've been making the maximum effort to prevent this situation. We were expecting a very high level Egyptian delegation on Wednesday, and we had assurances from the Israelis that they would not initiate hostilities pending further diplomatic efforts. We feel it is very important that the United Nations Security Council succeed in bringing this fighting to an end as quickly as possible, and are ready to cooperate with all members of the Council to that end. We've been talking about in these terms that it's probably better for us to get some sort of a message of this sort before the question of who really was responsible, because it's completely clarifying to let them know that we were not a party to any of this business at this stage. But I wanted to get your own reaction to this. What does it appear to you? Does it appear to you reasonably sure that these tanks kicked it? Well, the fact that the fighting has been occurring initially over Egypt is a little hard to start out. It would put more weight on the Israeli claim that they had a large number of Egyptian aircraft headed for Israel from the sea, but I think it's just a little too early yet. My instincts tell me that the Israelis probably kicked this off, but I just don't know yet, and I don't think we ought to make a preliminary judgment on that because it's just hard to say. Do they say to us that the Egyptians kicked it off? Well, they're both publicly, we have nothing, no message yet from the Israeli government except that they've asked for a meeting with the Security Council. We've had no direct message from Eshgal or Iban or anybody. Both publicly are claiming that they are the start of it, but they Israeli claim that a big tank column is moving toward Israel and that they went out to meet it. Iban looks just a little thin on the surface. Meanwhile, we've asked Harlan Cleveland, who's now in a meeting of NATO that was called to talk about this situation, to keep a group of the prominent members on a stand-by to be consulting throughout the day to be available for consultation, and of course the Security Council will be meeting. The Security Council will probably call on both sides to meet for an immediate ceasefire. It will be usual and typical for them to do that, but we just don't know how to fake that we'll have.  Now, I think by long about six o'clock we ought to see what we know and see whether we ought not to have the leadership meet at least on the hill if not in the White House to bring them up to date on the situation, because they'll be steering down there in the Congress like everything today. True. All right, sir. Thank you.


Middle East is a region where most of its country is lacking peace, acceptance and tolerance. Do we want to enhance the problem? Or do we want to enhance the solution? Our presence here is just for a short period of time. We don't have to shorten it by fighting each other. It's like we are all having identity crisis. Who are we nowadays? I, throughout the research, I came across this code because I want to bring the code on the Arab word. More mayor tolerance does not cut it. We need to create an atmosphere of acceptance that embraces life in all its diversity. Middle East is a region where most of its country is lacking peace, acceptance and tolerance in an environment of hate. Unfortunately, that we are witnessing today in the region, how can we enjoy and embrace life? So when there is strife, when there is war, when there is killing, this looks like ridiculous. But the question is just this, do we want to enhance the problem or do we want to enhance the solution? The solution is only when people become inclusive. Will it happen today or tomorrow or day after tomorrow or a thousand years later depends on how you and me live today. We may not see it, but we can start it. Yeah, because your solution is part of individuals, they try to work together. And unfortunately, in these societies, it is very hard to work together. So this is most of the challenges that individuals and people are facing today. They are not willing. The inclusiveness that you are talking, the consciousness is really lacking in this area of the world. That's why I'm saying, see if you plant a tree, you may not go and sit under its shade. You may not get to eat the fruit because it takes a certain amount of time. But out of your love for life, you plant a tree. Next generation will enjoy it. Similarly, any great dimension of life, if you start, it will not get completed in your lifetime. If you start and set the right direction, the next generation will take it ahead. So our contribution is this, because as a generation, we occupy this planet for a short period of time. Everybody must remember this. Our presence here is just for a short period of time. We don't have to shorten it by fighting each other. This is the only thing we are doing today.


The Bemidji baseball team came this close to a state tournament birth just a season ago. Bemidji fell in the section 8-3 a championship to Little Falls by three ending their season short of their goal. But now the Jacks are back and primed to take what they believe is theirs. Though the Bemidji baseball team fell short of their goal of a state attorney birth a season ago, that doesn't mean expectations have changed for this year's group. We want to get to state tournament and win the game on target field, win a state championship, which is the goal for every year. We want to go out there and win every game and compete with the best in the state so we want to be back there. In fact not making the state tournament made this group that much hungrier. It was our year last year and it didn't happen so we want it to be our year this year. Last year we had some expectations but we weren't really sure where we fit in then all of a sudden at the end of the year we were right in the mix.  The Jacks lose nine players from a season ago but led by junior Otto Grimm and seniors Caleb Carlson and George Lockstercamp, they are confident in the group they have returning. There's nothing that's going to surprise them. We've played a really tough schedule last year. They had a great season for legions so those things are all in place and now we just have to go out and use that experience and act like we've been there before. Offense wasn't a problem for Bemidji last year. The team hit just on 300 clip but one area they felt they did need to address was their pitching. We thought we had a really strong pitching staff last year and we just didn't quite perform as well as we had hoped for and three of those top four are back so we're looking for a you know a little growth there. And if they can figure that out they believe there's nothing to stop them from making state. One through nine we're going to hit the ball well and do good things in the field and on the mound you know we'll need some tuning up at the beginning but after that we'll be we'll be set. We have tons of experience I feel like we're I feel like we're ready to take take the step down to the state tournament. If you've enjoyed this segment of Lakeland news please consider making a tax deductible contribution to Lakeland public television.


You want some OSHA training, but you're not sure which course you need? Well, there are several options when it comes to OSHA training courses. Is it the construction course you need, or the general industry version? Should you take the 10 hour course, or the 30 hour course? Do you need an on-site training class conducted for a group at your site, or would one of the online OSHA training courses be better suited for you? To help you answer all of these questions, this tutorial will explain the different versions and formats of OSHA training classes that are available through our company. Then, you should be able to know and get the OSHA training you need. The OSHA training courses cover one of two major industry categories. The first one is called general industry. These training courses cover the OSHA standards that appear in part 1910 of the Code of Federal Regulations. There are also OSHA training courses that cover the construction industry, which is regulated by part 1926 of the Code of Federal Regulations. The general industry courses cover most workers in the United States, including those employed at most factories. Therefore, the manufacturing of most industrial and consumer products, including food products, and the maintenance activities taking place at these operations, would all be covered by the general industry courses. So would employees involved in warehousing and logistic operations, chemical plants, oil and gas production operations, including refineries, biotech facilities, workers in the healthcare industries, such as medical care providers and dental offices, and those employed in various service industries, such as plumbing, food and hospitality, and janitorial services to name a few. The construction industry courses, on the other hand, cover those workers involved in new construction, including all site preparation work, the construction of commercial and industrial facilities, residential properties, and other structures. Construction courses also cover all demolition work, as well as major renovation, alteration, and repairs, which also includes painting. If you need an OSHA training course because it is a stipulation of a current or perspective employer or customer, make sure and check with them first to see which version of the training course they require you to take. There are a total of four OSHA outreach training courses available through our company. The first two are called the OSHA 10-hour courses for general industry and for construction, and the other two are called the OSHA 30-hour courses for general industry and construction. The 10-hour courses are geared towards the workers on the job and provide the trainees with an understanding of basic health and safety hazards commonly found in the workplace so they can be avoided. The course also explains who OSHA is, as well as some of the basic rights afforded workers under the OSHA Act. Participants who successfully complete either 10-hour course will receive the OSHA 10-hour wallet card for their industry. The OSHA 30-hour courses for general industry and construction are geared more towards safety managers and coordinators, as well as anyone else with responsibilities for oversight of or a strong interest in, safety and OSHA compliance matters. This course is therefore appropriate for supervisors and managers, as well as anyone else who wants a thorough overview of the OSHA regulations applicable to their industry. The 30-hour courses allow trainees to better identify workplace hazards and the means to control them for applicable OSHA regulations. It also provides them with an understanding of the many administrative responsibilities that go along with managing a safety and health program. Employees who successfully complete a 30-hour course will receive the OSHA 30-hour wallet card for either construction or general industry. There are two formats available for taking OSHA 10 and 30-hour courses for general industry and construction through our company. The first is on-site classes where you schedule a time for our OSHA authorized trainer to come to your site and conduct a class for your group. And the other are our OSHA accepted online courses. On-site OSHA 10-hour classes are typically spread over two days and 30-hour courses are usually spread over four days. That is because OSHA now limits the maximum time a student can spend in actual training to no more than seven and one-half hours on any given day plus additional time spent for breaks. Once the OSHA training class is completed, all students who successfully finish the course will receive a personalized certificate of completion and the official DOL wallet card for each student's OSHA 10 or 30-hour class will be mailed out after they have been processed at the OSHA Education Center. The online OSHA 10 and 30-hour courses are designed to be taken by an individual student. A student can register for an online course on our website or it can be done by someone else from their company or organization. There is also a link on our website for sending information if you want us to register multiple students for you. Help is also available by calling our office. Once a student is registered for their course they can begin training right away if they wish or they can log into their course at a later time. In fact, students taking one of our online courses have the luxury of logging in and out of their course at their own pace even from different computers. Every time the student logs out of their course it is automatically saved at that spot and when they log back in it resumes. Just like with on-site classes OSHA does limit the maximum amount of time a student spends training online to no more than seven and one-half hours in a given day with the timer being reset at midnight. OSHA also requires that all training be completed within a six month period from when the course began. However, students wanting to get done quickly can finish a ten hour course in as short as two days and their thirty hour course in as fast as four days. In fact, there is absolutely no faster way to get your OSHA training completed than by taking one of our online courses. Once the course is successfully completed the student can print out their Personalized Certificate of Completion. This temporary certificate provides the student with proof they completed the course and the official DOL wallet card for your online OSHA 10 or 30 hour course will be mailed after it has been processed at the OSHA Ed Center. By the way, the wallet cards for an on-site and online class are exactly the same there is no differentiation. So which OSHA training course do you need? Hopefully what was once a confusing mess is now as clear as can be. So visit our website at www.osha-training.com and check out our online and on-site OSHA 10 and 30 hour courses. While you're there you'll see we also offer on-site and online training for many other OSHA topics such as confined space entry and the Haswapper courses. You'll also find other OSHA training resources that we offer such as safety training videos and DVDs and free OSHA toolbox talks. So go to our website and get the OSHA training you need now.