 So you're ready to quit Swift programming while you reach the right video. Let me explain. Alright guys, I've got a good topic for you today. We're going to talk about Swift programming and some of the problems why I'm getting ready to quit or this person that we're talking to getting ready to quit Swift programming. So guys, the takeaway of this video is you need to focus on the language that gets you to most results from a project perspective. Most companies are going to have that top tier programming language, that primary programming language that you may be a secondary, but the primary is going to be probably 80, 90% of the code base. And they'll have a second one just for maybe proof of concepts, things like that. So as you guys progress through your career, you're going to find out pretty quickly that, you know, some in some areas, certain industries, certain programming language are going to be the priority for a company. And it may be even different than what you've done before and what you make money with before. So there's going to have to be some decisions made on do you quit or you stop using a program language for something that you didn't have on your radar initially. So I want to go into some of that for you guys here. I got some good notes here. I want to make sure I cover these effectively. So at the end of the day guys, the big problem is most of you guys are trying to learn too many programming language at once. And yeah, if you're doing it for a hobby on the side or something like that, go right ahead. This video may not be for you because this is specifically talking about business minded developers who are doing this from a business side. They want to make money. They want to really make their time more efficient. So this is for you guys. That being said, at the end of the day, you have to focus on that primary language. I got a couple of examples for you here. But before you do that guys, I have some goodies in the description box. I have a free seven step guide that's going to help you take your career to the next level and really help you not quit a program language but really help you progress to the next level of your programming journey. So go ahead and sign up for that seven step guide. Also, if you already signed up for that seven step guide, I have some premium courses that's going to help you as well. Links below for both my free guide and my premium courses and you can get access to our community for free as well. So go ahead and pick that up guys. That being said, let's talk about some of the problems you guys are going to have when it comes to quitting C sharp development. That being said, let's put ourself in a position of a freelance Swift developer. Guys, if you already know, Swift is a Apple based language used for iOS programming, all that stuff from Apple side of things. I've used it in the past. I don't use it as much now because I outsource a lot of that stuff and I'm mainly working with SQL C sharp and that's what I do. Well, depending on where you are in United States or overseas, different markets have different programming languages that they demand. In me, in my specific market, in my industry and what I do, Swift is not one of the things that stay priority. We outsource a lot of that stuff for other contractors who specialize in that because we don't do a lot of stuff on the Apple side of offense, unless it's just customer facing for driver portals and things like that. And with the mobile, the more reactive, oh, I can't think of it right now. Web design is more going to be, it's going to be better to not necessarily have a modern application. So you can do everything via web browser and it reacts to your actual web browser, your device, so that you got more flexibility. That means say, guys, at the end of the day, you have to make sure your skill set, your programming language that you personally learn is in line with the local demand or the industry you work with. Because if not, you're going to struggle with these issues that I'm going to discuss here. So one of the issues you're going to have guys has a freelance Swift developer. Just say if you're in a market that may not necessarily have all the Swift developers have Swift work, but it's more C sharp work. And at the beginning, you're a software developer, your freelance developer, you're just trying to get any gig and you'll eventually find yourself doing Swift jobs. At least that's the thinking at the beginning. So you take on a lot of these C sharp jobs and over time, you look at your job list and kind of gigs you got 90% of them are C sharp job and the other 10% are Swift. Now you're juggling. Now you're having to learn and specialize in two different programming languages. And yeah, if you're doing that occasionally, no big deal, no harm, no foul. But if you just you got a demanding client on your Swift side, maybe 10% of your business they call you every time stuff breaks with the app. That gets old quick. And if you try to scale get other people on your team, you want a standard program language even as a freelancer guys you want to apply clients who have similar programming stacks. So that when you do decide that hey, I want to hire somebody else. So I want to meet my workflow simple. You have the clients that have similar programming stacks. And he's going to make life easier for you. You don't have to maintain one source code or no one set of syntax and then kind of go from there. A lot of you guys make that mistake. I make that mistake. It's okay at the beginning, but you need to focus on what's in demand in your local market. That specific language so that you don't get stressed out. You don't spread yourself in. You can't be juggling all that stuff guys. Most markets, especially in the professional services, going to lean towards Java C sharp data science from the Python side of the fence. You got other are you got the Google's and more Silicon Valley's going to be more of the edgy goals and all that stuff. So each market is going to be unique. And you got to find that out and really kind of put yourself in a position where you're not juggling program multiple programming languages. That we're going to cause you to burn out because it's going to get hard guys. It sucks to have to manage two different code base switch between two major program language. And let me give you guys context as well. I'm not talking about just say a company has a main program language C sharp and they may have. Maybe I don't know 10% 5% or something like that may use Python or have a WordPress site. That's on the side. That's not necessarily a main system. This is reporting system. That's typical right there. I'm talking about you have two different clients or you. Let's just say you had 10 clients, right? Nine of them use C sharp and this other one use Swift and they call you 60% of the time you're on the phone with this client trying to fix something. You need to not fire but find somebody else that can support that code for you so that you can focus on that. Those other nine clients that have that C sharp code and maybe get a tent one so that you can make sure that your experience your workflow. This is more efficient guys. This is going to be very important for you because if you don't, it's going to stress you out. And I got a couple of tips here. I want you guys to really understand so that you don't make the same mistakes I made because now that you know this and you're thinking about quitting Swift before you do that. Let me give you some pointers here. One program language is not necessarily better than the next. And let me explain because at the end of the day, think about cars, right? You got a Lamborghini and you got a Honda, which one best? Most of you guys going to say the Lamborghini right off the bat. And I would say, I can see where you coming from, but you got to think use case, use case, use case. Most people going to be that Honda is going to be more useful for most people because of the actual practicality of it. The price of it, other characteristics that makes that particular car in that specific use case better. You got to think of your program language is the same way guys. Swift is one of those languages that is sexy, that's used all around, but some companies do not leverage it internally in their code base. At least they don't support the code. It may depend rely on a third party to do it, but they don't necessarily do it. Not that Swift is not better than C sharp or maybe not have a use case. It's just that particular use case that specific client need that. Think about your program language is the same way guys. Number two, align your skills with the local market demand or in your industry. Again, top 10 companies, what programming stacks they use, what programming languages you're going to start seeing trends. You're going to start seeing opportunities. You're going to start getting direction on what you need to learn and what you need to prioritize. As far as just I need to know this because 80% of the market use it. I can get that business and it's going to make life easier for me guys. Number two, languages that are not in demand. Take them off the table. This is different between hobby and you programming as professional. You have to take those off the table when it comes to businesses guys. Business time is money. All the time you're using learning a programming language that's not demand in company hours. It's time you're losing. So you need to get rid of those programming language and focus on the stuff that makes you the money. Again, number four, follow the money guys. Follow the money. If you're not following the money, you're going to put yourself in a position where you're going to be a broke developer. Starving artist. Bitch again, if you're doing this for a hobby, go right ahead. But we're talking business over here guys. This is the business of software development over here guys. So go ahead and do that. And number five, know what programming languages you do for hobbies and for business guys. At the end of the day, it's all about knowing what you want and knowing what the priorities are. And you're going to be less likely to quit. So at the end of the day guys, hopefully I gave you enough insight so that you can make the right decision on which programming language to use and which ones to quit using. And I hope this helped you guys. If you haven't already, go ahead. Links are below to my Seven Step Guide and my premium courses. Go ahead and check that out. If you agree with me, comment below. If you disagree with me, comment below so that we can start a conversation. Like, subscribe to the content. I'm going to put a link to my Seven Step Guide here to help you guys out. Click on that. I'll see you guys in the next video. Peace.