Before going into the details of our founding document, we need to look at it as a legal paper. It is written as an agreement for we the people and signed by people of the colonies, but signatories are representatives appointed by state-level governing bodies. The first note is that this is no government document. It does not get its authority from the sovereignty of any government unit, nor are states the signatory to it through their representatives. It is in accord with the common law covering contracts, we the people who are the only stated parties to this agreement. It is for specific notes that the United States is not even a party to this agreement. It did not even exist until it was signed. The intense wishes and needs of the new government formed under the provisions of this agreement are not even matters in issue. There is only one party to this agreement and it is we the people. In accord with the principles of the common law, there are only two ways to determine what has been agreed by we the people. The first is to read what was written. The second is to return to the people and ask after the subject of their agreement. There is no common law authority in the colonial governments, nor the central government that had been formed by the initial confederation of these colonial governments, to reset or influence the meaning of contracts between people. Neither is there any government right or privilege to change or expand upon agreements by and among the people. In specific, this document is not some authorizing book of instructions for sovereign government and its leaders. It is not like the constituting documents of other nations setting limitations upon the exercise of their sovereign rule. It is what its writing proclaims it to be, an agreement among the people of the United States on setting up and authorizing a government to serve their desire for self-governance. The authority of government does not include adding a title to this agreement to imply that it is something other than a written agreement for and by the people of the United States. The authority of government does not include interpreting or expanding upon the agreement of the people to accomplish some governmental purpose. No action can be authorized by this document that would interfere with the rights of citizens to own this government and to give it purpose. This document does not and cannot subordinate the people to the government authority without denying its own legal foundation. This is a matter of law concerning a written agreement, but we also have to recognize contrary results. We have a history of the U.S. courts treating this document as a royal edict to be interpreted as a matter of law. This demonstrates an active and continuing failure in applying the common law to address what was written into this signed agreement. To compound their open and obvious error, the courts have relied upon judicial readings to set new meanings and new intents upon our agreement. The courts have given effect to provisions on which we the people were not agreed. This is why it is often wise for a citizen to have attorneys when dealing with this government. It is wise to employ those who are expert in current legal interpretations and this to establish procedures. The courts will not protect the rights and privileges of citizens just because a citizen is an owner of this government. I must return to the purpose for this study of law and it is not intended to help you be lawyers. It is to provide for foundation in law so that you will become effective citizens when you gain your majority. Our constituting a document is foundation as is our environment in which the people came to agreement in establishing our national government. Where people are in agreement, they are the owner of both this nation and its government and they are the authority that can direct its officers to see the public purposes set by we the people. Does this constitutional agreement apply to you? In a practical sense, you are within the territory of the United States then U.S. law applies to you. This is true even if you are a foreigner who has no claim to U.S. citizenship. In a legal sense, the question is whether you are part of we the people who are signatories. The historical answer is that you are not part of the body of people who are directly represented, but you are part of their posterity. It was also intended for you to become a part of we the people that intent is written right into our national agreement. In yet another perspective, teenage students are not given that decision as a choice. Their parents make such determinations on their behalf. If your parents are citizens of the United States, then by default you are also a citizen and this parental agreement addresses your legal situation and relationship to government. On reaching your teen years, you find yourself given more and more choice with the purpose of supporting your maturation into independent and effective citizens of this nation. As you pass through your teen years, you will be required to make many of your own choices based on your personal decisions. One immediate challenge in this area of the course is whether you would agree to this same constitution as a guiding document for government that represents you. A second challenge is whether you would support like decisions of your friends, neighbors and fellows. These are both questions for you as part of we the people and as a citizen who will interact with the laws, institutions and procedures that define our legal government. Your answer of course is private in the sense that you are not required to confess your belief in this document. You are rather to learn about our constituting agreement to discover your own answers to your personal purposes and concerns. Your first challenge, will you be part of we the people of the United States? That is a choice that is not open to you under our laws until you gain your legal majority. Then, almost all of you will be defaulted into independent US citizenship. Inherent in that citizenship is the application of law and governance in reliance upon this constitutional agreement. You will then be able to deny your citizenship, but there are costs to an opting out. That takes a positive decision with acceptance of the costs. It requires positive action to deny citizenship. Still, that choice will always be yours. Once you gain your majority, that option cannot be legally taken away from you. It can only be delayed by contrary situations. This of course is the big stick of citizenship. It is ability of a self-governing people to accept or reject government. If a government becomes too abusive and burdens them, then we as individual citizens can withdraw from it. Like a peasant who is being abused by a feudal landlord, we are able to withdraw from the supposed authority delegated to a few who govern in our name. This is not some threat of revolution. It is a threat of abandonment. The government of the United States has only legal existence, as it has the support of we the people who continue as its citizens. So what is your part in the empowerment of government under our constituting agreement? The U.S. citizen is the source of authority for this government. The citizen is the ultimate owner of the United States government, established under the authority of this marvelous agreement. Your part on reaching your majority as a citizen will be in terms of sovereignty as a citizen. It will also be shared with other sovereignty of citizens. This government will be partly your creation, as you are part of today's we the people of the United States. We find a stated purpose for this government written into the documents preamble. It is a statement of the founding purpose for there being a government. It is a statement of what the people directed to the government that is documented here. These written provisions and purposes provide the legal reason that the people have been agreed to enter into and maintain this government. The first provision is a general one. It was the purpose of forming a more perfect union. In the original signing, union was the purpose for their signing this document. It was to establish a united government. Clearly we have a government in place, so what does this mean to us today? What is the meaning of this wording to us so we can agree among ourselves? For me it speaks to the perfection of the union. This is purpose that generally addresses our modern effort as working toward improvement of our government in promoting unity among citizens. For me that is a good and sufficient purpose for my acceptance of this document as foundation for our government. I stress that the choice is mine even as the choice will be yours. As a performance expert in my own right I note that people working together to get things done are many times more effective than people working against one another. I see government working in ways to create divisions and intentionally set some citizens against other citizens. Consider if you will the potential for legislation to promote either a pre-born's right to be born or a parent's right to abort. The very subject is one of division, one where it is unlikely that there will ever be agreement amongst all citizens on it being right or wrong either way. Any legislation in this area no matter which direction it takes will be divisive rather than unifying. If anything it appears that searching out our division producing legislation has become the common business of US leadership. We are not becoming more unified by active government and our government has been feeling us in this purpose. We are less unified now than we have been as a people in the past. The United States government seems to have taken on new purposes that are in discord with the purposes we set upon our constitution. For your consideration, is it our purpose to call this back to our originating agreement or to authorize and support other directions? The unity purpose is followed by to establish justice. Again, the original signing was establishment. I read this same wording as a modern purpose promoting justice for citizens today. In accord with modern political language I must emphasize that this is personal justice. Justice for each sovereign citizen who is in general agreement with this document. There is no separate social justice that is supported. Society does not sign this agreement. It is signed on behalf of sovereign self-governing people. It is also not some increased level of justice for some special people at the expense of others. It does not promote buying and selling justice as a commodity but promotes approaching it as a service for all who are part of we the people. In terms of this agreement that applies to each of us as sovereign sources it is a self-governing purpose behind this constituting agreement. As a quick observation of modern challenge wherever any citizen must have a personal lawyer to find justice the government is failing to provide it in accord with this overriding purpose in its founding document. Our government is created to serve us not to rule over us. Our government is to serve its citizens not to respond to legal experts as separate and special class of citizens. This is not a source of complaint even though there is certainly reason in light of failing to serve. This is a purpose for future public efforts a way in which the experiment that is the United States has potential for improvement. Next we have insured domestic tranquility. In historical perspective this is the governmental acceptance and promotion of the common law with implementation of such official actions and institutions as we'll see to its application. The purpose of that law was domestic tranquility promoting a society where people were able to generally live in peace in the presence of other citizens. It was where their legal actions and activities were promoted so that governments honored personal efforts to live in harmony. The personal challenge for you is whether this is what you want or what you will want when you reach your majority. The cost of this provision is your adherence to the requirements of the common law and support for the institution of application. The benefit is that others will have to be agreed on the same principles. I must put the question to you on this provision has government been acting in promotion of your peaceful dealings among others? If we are not agreed that our government is promoting a peaceful existence for us as citizens then it is challenging the unity principle discussed above. Provide for the common defense. The meaning in the original signing of this document was clearly associated with the national military defense of we the people. Through change of time and needs and also through amendment this document has come to address personal defense from both foreign and domestic assaults. Inherent in this is the idea of a combined defense effort. It addresses an effort that is so common that it brings we the people together in agreement to support public activities. In accord with our history defense has been one of the chief benefits of being a nation being a people who are not subject to foreign military aggression. As never before in history we seem to be growing into a society where groups of citizens gather and visit violence upon other citizens. Whether it is gangs of young tufts or terrorist cells does not matter under this provision. Our needs for common defense are undergoing change and perhaps serving for the common defense should also involve protection from internally promoted violence. Promote the general welfare. This provision is subject to multiple readings but all seem to address a common theme. It is to secure a common good for we the people. As with justice the common welfare of we the people cannot be common welfare for some people at the expense of others. In accord with the signing of this agreement we are addressing the common welfare of the gathered people and our government's role as promoted through the common welfare of the people as sovereign citizens. In this we have to address public welfare as a representative duty for people under this document. The amazing realization that giving charity is a personal freedom. It is a choice that is inherited being a member of we the people. A public action that sees to the welfare of some people at the expense of others denies this personal freedom. The government that engages in public charity where people would not give charity on their own is directly misrepresenting the people. Our misrepresentation through social programs is not the fault of the signed constitutional agreement. It is a potential area for eventual citizen action based on valid public purpose. The challenge for the student is again whether seeing to the general welfare is what you want your government to accomplish and will it be acceptable direction when you reach your majority. By default you are now a citizen of the United States but acceptance of the constitution as representing you as an individual is still to be determined and secure the blessings of liberty to ourselves and our posterity. The subject is liberty a synonym of freedom. It addresses lack of imposed restraints. The subject is liberty not only for ourselves as part of we the people but to people of the future who have the blessing of also becoming part of the future of this nation. Liberty is not freedom to do everything we want but freedom to do an agreement with others. This is freedom that respects the freedom of other people. It ignores honoring the special rights and privileges of other sovereign citizens. Even if you receive the support in exercising your own this has two impacts on governance. The first is that minimizing of imposed restraints that government establishes by its operation. The second is protection from of the freedoms that are recognized in we the people who are the source of government authority. It is also recognition of the superior rights and privileges of citizenship over those of governance even as we accept reasonable regulation to protect and preserve the benefits that come from peaceful exercise of our freedoms. It is something to which you agree as a citizen of a nation. Will you still be an acceptance when you reach your majority? Will this continue when you are asked to take part in self-government efforts of we the people? If you are an effective agreement with the purposes as stated then you can be an active part of we the people and your part is that of a sovereign citizen saying to our united purposes through the continuation of government in accord with the articles of this document.


Live from the Sands Convention Center in Las Vegas, Nevada, it's theCUBE at AWS ReInvent 2014. Brought to you by headline sponsors, Amazon and Trend Micro. Hey, welcome back everyone. You're watching theCUBE. This is Silicon Angles. Show where we go out to the events and extract the signal from the noise. I'm John Furrier. Joe at Jeff Kelly here at Amazon ReInvent, on the ground, two days of live wall-to-wall coverage. Executives, entrepreneurs, thought leaders, venture cast, we're all coming on theCUBE, sharing that signal with you. Our next guest is Ania Chakravarty, Chief Product Officer at Informatica. Big announcement today, Informatica, a huge company, really a leader. In the old school, considered old school, if you want to put that in a bucket, but also now relevant today with Amazon, as you guys continue to evolve the company with customers, welcome to theCUBE. Thank you, happy to be here. So we've been watching you guys for a while at Informatica, so we've always been looking for the companies that are moving with the customer trend or the ones who are buckled into their silo. Where I got my market share, everything's a nail on my hammer. I don't understand that. You guys see a future with cloud. So talk about that future and where Amazon's announcement today fits in and what is the announcement? Yeah, you know, with the cloud, we see at a high level, obviously, customers doing two kinds of things. One is they're using platform as a service, which is what they're doing with Amazon, or they're using software as a service with a number of providers like Salesforce. So we at Informatica, our point of view is that both of these will become an extension, continue to be an extension of the enterprise. And one of the reasons for us to go all in with Amazon is that they're using with Amazon is to help enterprise customers do that. With the platform as a service, that is really their extended data center of the future. And their data for all the enterprise customers that we've worked with over the last 20 years will be across both their enterprise with Amazon and across the cloud. And that's what we can help bring together. Okay, so I got to read this because this is a very bold move. So the press release that you guys are putting out says Informatica goes all in. You mentioned that on AWS to help enterprises move to the cloud. Data enablement portfolio makes it easy for customers to orientate. Okay, you know, get that, that's marketing. All in with Amazon. What does that mean to you guys? Is that all in as in chips in the table, moving in from the company standpoint, or all in as a metaphor? No, all in as in embracing what Amazon is really trying to do and supporting that. So if you go to Andy Das' keynote. You're not doing Texas Holder and putting all the company. No, we're not playing poker. Informatica, all the chips are betting on this. Yeah, I'm not a poker player. Exactly, look at this face. You think this is a poker player?  I can tell. Yeah, it's not a poker player.  But all in for us means, you know, we take a look at their strategy and say, especially look at what they're doing. You're all in on Amazon. You're not all in as a company with Amazon. Exactly, we're all in on Amazon. We believe that their long-term orientation, their focus on innovation and disruption is ultimately very good for customers. We're seeing customers adopt that in a big way. And we're all in helping customers adopt that in a big way. That's how we're all in. Yeah, the wind's at their back and you're seeing the CIA, you're seeing, I mean, the government. I mean, the fact that the government's consuming this way is a pretty good indicator that enterprises will pretty much move that way as well. So you're looking at that consumption trend and you guys want a piece of that business. We want a piece of that business and we say, look, actually we think that that business naturally extends from what we've been doing. People want it because they want, they don't want Amazon to be a silo. They want Amazon, what they're using on Amazon to be integrated with everything else they have and that's where we come in. Well, talk about what you're seeing from customers in terms of moving to something like AWS. Do you see them moving some of their traditional data warehouses and databases, things that you've helped support over the years? Are they looking at AWS for net new applications on some of the AWS big data products like Redshift, et cetera? What does it actually look like in the field in terms of enterprises and how they're using AWS for not just big data but just database, data management generally? Yeah, when we look at it, we see a lot of net new. Basically things that they either could not have done economically in the past or where they have new sources of data, new types of data that they can more easily combine and work with on Amazon's platforms. So what we see a lot of customers doing is they're incorporating some data from other sources that they already have but the workloads and the use cases that they are following are definitely net new in terms of what they're using Amazon. A lot of that. Can you give us any examples of some of your customers and some of the, even if you have, maybe you have to leave the names out, some of the interesting things you're seeing them do on AWS? Yeah, we see, I mean, we're actually in our Informatica world. We had a customer, a joint customer that was mentioned today which is the weather company. That's a common customer. The weather company is one of the big customers that's using Amazon Redshift and they are a company that has used Informatica Cloud. They've also used Informatica's on-prem products, Informatica Power Center products. They've been a customer for a long time but they're using Informatica Cloud to move a lot of their data where the analytics happens on Amazon's platform but they're using Informatica Cloud to move the data, to transform the data and to get the data at the right place so that they can do the analytics. So let's dig into that a little bit. How is the cloud impacting Informatica and how you deliver value to your customers? Is it simply taking what you've done on the on-premise world and now doing it in the cloud world or is there a new paradigm? Is there a new way that Informatica is providing value to customers in the cloud specifically? We obviously see the cloud as a huge opportunity. Most of what we see is actually net new so it's not really displacing what we have today because it's new workloads, new use cases combined with existing data sources. So we actually don't see customers doing a lot of say, hey, whatever I'm doing now I'm just going to do exactly the same thing in Amazon, which would mean an actual displacement. They're handling a lot of new use cases so it's incremental for us as well. But in terms of the actual workloads that Informatica is doing, I'm guessing in these new applications you still need things like data integration, data quality, data governance. So in that sense, are you still doing some of those core workloads that Informatica is known for or are there new things that Informatica has to do, has to adapt to provide value in a cloud environment? That's right. So in the cloud world what we define our portfolio as is not only cloud data integration, so data integration we did on-premise, we continue to obviously do that really well in the cloud. We also do cloud data management which thinks like data quality, master data management, data archiving, et cetera. And also cloud application integration. In the case of Amazon specifically obviously a lot of what we're working with is their analytics tools, et cetera so it's not necessarily application integration but in the case of other cloud providers Salesforce being a prime example, there's a big cloud application integration as well. So it's really, that is the combination of services we provide in the cloud. So let's talk a little more about AWS specifically. So I mean how do you, what's AWS, what is their impact that you've seen so far on the more traditional database world? I mean you have a great view of that world because that's where you do your work, right? You help it connect databases and systems. How are you seeing them disrupt the market? I mean you mentioned it's new workloads but is that, so it's not necessarily disrupting or replacing existing data warehouses and databases but presumably if these new workloads were taking place in AWS would they be taking place with these more traditional technologies? What's the relationship there and how do you see that playing out long term? Yeah again what we see, the impact is mostly on the new use cases, new workloads, et cetera. And obviously what AWS is doing is across the industry, they're just coming up with new models that's making everybody think about what they're doing. Now thinking doesn't immediately translate into I'm willing to vet my career as a CIO to take whatever is working today and move it in one shot, right? Nobody really wants to do that. What they're really leading to is thinking about new ways of doing analytics, new ways of doing storage, cost effective for sure but also just being able to handle workloads that they would never have done in the past. Basically taking for example web logs, streaming logs, unstructured data, combining it with structured data, being able to afford that, do it fast, do experimental work. These are the kinds of things that were really hard to do in the past. So what we see especially in the data world is they are really blazing a path with the offerings that they have around Kinesis, around Dynamo, around Redshift, around RDS. So they're bringing that whole portfolio of data-oriented services together. And our goal is obviously to be the data layer that connects across all of them. That's what we do today. We have connectivity and integration with all of those. We also have on-prem available to run within AWS. So for customers who want to be able to reuse any licenses or buy new licenses but they still want to keep the existing deployment but essentially run it on AWS as an infrastructure layer, they can do that as well. So you're allowing them that flexibility? Tell me about the big data business. Jeff and I were talking on the intro and I was trying to pepper Jeff on this and he was holding his ground. But I was making the bold statement that I don't think there is a big data market. I think big data as a sector might be a bit shaky in the sense that big data is more of an embedded feature where there are a lot of different growth areas in other markets, say cloud for instance. So I mean is there a big data market? Like I'm number one in big data. Like you see Cladera, Hortonworks, these guys and you guys are in this market. Of course we're trying to be provocative in the conversation but can there be just a siloed or pure play big data business? You know we actually thought of big data. We tried to sift through the hype and say what does big data mean? And we have actually defined six different types of analytics so I won't go through and bore you with all of them. Obviously Hadoop is one of them. We also see for example analytic databases like a Green Plum or a Verdeca. We have in memory for example. We have the visualization layer and obviously we have the cloud analytics layer with Amazon Redshift or Salesforce Wave. So big data actually is several different pieces of our types of technology and then if you look at it from a layer perspective where the data comes in, where it's processed, where it's accessible to the user, again a lot of the big data companies play a different layer. So there's a lot of confusion but if you look through the taxonomy there are multiple kinds of analytics and there are different big data players playing at different parts of the stack and that's what we think of as we think of as big data. So Jeff, what's your take on that? Do you think that people are going to be owning stacks or dancing around the stack because some are being very specialized in their pitch. What's your take? I think, look, if you think about big data it is part of a larger stack if you will around that involves cloud as well, dev ops and certainly it has to involve operational analytics or what we're calling inline analytics. So it's an important part it'll be interesting to see if these pure plays can establish themselves because it's going to integrate with everything else that you're doing in your organization. Where the data is coming from and also getting the data, the insights to different systems whether it's your traditional data warehouse which isn't going to go away or what's really exciting to me are these operational systems where you're taking all the insights clean from deep analytics maybe in Hadoop, something like Hadoop or a similar system, maybe even Redshift you've found some insight you've built a model but then actually shifting that model to an operational system so you're actually doing things in real time. So you've got to connect all these different systems so I doubt there will be one vendor that does all of that. AWS is interesting because they are enabling a new way to bring that all together in a way that abstracts it away from the customer and allows them to focus on their business which I think is an approach that is going to become more and more popular. I was just going to say exactly right we obviously want to play a piece in connecting all of that you're exactly right, I think in the initial days of big data you had for example a developer thinking let me do everything in Hadoop but the reality is if you want it to be a scalable system, an operational analytical system like this, it's got to integrate and you've got to start reusing what you have, otherwise you're never going to be able to do everything again and we see that model to it. Anil, I've got to ask you about Informatica so you all in with the Amazon piece of the business what's your plans going forward what's your top areas that you guys are focusing on, where you're investing behind where you go to market is strong what are some of the things priorities for you, for your business? Priority for us is we're creating what we call the intelligent data platform of the future the idea of the intelligent data platform and you can have any kind of data source structured, unstructured, Hadoop NoSQL, whatever it is on-prem or in the cloud and you can have any kind of consumption layer it could be a business user it could be an operational user it could be a machine that's consuming the data it could be any kind of consumption layer right now, the way it's working in the enterprise it's like lots of point to point connections that's not going to scale so our goal is to create an intelligent data platform layer that doesn't lock you into anything at the right time to the right application that's really what we're focusing on And how about the marketing side you guys have a nice marketing approach are there going to be direct sales force continuing more partnerships, how's that all balancing mix of indirect, direct it's a mix, it's a combination for example with Amazon we're doing a lot of things with the marketplace for example those are some of the new things that we are doing in terms of marketing traditionally we've obviously been a very direct sales oriented company at the large enterprise but we see the opportunity to work with a lot of partners everybody from the global system integrators down to the partners that you see here in this show so this is a market for all Thanks for coming on theCUBE, we really appreciate it I want you to share with the folks out there the bumper sticker for the show how would you summarize the show here today for Amazon, what does it say in the bumper sticker I was going to put a bumper sticker on the car what's it say? Well I would say a lot of people are going all in that's what we see I can see the proof as I come in It's all in, I mean Amazon certainly has the attention of developers for years now you start to see the real integration you start to see the business outcome again Informatica, great testament, endorsement for Amazon and good business model opportunity for you guys as well so I appreciate you coming on, Anil here inside theCUBE Chief Product Officer of Informatica breaking it down here at Amazon, reinvent this theCUBE I'm John Furrier with Jeff Kelly we'll be right back after this short break


What's going on everybody? Welcome back to another video. Today we are going to be reviewing your resumes. Now if you didn't know this already, I'm about to drop a pro tip on you. Your resume is really important in order for you to get a job and that is the high quality content that you guys come here for. So today I'm going to be reviewing some of your resumes and there's going to be a little bit longer video than normal because I will not be doing a lot of cuts. I'm going to be starting from the very top of the resume, working my way down to the very bottom of the resume. I'm going to be marking up the resume as I go along with my thoughts and critiques, things that I like, things that I don't like. This is going to be completely anonymous. So I'm going to take all of the personal information out of these resumes so that I can critique it without anybody feeling bad.  Without further ado, let's jump into our very first resume. So here's our very first resume. Like I said, we're going to be starting from the very top, going to the very bottom, and I'm going to be marking this up as we go along. So let's start at the very top with the header section. So he has his first and last name, phone number, an email, location, and then his LinkedIn. All good things. You can also add any type of website or any type of portfolio there as well. But how he has it looks totally fine. So I don't really have any feedback on this top section. Let's read this professional summary really quick, analytically driven financial analysts with two years of experience focusing on error-free reporting and analyzing trends on actual versus forecast revenue and indirect rates, managing an average of 12.5 million worth of direct projects each month as corporate FPNA mid-level associate. So, you know, a lot of people have a lot of different opinions on what you're supposed to do in this section. Some people take it truly as a summary. Some people will have bullet points and say kind of highlights of their career about them as a whole, like their education and different things. I have my own opinion on this and my opinion is that this is supposed to be kind of like a sales pitch, an elevator pitch, if you've ever heard of that. So imagine you get on an elevator with Elon Musk and you want him to know who you are and what you're, you know, you say you want a job with him, what you're looking for within those that 30 seconds that you have before he gets off the elevator. That's kind of what I imagine in this professional summary. And so it's hard for me to say that there's one right way to do this. So I'm just going to give you my opinion, what I think should be changed. In my opinion, I don't think you should be throwing around that you're working with 12.5 million of indirect projects. I don't think that's really, that really makes sense to be in a professional summary.  In my opinion, after that sentence, you should be saying like what you want, you know, here's who you are. Here's what you're looking for. And that's just my opinion.  So I'm not really going to mark that up. I think you can, I just would take out the 12.5 million worth of direct projects to me that just, I don't know, doesn't, doesn't rewrite feels a bit like showbody almost. I don't know if that's the right word. That's just my opinion. Let's go into the skills section. This is probably one of the more important sections. And let's look some of the skills that we've got. We got Cognos, Excel, Python, R, Microsoft Power Query, cost point, Power BI, SQL, Hyperion, SmartView, Java Tableau. Some of these things I have not heard of. And so this may be domain specific for financial analysts like cost point and Hyperion. I've heard of Cognos, but I don't use it. Normally how I would like to do this is kind of order it in the level of importance. If they're skimming this, they should see the most important ones right away. To me, things like SQL, R, Tableau, Power BI, Python, Excel, these are the things that I would be putting first so that when they are glancing at this or just looking at it, they see those things first and put things like Java, which not a lot of analysts are going to be using Java, Hyperion, SmartView, cost point, all these other things I'd be putting at the back or maybe even separate into two sections depending on the financial analyst role that you have. Then there might be two different skill sets. Some are domain specific, some aren't. So you can separate them out. But I would just be putting those first. Another thing that I really wish was on here, and let me get rid of these really quick, is after Python, if you just do a parentheses and you put some of the things that you know within Python, I find that to be extremely helpful. Because when you put Python in your skill section, to me, I don't know what that means. What do you know in Python? Do you know web scraping? Do you know how to build machine learning models? What are you doing with Python? I don't know. For me, I like seeing Pandas because Pandas is, of course, an analytics library in Python. It's extremely popular. It's used by a lot of teams. It's used by our team. I like seeing that where people have parentheses and have a subset of skills within that, or libraries or whatever it is. That's not only used for Python. You can do the same thing with Excel. You probably don't need to do it with something like SQL or Tableau. Those are pretty standard, I feel. I wouldn't be going in and putting SQL in parentheses, joins, unions, store procedures. That's just not something that I would do, but you can do that if you'd like. That's up to you. Overall, the skill section isn't bad. It says the skill, and that's what it does. If that's what you're going for, it was good. I would add more to it. I'd organize it a little differently. Let's look at this work experience. First off, right off the bat, this work experience section down here looks really odd to me. There's some really relevant stuff in here, but it doesn't elaborate on any of this. You have things like system admin intern, customer care analyst, data center technician 2, accounting intern, and then you have your current role, which is the financial analyst and financial planning. To me, it just feels really odd, like really cramped. I would choose maybe just the top one or two jobs that you feel are the most relevant or the most recent and include bullet points on those as well, because it just feels like you only have this one role that you're trying to put on there. This is really quick. Then there's this additional experience down here, which just feels even more strange. Again, I would cut out this additional experience. A sales consultant really doesn't have much to do with it. What I would personally do is I would trim this down to the top three jobs maybe, and then I would elaborate more on those. Let's really quick, going back up to the top. You don't have to have six, seven, eight, nine, 10 bullet points per job. I think five is like the max. You don't need more than five bullet points. I don't think you should put more than five bullet points. You should be able to condense your role, your main tasks that you feel are going to give somebody a good understanding of what you've done. I would trim back this first one right here, and then I would elaborate on maybe the last two jobs. Again, I don't know what these jobs, I don't know what you're doing in these, so take it with a grain of salt. I don't know exactly what you're doing in all these jobs, but it's really cluttered. There's a lot just going on right over here. This isn't how I would personally do it. Again, this is all just my opinion, you don't have to take my advice. This is just what I think. Let's take a look at some of these job descriptions within this role. Performing ad hoc analysis, special project as requested, assisting in planning, development, and execution of long-range deliverables. I'm going to skim really quick. Creating reports to help analyze in actual, help analyze actual and forecast potential areas of risk, contribute to monthly processes, prepare timely and insightful monthly variance reports, and create and execute. So everything that I'm seeing is really high level, which is not a bad thing. You have some action items like you're performing, you're creating, you're contributing. Good stuff. Something that I would be adding is if you can, and not everybody can do this, and not even everybody has even made that huge of an impact in their role, which sounds terrible, but if you can quantify any of this, any type of numerical information like I performed ad hoc analysis and special projects as requested, working with 20 different vendors or working with banks or whoever you work with, just something to quantify some of the work you do because when you say that, it can mean very little or can mean a lot depending on some of those different variables. Anything including like if you got your company a grant that got them a million dollars or something like that, you can throw that in there and it's very quantifiable and they can really understand it better, I think. And so yeah, that's the only thing that I think it's missing. I don't think anything that you have on there is terrible. That's just at a quick glance, that's what I think. And then I would again, I would redo this section a little bit because I feel like you just included too much. It's all the way back to August of 2010. I mean, it's 11 years ago. I don't think you need to go that far back. And so let's go down a little bit further. Let's go look at the education. So in 2019, graduated from George Mason University, double major in accounting and information systems and operation management. That's really cool. GPA three out of four. Boston University Masters of Science and Applied Data Analytics. Very nice. So good education. I'm not a person who wants to put the I think I had like a three, four or something. I don't I've never felt like the GPA was something that I should put on there or supposed to put on there. And I think that's I think that's really location based like that's like, like some people in certain countries or certain locations do that. I have never done that. I've never really cared if somebody had like a 4.0. You know, that's just not something that I personally have cared about. But I do think that sometimes in like internships, or if you're getting like an entry level job right out of college, it may be worth putting on there. Sometimes they require it is what I've been told. Again, I didn't do any type of internship. I just dove straight in and I didn't have that on my resume. So, you know, my opinion is just not to have it on there, but there are some cases where people want it on there or need it on there. So let's move on to the year up awards. And yeah, let me just I would just remove this. That's really all my feedback on that. So the year up a year up awards. I don't know what that is 2014 or 2015. I'm sure that's it might be like a company based thing. This is under his achievements. Excellence of leadership, engagement, embrace diversity, perfect attendance, intern of the month award. What is there to say? Won some awards, added them to your resume? I don't necessarily see a problem with it. Again, I have a lot of really I don't maybe maybe I'm just unique in the fact that that's not something that I would put on mine or care about. But you know, honestly, I could see people wanting to see stuff like this. And so I don't have a problem with this being on here at all. I personally just that's not something that I would be adding. I think things like scholarships and you know, awards for I guess maybe for for leadership and stuff like that is not bad to add. It's just not personally something that I would be adding to mine, just my opinion. So overall, I think this resume was not bad at all. You know, good education already has two years of experience, really good skill set just needs to be reformatted in my opinion a little bit. The layout overall is really good. I really like the sections and the layout and the way it's organized. Some people will put this skill section like way down here, even under education sometimes, I like that the skill section is right there. The glance factor is good on this resume. If you don't know what the glance factor is, the glance factor is the 15 seconds that a hiring manager or recruiter is going to look at your resume. And within those 15 seconds or however long they spend, you want them to really see who you are, the skills you know, the experience that you have extremely quickly. And this has that glance factor. I can really quickly skim this resume. And it's not super cluttered. It's not it's not a ton of reading. It just it tells you what it needs to know. So overall, I think this is a really good resume. I just had a little bit of feedback. But you know, I like this resume. So let's move on to the next one and see what that one is like. Alright, so we are on to the next resume. This one is definitely very unique. I'm going to scroll down really quick and just show you. It has the resume but also has some scripts as well. If you've seen my video, I used to do this when I was first starting out is I would send scripts with my resume, very similar to this. It was actually a separate file, but he just included it on his resume. So I am really looking forward to actually looking at these scripts and telling you what I think of those. If they, you know, make them look good or, you know, don't make them look good. You know, you can tell a lot about a person by how they write a SQL query, just so much. No, not really. But we're going to look at that in just a little bit. Let's look at the resume first and then we'll go on to the the SQL scripts. So right off the bat and I'm going to maybe zoom out a tiny bit. Maybe I shouldn't have done that. Let me go back. Right off the bat, my first impression is this isn't my favorite layout I've ever seen. Is it bad? It's up for interpretation. I don't hate it. I don't love it. And maybe that's just as bad as not like not loving it. Like it's just bad. To me, this kind of resume, I don't know, it just feels weird. I don't know how to explain it. I am a classic. Keep it simple for those automated processes on LinkedIn and stuff. Keep it simple to where the machine can read it. That's what I like. Again, personal preference. But let's start at the very top first name and last name. He says aspiring data scientist with BI and inventory background. Okay. I guess that's cool because there's a contact section right here. Let's take a look. The phone number, LinkedIn, hotmail. Okay, real quick. Oh, do I have this pulled up? Give me a second because I've been using this is what I'm using to get on here. Hotmail. Who uses hotmail? Because I didn't know hotmail was still in use. I thought they like discontinued that like 20 years ago. I'm obviously joking. But I mean, come on. Like just get like a Gmail account. It looks more professional. Hotmail makes you look old. I don't know how old you are. I really don't. Let me look. I'm not trying to be mean. Okay. So you graduated. It looks like with a bachelor's back in 2000.  I'm sure it shows age quickly. I personally recommend trying to stay up to date on I don't know. I don't want to say current technologies. But a hotmail has been, I mean, I don't know anybody who uses hotmail anymore. Just something I would take into consideration. It kind of shows a little bit of age on that one. And they also have a GitHub contact section looks good. So lots of good stuff in there. Let's look at the profile, an analyst background, oops, an analyst backgrounded in statistics and business operations with a strong passion and identifying patterns with seas of data, helping businesses make better decision by translating data into meaningful details interested in opportunities for gaining experiences in the areas of data sciences. Identifying patterns within seas of data. That's some that's some imagery right there. I'm not a big fan of poetry and imagery in a profile section. Also, I feel like it's super vague. Everything in this was vague, especially this part right here. So interested in opportunities for gaining experiences in the area of data sciences. Data science is so broad. I'm a data analyst. So of course, I know more about the analytic space than than this, which looks to be like a data scientist one. I'm just saying that that's super broad. And there's 100 different things that, you know, you could be looking for and we would have no idea. Just the area of data science. My advice is keep it simple. Two sentences, who you are, how many years of experience, the skills that you have and what you're looking for. This what you're looking for is just not beneficial. I feel like you need to be a little bit more specific. Yeah. And the seas of data thing, you know, maybe that just really shows your personality. I do not know you personally. And so, you know, maybe that's something that you really like and you want to keep in there. By all means, keep that in there. Gosh, I got this nose itch. I apologize. By all means, keep this in there. But it's just, it's, it doesn't come off as like, I'm a, I'm a super professional when, you know, you aren't being super specific on what you want. And you're adding, I don't know. And it just doesn't seem, this doesn't read super professional. That's my opinion. So let's move on to the skills. I feel like I've talked about that one enough. We have SQL, Python, SSRS, Microsoft, Excel. So you hit a lot of the core stuff. SQL, Python, SSRS is for like reporting in SQL server and then Microsoft Excel. All good skills. I feel like it's a very small list. Let me see.  Yeah. And maybe you just don't have any other skills. I would recommend, and this is just me, because this is a very small list of skills after how many years of experience back to 2011. Going back to 2011, I feel like you should have more than four skills. And maybe I'm wrong. I feel like you could pick up some skills on the side. I don't know your personal life. I don't know how much free time you have. But over the course of 2011, the past 10 years, I think you should have at least more than four skills. Try to pick up a cloud platform like AWS or Azure. Maybe try to pick up R or try to pick up. There's lots of other skills that you could be picking up. And I feel like only having four skills on resume is just kind of sad to look at. Again, I am not trying to destroy your resume in any way. I'm just trying to be honest. It makes me just kind of sad that there are more skills on there after 10 years of employment. Being an analyst and being an inventory analyst and a BI reporting developer, I just, that's what I think. Let's go on to the experience really quick. So we have BI reporting developer slash inventory analyst has been working there for six years. Really quick, just something that's jumping out of me is we have some quantifiable stuff right here. So I want to really look at this just really quickly reduced 50% of labor cost and 30% of count time of annual inventory count by developing a Python programmed data capturing application with barcode scanners, which replace the manual paper and pen process. Whoa, that is fantastic. Just reading that is like, that's impressive. I mean, I don't know how to do barcode scanning stuff. But if I read that, and I was like, well, this guy knows how to either he's really creative or is really inventive or he's a problem solver. That's really cool. That's a really interesting thing to put on a resume or job, you know, like your job description. Then there's an inventory inventory control coordinator. And this looks like kind of a management position. And then before that, an operations inventory analyst, logistic planner. And so obviously the highlight is on this first one, because that definitely has the most relevance. Development manage over 200 SSRS reports with Microsoft report builder and SQL servers. And I'm going to read the middle one because there's only one left though I want to read it reduce time needed to plan for cycle count schedules improvement from an average of three hours of planning to only 30 minutes by using Excel and Python periodically analyze sales data and classifying inventory. Oh, this is getting too long. Look, keep it simple. It needs to be like one sentence. It should not take up four rows. It was just a lot to read. They call it a wall of words. Wow. Because it was just it was long. It was too much to read. Of course, if I had a ton of time and I was really invested in your resume as a hiring manager or somebody, they might read every single word. But, you know, the glance factor on this one is not solid. Just for this section for other sections, it's fine. But overall good experience. It looks to have a good some good really good information. I really liked that first one. Although it was a little bit long. It's still told a really good important thing to know. Definitely a problem software, which is great to great to have. So overall, not bad at all. I would just reduce these in length a little bit, but a pretty good pretty good job description and good experience. Let's move on to the education education. Simon Fraser University statistics and mathematics of bachelors. And that's awesome. And then British Columbia Institute of Technology business diploma operations management. So you went first got the kind of more, I would consider more technical statistics and mathematics background and went back for the management. So I think that's how, you know, that coincides with some of his management experience. Really good stuff. I wouldn't change the thing. Education looks totally fine. Um, overall just the resume part. I personally would change the format of this entire resume to make it more easily readable, more clean, similar to the last one that we looked at. I just prefer those formats better because they're just when you are reading a lot of these and, you know, they come in like this and then, you know, there's different. How do I say this? It doesn't look as professional as those, the ones that we looked at last one. It doesn't look as professional. It doesn't look as clean. It looks kind of outdated is how I would say it. It looks a little outdated. Okay. So let's, and before we, before we move on, again, this is anonymous. So I'm, I'm just being completely honest. I'm not trying to hurt whoever's resume this is. I know who's resume this, but I'm not trying to hurt your feelings. I'm trying to be as honest as I possibly can be. So I hope you know that. I care about you. Um, but, you know, if something's off, I want to, I want you to know it. I'm trying not to do that in a hurtful way. Let's look at this SQL script because he provided, he or she provided this SQL sample and he included some notes in it. Um, but I'm not going to read that's a lot of notes, but it just says one of the first SQL script such reports that I developed as an inventory analyst. My question is, why would you include one of the first scripts you wrote as an inventory analyst? Why wouldn't you do one of the, you know, last scripts that you wrote that's much more impressive, much more clean, much more, I don't know. And maybe I'm wrong. Let's take a look at it. Uh, I don't know. I wouldn't be, I wouldn't show anybody my first scripts. They were terrible. Just absolutely awful. I would show people my really good scripts that I write now. Um, okay. I'm just, I'm just skimming it really quick before I kind of start giving feedback. So there's nothing, there's nothing really wrong with this and I don't have a problem with it. Um, there's not much, maybe it's up here and I'm just not reading it. There's not much explanation to what's going on. Um, what this data is, what these tables are. Um, I can, I, it really does look like he knows what he's doing. Um, the format is kind of funky in my, from, from, you know, it's just like, maybe this is how to develop. Oops, what am I doing? You know, maybe it's just how developers do things where I have like this huge space right here. Uh, I don't work with anybody who writes like that, but, um, it's very possible that that's just like a commonplace thing. Overall, he's doing a lot of good stuff using things like get date, case statements, um, joins, trimming row number, um, window functions, different types of joins, sub queries. I mean, there are lots of good things in here. So overall, I would, I don't, I would include this. I don't think there's anything wrong with it. I think there's just a lot going on and it's not formatted in like a super easily readable way. That's what I think is bothering me is because the format is just kind of funky and I don't, I don't know how to exactly say that, but like, when I look at this, this is not how I would write a case statement. It just, it's just not how I write a case statement. So, uh, overall though, I like it. I would keep it. I would just maybe even clean it up a little bit, organize it a little bit differently, but you may be writing it exactly how you want it and this is perfect to you. Totally fine. That's just, I have preferences. You have preferences. We all have preferences. Uh, so overall, not a bad resume. I think between these two, I preferred the last resume more. I like that one a little bit more. I think the skill section looked better. It looks cleaner, had more skills. Um, I'm not trying to compare. No, nobody does. He's, this person isn't worse than the other person. Just the resume, I think could use a little bit of updating. Um, anyways, I'm not going to harp on that any longer than I have to get a Gmail. Let's move on to the next one. Uh, and see what that one looks like. All right. So let's jump into this resume at the very top. The first thing that I'm noticing is that it is very barren. Um, it has the first name, the last name, and then just one email. Um, I would provide a little bit more information than this. I provide a location because if you are applying to somewhere and they don't know what your location, you could be from across the country for all they know.  Uh, and so I highly recommend, you don't have to put, you know, one, two, three, here's my address. You can just put, uh, Dallas, Texas. Uh, that's what I have on mind. And so I recommend putting some type of identifying location, um, on there. I also would recommend putting either your LinkedIn or some type of portfolio or website, something that they can go and look up if they choose to. And then, of course, um, if you want to include your phone number, uh, I recommend that as well. I just feel like there needs to be more up here. It's super barren right now. Um, there's not much, not much on there. I'll give you one second. Um, so, all right, I'm back. So the additional skills, um, additional skills. Is there another skill section? Uh, so I don't think these are additional skills. I think these are just your skills. Uh, so I'm not sure why they're called additional skills. It also feels, uh, it just feels weird not having, because every other one had like, uh, a summary. Yours has no summary. I don't have a problem with that. I think the summary section of a resume is kind of normally redundant. You're just repeating things out in your skills, in your experience anyways, or in your education. So I don't have a problem with it not being on there. Um, personally, I've thought about taking mine off because I feel like it makes no difference. But, uh, it just feels weird now looking at those past two resumes. So let's, let's forget about everything that I'm saying. Let's look at the additional skills. Again, I don't know why it's called additional skills.  Those are your main skills. So I just might call it skill section, uh, and just get rid of additional. So you have Python and SQL, Excel, SPSS, and Amos. I don't know why Python is, is grouped right here with SQL. Um, and I don't know why this is grouped either. Why not put, you know, Python and SQL and Excel on the same line if you're gonna do it that way. Um, I feel like there's a lot more that can be said and shown in this skill section rather than just putting Python and SQL. Um, like I said in one of the previous ones for Python, I don't know what you know in Python. Uh, I really just don't. Python is so broad. So if you can specify, you're using NumPy or using Map.lib, etc, etc. I would put that in parentheses and specify that because right now I just know that you know what that is. Um, and maybe down here you'll, you'll, you'll tell me later. Um, but as of right now, I have no idea. And that's your first thing you're telling me. This is my skill section. These are the things I know. Um, you know, uh, that's something I would work on. I don't know if you guys have noticed, but there's a weird font going on. It's called Georgia apparently. Yeah, I, I say keep it simple. This font, this font is like really weird. It's like it, it feels completely normal, but compared to the last ones, which were like normals, like times, times new Roman and what's the other normal one, this one just feels really weird. Um, you know, in, in general, I, I just recommend keeping it as standard and as normal as you can.  I don't recommend doing those things. I feel like most people in this profession, unless you're doing maybe like marketing analytics or something where you can showcase your, yourself in a different way and be creative with it. Um, but, but I in at least my line of work or, um, in my domain, that's not really something that people do. So I'd recommend keeping it super professional, the regular stuff. Um, you guys might find that boring. I just think it's smart. Um, so that's my feedback on the skill section in the font. So weird font to me. Um, here's relevant experience. I'm gonna skim this really quick. Uh, okay. Project leader, project leader, researcher, researcher. Let me go back to the very first job. I'm getting, I'm getting kind of confused at what this person does or what this person's like background is. Okay. So there's a Soul Pine International Restaurant Project. Collaborate with group members to ensure it is you. This is like a school project. Analyze data using linear regression to determine relationship with the data. Launch a new pathway service. Increase social limit. So I can't tell, I can't tell if this is a project and it says project on here. I think this might have just been like a school project, project leader. This may have just been like a project that they did in school, but it's really hard to tell. It says relevant experience. And then this one is a researcher and researcher. And I'm, I'm just reading some of these things because I'm, I'm genuinely confused at what I'm looking at. Developed. So the very first one says consumer research in restaurants during COVID-19 development online survey to measure consumers' perception, information seeking process based on theoretical models. Okay. Here's my, here's my thoughts on this. I'm really confused because it says relevant experience. You're saying project leader. I'm guessing this is a school project. Let me see what, when they were in school. Yeah. So maybe this is like the first year of their undergrad. It's very possible. Here's my feedback on it. The relevant experience and maybe it's just how I'm reading it. It doesn't seem like, it seems like the way you're, I guess, portraying or saying these things is really confusing. I would be breaking this up into two different sections. The first two, which look like actual jobs, which are as a researcher and a researcher, that would be my job experience. Whereas the projects could go in a project section because right now, maybe, and everyone watching this may make things completely normal. I'm just, I'm confused by the project section. And so, so yeah, so that would, that would be my biggest feedback would be separate these and make it more clear on what these are. You have some good stuff.  I mean, these are all good stuff in, you know, predictive segmentation. Like this stuff sounds really good. It's just hard to really understand the context and how you're, what you're using it for and what you're doing. It's hard to give feedback on it just because it's kind of vague. I don't really understand everything that you're doing in your position or what your job entails. I don't know what kind of tools you're using or anything. My recommendation would just be more specific. Be more specific in your job. I feel like you're, you are saying some good stuff. It's just, I don't understand how it applies to your position, what impact you had, those types of things. And so, and there's no, there's no type of quantitative information. Like I keep saying that word, but it's just numbers. I'm not saying any numbers to quantify the kind of work that you've done and the impact that you've had in your job. I feel like I said that really so fast, but I'm going to go to the next section because I don't want to keep harping on this. And then there's education, bachelors of food service management in South Korea, very cool, masters in food service management. So you're definitely in the food industry. I can tell you that, you know, how you know these things or worked on these things or why you're using these things. I kind of have an idea. It's just hard to tell. It really is hard to tell how you're trying to use your degree with these tools and you don't have any of the tools within your job description. Like how are you using Python? How are you using SQL? How are you using Excel? You can specify that in your job description so I can understand how you're using those things better because maybe you are using a bunch of Python for like this predictive segmentation. Maybe you aren't doing that. I just don't know. So yeah, so big takeaways from this resume for me is be much more specific for your skills with parentheses and adding those sub-skills. Be more specific in or separate those out those two columns or two areas for job experience and then projects. And then be more specific in what you're actually doing and the impact that you're having. That is for this resume. That would be my biggest feedback. And then the fonts. The fonts as well. I would personally just keep it standard and traditional. That's just me though. So that is this resume. So that is all the resumes that we're going to be looking at today. I hope that I wasn't too harsh on this one. I feel like in previous videos where I've done reviews on people's resumes, I was actually too, I guess, gentle. I didn't really speak my mind 100%. Whereas today I felt like I spoke my mind. If I didn't like something, I wanted you to know it and know why. So I tried maybe I tried a little bit too aggressive. We'll see. We'll see what you guys think. But honestly, I was just trying to be really honest. And these were all anonymous. And so I hope that I didn't hurt anybody's feelings. I was not trying to do that in the slightest. I am just trying to give you guys a glimpse into what I think of and what I'm trying to do. And when I review a resume, what I'm looking for. And so that when there's extra stuff or things are said in a certain way or there's certain fonts, I want you to know what I think of them. Take everything that I'm saying with, you know, just a grain of salt. I am just one person. There are many people that may disagree with me or see things in a different way. That's totally fine. I just hope that this video benefits you in some way that you go back to your resume and maybe make some updates or some changes that improves it and gives you a better chance at landing a job. Thank you guys so much for watching. I really appreciate it. If you liked this video, be sure to like and subscribe below and I will see you in the next video.


One of the most important shell utilities is the xargs command. What is xargs? It allows you to take standard input and pass that along as an argument into another command. You guys know that many shell commands actually allow you to take standard input and use that as a parameter for that command. Things like grip, sed, awk, cut, you know, they allow for that. But many shell utilities, shell programs, they don't actually allow you to take standard input and use that as a parameter for those commands. So think about the ls command, the list command, or the remove command, or, you know, more echo, you know, all those kinds of utilities. You can't just, you know, pipe something into them, right? You can't just take standard input and put that directly into those commands. To do that, you actually need another program to help with this, and that is what the xargs command does. So let me switch over to a terminal and show you the basic format of an xargs command. So typically how you would run xargs as you would do some command, I'm going to call it command one, and then you would pipe that into xargs space and then command two. And what this is doing is the output from command one is used as an argument for command two. I hope that makes sense. So let me give you a real world example. I'm going to do a sequence of numbers one through five. So I'm going to do seq space five. That gives me one through five each on their own line. But maybe I don't want one through five each on their own line. Maybe I want to pipe that into echo because echo would take that one through five and give me one through five all on a single line. Well, the problem is you can't pipe into echo echoes. One of those commands that just doesn't take standard input like that as an argument. But what you could do is pipe sequence five into xargs space echo, and then you get one through five all on one line. Now, I actually did not need to add echo to this command here because by default xargs if you don't give it a second command to use it automatically defaults to echo. So if I run that without the word echo, it returns the same output. One of the flags you need to know about with xargs is the dash t flag. So let me run that a sequence five again and then pipe that into xargs. And what I'm going to do this time is give it the dash t flag and that will say, hey, tell us the command that is being used. What are the arguments being passed into? And that's going to print out two lines now. You still get your standard output, which was the one, two, three, four, five. But it also prints out the actual command it runs to get that output. And of course, the command it's running is echo one, two, three, four. Because by default xargs uses echo unless you specify something else. Maybe instead of echo, we'll do printf. So it's printf one, two, three, four, five. It actually can't run that command because of excessive arguments. We probably needed that being wrapped in quotes. And of course it's not wrapped in quotes. One of the most common shell commands you run is the ls command. The problem with the ls command is it also can't take standard input as a parameter. But what you could do is you could pass a command into xargs and then pass along ls. So if I ran ls, pipe that output into xargs and run another ls, it's actually going to run ls on every single directory and file on this directory. So it's almost like a recursive ls, which ls has the ability to do recursive listing anyway, so it's not really that useful of a command. But that was just an example of how you could pipe something into ls using xargs. Now on Linux systems, there is a file called slash etsy slash pass wd, which lists all the users on your system, every single user on your system. And the problem with this particular file, if I cat it out, you see it's kind of a mess to read because there's really no spaces.  But we could actually clean this up a little bit. So what I could do is I could run this command here. This is the cut command dash d using the delimiter, the colon. I did a video just a couple of weeks back on the cut command. So check out that video if you're unsure about what cut does. But what it's going to do is it's going to go and use all the colons as delimiters. And it's going to grab the first field from each line. So I'm going to grab the first column from each line of the slash etsy slash pass wd file. And then it's going to sort it. So it's going to give me an alphabetical sorting. And then we're going to pass it into xargs, which xargs, of course, is going to use echo. And it's going to spit out a list of all the users on the system sorted alphabetically on one line. The next flag I want to show you is the dash capital I flag. So if I run an LS command here in my home directory, then I'm going to pipe that into xargs. And I'm going to give it the dash capital I flag. And what this does, it allows us to specify a placeholder, basically an alias for the arguments. So the output from the LS command in this case. So I'm going to specify in this case that the curly braces are basically a placeholder. They signify the output of the LS command. And then we'll give it our second command. In this case, I'm going to give it echo. And what I'm going to do is I'm going to do a slash home slash dt slash. Then I'm going to do the curly braces. And you see what that's going to do there? Again, the curly braces are the argument. It's the output from the LS command. And what it's going to do is it's going to echo slash home slash dt slash the name of the file or the directory because that's the output of the LS command. And you see how that would work if I ran a regular LS. Of course, you get just the file names themselves and not the full path. But what I did with this is I took XORGs and I echoed the full path slash home slash dt. And then the name of the file or the directory. Let me clear the screen. I'm going to up arrow back to that argument. Now you could specify anything as the placeholder, as the alias for the input. So if you didn't want to use the braces, I mean, you could use anything. I mean, I could use for capital X's here, right? It's not likely that that would ever, you know, occur naturally in standard input anyway. So I could use that and I would get the exact same output from running that command. Now this is where things really start getting interesting. So I made a test directory here called foo on my system. I did an LS, it's an empty directory, but let's make something. Let's make some files. Say I wanted to make 1,000 files in this directory. Maybe I want to do them sequential numbers. So I could do a sequence 1,000, you know, if I just ran it, you know, it just outputs one through a thousand here. But what I could do is then pipe that into XORGs. And again, let's do the dash capital I flag. I'm going to do the curly braces.  So touch is a command that creates an empty file for you. It's going to create a file named one through a thousand. So what we're going to do is we need to specify the curly braces again. So basically take everything from the sequence arguments. And then I also want you to add .txt to the names. So if I ran that and did an LS, you know, we created a one through 1,000.txt. Now imagine I made a mistake. I didn't want all those to have a .txt extension. I wanted them to have a .txt extension. Well, how would you go about fixing that mistake? Well, it's actually pretty easy. What I could do is I could do an LS. So I would LS one through a thousand .txt. Then I could pipe that. You know what? Let's pipe it into cut because we did a video about cut the other day. Let's use the period as a delimiter. So it's going to grab one through a thousand without the .txt because I specified stop at the period. Right? Period signifies the field separators. And then I only want you to return field one. So dash F1. So it's just going to give me a list one through a thousand, those numbers. Then let's pipe that into XORGs and give it the dash capital I flag one more time. Let's do the squirrely braces. And we're going to do the move command this time. I want you to move all of the arguments .txt. And I want you to move them to all of the arguments .txt. And if I did this correctly, run a LS. Now all the files have been renamed essentially. So now I have one through a thousand .txt. Now sometimes you don't want the output to be all on one line. For example, if I ran a LS and pipe that into XORGs and remember the dash t flag, if I did that, you know, it's going to be a massive amount of output. But at the very beginning, remember what it's actually running is echo and then all of the output. And then of course at the end it actually gives the output. So it's a very massive list of stuff here. But you don't have to have it treat every argument like that. You can specify a max number of arguments. So I could do dash in one, for example. And if I hit enter there, you see it takes each argument separately. It runs echo one and then you get the output echo two. Then you get the output echo three, output et cetera, et cetera. Instead of echo one through a thousand and then get the output for the whole thing. I hope that makes sense. So dash in is a number of arguments. If I did dash in two, what it's going to do is it's going to echo them two at a time. So it's going to echo one, two, and then it's going to echo three, four, et cetera, et cetera. Another example of a dash in flag, let me do a sequence five one more time. So we're going to do dash in one. So just the max arguments is one. And then the second command we're going to pipe this into, I'm going to pipe it into bash. We're just going to do some shell here. We're going to run the echo command dollar symbol zero. If I ran that, I get an error because I obviously did not add the S to XORGs. But there is that. Now, why did I run that? Because obviously that's just a very long and convoluted way of just doing sequence five piped into XORGs without all the extra stuff. It's because I want to also add the dash P flag for the number of processes. So in is the max number of arguments at a time. Dash capital P is the max number of processes at a time. I'm also going to do one process at a time. And then the command bash echo and then run that. It's still the same thing, but you will see it's actually not because what I'm going to do is I'm going to do echo dollar sign zero. And then I'm going to do a semicolon. I'm also going to tell it sleep one second. So what this is going to do is it's going to take one argument and one process at a time and in between it's going to sleep for one second. Now watch what happens. One, two, three, four, five. So that's kind of cool. So you have the dash in flag. Again, that's the max number of arguments at a time and the dash capital P flag. That's the max number of processes at a time. And just to make sure no one's confused thinking, well, max number of arguments, max number of processes, are they the same thing? No, they're not because if I did dash P two for two processes at a time, you see now I get two processes at a time. It did one and two together at first and then it did three and four together on the next process and then it did five by itself because there wasn't another argument to go along with five to make that two. Now probably the most common command people use with XARGs is the find command because the find command is really powerful but you can't really pipe anything into find but of course you can use XARGs with find. So I'm going to paste this command here. So this is a find command. What this is going to do is we're in that foo directory that has one through a thousand dot txt. Remember that? Well, what we're going to do is I'm going to find in foo, this directory, dash type F, find all the files, dash name that have dot txt as an extension and then we're going to pass this dot exec flag that is execute this command, remove RM, all the files that have dot txt at the end. Now why would I use XARGs if find has this execute flag? Well, the execute flag for find actually is kind of slow. I mean, it works but it's kind of slow. I could run that command by the way and we're already in foo. Let me CD back up into home and then from here specify find in foo type file name dot txt execute the remove command on all of the arguments. And if I CD back into foo and did an LS that is empty directory, we deleted those 1000 files. Now let me create those 1000 files. One more time, I'll rerun that sequence command, sequence 1000, pipe it into XARGs with a dash capital I flag and then run touch on that. So we get all of those created. Now other than using find with the execute flag a better way to do this is actually to just use XARGs. So if I go back up here to that last command, what I would do is let's remove all the dash exec stuff and just pipe that into XARGs and then remove. That's all we would need to do. Again, I'm actually in foo already. So instead of find foo, let's just find period. So we're in the directory foo. And then what this should do is remove all 1000 of those files for us and that's exactly what that did. Now one thing you may have noticed when I ran the find exec command to remove those 1000 files, it hung for a second. It took about a second for that command to execute before I got the shell prompt again. When I did it passing it into XARGs, I got another shell prompt immediately like it was lightning fast. We could actually put that to the test. I could time it. Why don't we do that? Let me go ahead. I'm gonna create 1000.txt files again and let's actually time this. So I'm gonna time the find command running the exec flag for find and then removing the arguments. And you see what the time is. So the real time is 0.708. The user time is 0.543. The system time is 0.148. Now let's do the same thing. Except this time, let's use XARGs to remove those files. So we're gonna use find to find the .txt files but we're gonna pipe it into XARGs RM. And you see how lightning fast that was? That was almost instantaneous. So if those of you worried about speed, especially with your scripting, you would never really wanna use the exec flag with find, especially when you're dealing with large amounts of files. You always wanna just pipe that into XARGs. So in a real world example, you can see XARGs is much quicker. Typically people would tell you that XARGs is just like six times, seven times more efficient than using the exec flag with find. So that was just a very brief overview of the XARGs command. It's really cool utility and it's one you need to know about because it's one you're gonna have to use because sometimes you're gonna want to pipe information into some of the shell utilities that normally can't be piped into. How do you get that information to be piped into them? Well, you have to use XARGs. Now before I go, I need to thank the producers of this episode, Absi Gabe, James, Mitchell, Paul, Wes, Akami Allen, Chuck, Kurt, David, Dylan, Gregory, Haco, Erion, Alexander, Peace, Arch, and Fedor, Polytech raver Scott, Steven, and Willie. These guys, they're my highest tiered patrons over on Patreon without these guys. This episode about the XARGs command would not have been possible. The show is also brought to you by each and every one of these ladies and gentlemen as well. All these names you're seeing on the screen. These are all my supporters over on Patreon because the DistroTube channel is supported by you guys, the community. If you like my work and you wanna support me, please consider subscribing to DistroTube over on Patreon. All right, guys, peace.